Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 1 addition & 0 deletions skills/dispatching-parallel-agents/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,7 @@ When agents return:
- Verify fixes don't conflict
- Run full test suite
- Integrate all changes
- Release each agent unless you intend to send it further input — on some harnesses a finished agent holds its slot until closed (see the per-platform tool refs in `../using-superpowers/references/`)

## Agent Prompt Structure

Expand Down
1 change: 1 addition & 0 deletions skills/requesting-code-review/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@ Dispatch a `general-purpose` subagent, filling the template at [code-reviewer.md
- Fix Important issues before proceeding
- Note Minor issues for later
- Push back if reviewer is wrong (with reasoning)
- Release the reviewer unless you intend to send it further input — on some harnesses a finished agent holds its slot until closed (see the per-platform tool refs in `../using-superpowers/references/`)

## Example

Expand Down
7 changes: 7 additions & 0 deletions skills/subagent-driven-development/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -215,6 +215,8 @@ final whole-branch review. When you fill a reviewer template:
subagent with the complete findings list — not one fixer per finding.
Per-finding fixers each rebuild context and re-run suites; a real
session's final-review fix wave cost more than all its tasks combined.
- Release the final whole-branch reviewer, and any fixer it triggered, once
you have acted on its findings and will send them no further input.

## File Handoffs

Expand Down Expand Up @@ -257,6 +259,11 @@ a ledger file, not only in todos.
- When a task's review comes back clean, append one line to the ledger in
the same message as your other bookkeeping:
`Task N: complete (commits <base7>..<head7>, review clean)`.
That bookkeeping includes releasing the subagents the task used —
implementer, task reviewer, and any fix subagents — you will send none
of them further input. On some harnesses a finished agent holds its slot
until closed (see the per-platform tool refs in
`../using-superpowers/references/`).
- The ledger is your recovery map: the commits it names exist in git even
when your context no longer remembers creating them. After compaction,
trust the ledger and `git log` over your own recollection.
Expand Down