Skip to content

feat(gh-aw): use parent issue as casting brief for /squad cast #1635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bradygaster merged 2 commits into from
Aug 7, 2026
Merged

feat(gh-aw): use parent issue as casting brief for /squad cast #1635

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8033e76
feat(gh-aw): use parent issue as casting brief for /squad cast
bradygaster Aug 7, 2026
87804b1
fix(gh-aw): address Copilot review — include issue title in brief, ex…
bradygaster Aug 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions workflows/squad.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,37 @@ Cast mode analyzes the target repository, composes a specialist team, assigns
character names from a fictional universe, generates full `.squad/` scaffolding,
and opens a PR introducing the new team.

##### Step 0: Brief Resolution

Before analyzing the repo, determine the **primary casting input** by evaluating
two signals: the parent issue title and body (`github.event.issue.title` +
`github.event.issue.body`) and the repository content (README, file structure,
etc.). Both title and body contribute to the casting brief — a non-empty title
with an empty body is still a valid issue signal.

**Priority cascade:**

| Repo Signal | Issue Signal | Result |
|-------------|-------------|--------|
| Empty/bare | Empty/no body | **Noop** — post a comment (see below), stop |
| Empty/bare | Has content | **Issue wins** — cast from the issue description |
| Has content | Has content | **Merge** — repo is base context, issue augments or overrides |
| Has content | Empty/minimal | **Repo wins** — standard cast behavior |
| Any | Explicit source-of-truth signal | **Issue is source of truth** — user intent overrides, repo validates only |

"Explicit source-of-truth signal" means the issue body reads like a team spec — explicit role
lists, team-size declarations, operating-model descriptions, or language that
signals "this is what I want." Infer this from structure and detail level.

**Noop handling:** When both inputs are empty, use the `add-comment` safe-output
to post: "Nothing to cast from — the repo has no substantive content and the
issue has no casting brief. Add a README describing your project, or write your
desired team composition in this issue body, then re-run `/squad cast`." Then
stop — do not proceed to Step 1 or open a PR.

Carry the cascade result forward: it determines whether Step 1's repo analysis
is the primary input, an augmenting signal, or a validation-only pass.

##### Step 1: Repo Analysis

Analyze the repository to understand what kind of team it needs:
Expand Down
Loading