Skip to content

perf(workflows): load shipped mode playbooks as inline skills #1739

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 1 commit into from
Aug 18, 2026
Merged

perf(workflows): load shipped mode playbooks as inline skills #1739

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 8 additions & 4 deletions .github/agents.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,17 +222,21 @@ Squad's planning behavior is configurable through policy profiles.

### Selecting a Profile

Add an HTML comment to the issue body:
Add a policy directive line to the issue body:

```html
<!-- squad-policy: lean -->
```markdown
Squad-Policy: lean
```

Use a plain visible line — **not** an HTML comment. gh-aw strips HTML comments
from issue bodies before the agent sees them, so a commented directive is
silently ignored.

Or configure at the repo level in `.squad/planning-policy.md` with YAML frontmatter.

### Priority Order

1. Issue body (`<!-- squad-policy: ... -->`) — highest
1. Issue body (`Squad-Policy: ...`) — highest
2. Repository file (`.squad/planning-policy.md`)
3. Profile name (built-in)
4. Default — fallback
Expand Down
2 changes: 1 addition & 1 deletion test-fixtures/planning/aspiregregator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The Aspiregregator is a .NET Aspire community content aggregator application. Th

### Manual Validation

1. Compare each output file against the schema in `workflows/shared/planning-ontology.md`
1. Compare each output file against the schema in `workflows/shared/squad-planning-ontology.md`
2. Verify every `Structured data:` JSON block has `schema_version: "1"`, `origin_issue: 8`, `phases: []`, and the expected `squad_artifact`
3. Confirm traceability: every task → epic → initiative → triage item

Expand Down
Loading