Skip to content

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

Merged
bradygaster merged 2 commits into
devfrom
squad/1634-casting-brief-resolution
Aug 7, 2026
Merged

feat(gh-aw): use parent issue as casting brief for /squad cast#1635
bradygaster merged 2 commits into
devfrom
squad/1634-casting-brief-resolution

Conversation

@bradygaster

Copy link
Copy Markdown
Owner

Summary

Adds Step 0: Brief Resolution to Cast mode in workflows/squad.md, inserted before the existing Step 1 (Repo Analysis).

This step evaluates two signals — the parent issue body and the repository content — and applies a priority cascade to determine which is the primary casting input:

Repo Signal Issue Signal Result
Empty Empty Noop — comment + stop
Empty Rich brief Issue wins
Has content Has content Merge — repo base, issue augments
Has content Empty Repo wins (current behavior)
Any Explicit SOT signal Issue is SOT — user intent overrides

The noop case posts a helpful comment via add-comment and stops without opening a PR.

All existing steps (1–6) remain unchanged — Brief Resolution just sets context for how downstream steps use the repo analysis.

Closes #1634

Adds a Brief Resolution step (Step 0) before repo analysis that
evaluates both the parent issue content and repository state to
determine the primary casting input. Implements a priority cascade:
empty+empty=noop, issue-only=issue wins, both=merge, repo-only=repo
wins, explicit SOT signal=issue overrides.

Closes #1634

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings August 7, 2026 19:19
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

🟢 Impact Analysis — PR #1635

Risk tier: 🟢 LOW

📊 Summary

Metric Count
Files changed 1
Files added 0
Files modified 1
Files deleted 0
Modules touched 1

🎯 Risk Factors

  • 1 files changed (≤5 → LOW)
  • 1 module(s) touched (≤1 → LOW)

📦 Modules Affected

root (1 file)
  • workflows/squad.md

This report is generated automatically for every PR. See #733 for details.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

🛫 PR Readiness Check

ℹ️ This comment updates on each push. Last checked: commit 87804b1

PR Scope: 🔧 Infrastructure

⚠️ 2 item(s) to address before review

Status Check Details
Single commit 2 commits — consider squashing before review
Not in draft Ready for review
Branch up to date Up to date with dev
Copilot review No Copilot review yet — it may still be processing
Changeset present No source files changed — changeset not required
Scope clean No .squad/ or docs/proposals/ files
No merge conflicts No merge conflicts
Copilot threads resolved 0 active Copilot thread(s) resolved (2 outdated skipped)
CI passing All checks passing

Files Changed (1 file, +31 −0)

File +/−
workflows/squad.md +31 −0

Total: +31 −0


This check runs automatically on every push. Fix any ❌ items and push again.
See CONTRIBUTING.md and PR Requirements for details.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Cast mode workflow documentation to add Step 0: Brief Resolution, clarifying how /squad cast decides whether the parent issue brief or repository analysis is the primary casting input before proceeding with the existing steps.

Changes:

  • Documented a new “Brief Resolution” step with a priority cascade across issue brief vs repo signals.
  • Added explicit noop handling guidance when neither the issue nor the repo provide meaningful casting input.
  • Clarified how the chosen input priority should influence downstream repo analysis.
Show a summary per file
File Description
workflows/squad.md Adds Step 0 documentation describing brief selection, noop behavior, and how to carry that decision into existing Cast steps.

Review details

  • Files reviewed: 1/1 changed files
  • Comments generated: 2
  • Review effort level: Lite

Comment thread workflows/squad.md Outdated
Comment on lines +115 to +117
Before analyzing the repo, determine the **primary casting input** by evaluating
two signals: the parent issue body (`github.event.issue.body`) and the repository
content (README, file structure, etc.).
Comment thread workflows/squad.md Outdated
Comment on lines +127 to +131
| Any | Explicit SOT signal | **Issue is SOT** — user intent overrides, repo validates only |

"Explicit SOT 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.
…pand SOT acronym

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster
bradygaster merged commit a4b60e8 into dev Aug 7, 2026
15 checks passed
@bradygaster
bradygaster deleted the squad/1634-casting-brief-resolution branch August 7, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use the parent issue as the casting brief for /squad cast

2 participants