rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-07-17 23:44:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(sdd): align templates and codex reference with resume-based fix rounds

Browse Source
This commit is contained in:
Jesse Vincent
2026-07-15 11:36:24 -07:00
parent bdbe81c403
commit 236077326b
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
skills/subagent-driven-development/implementer-prompt.md
View File

@@ -106,9 +106,12 @@ Subagent (general-purpose):
## After Review Findings ## After Review Findings
If a reviewer finds issues and you fix them, re-run the tests that cover If the task review finds issues, you will be resumed with the findings.
the amended code and append the results to your report file. Reviewers Fix them, re-run the tests that cover the amended code, and append a fix
will not re-run tests for you — your report is the test evidence. report to your report file: what you changed, the covering tests you
ran, the command, and the output. Reviewers will not re-run tests for
you — your report is the test evidence. Then reply with the same short
status contract as your first report.
## Report Format ## Report Format

3
skills/subagent-driven-development/task-reviewer-prompt.md
View File

@@ -183,6 +183,3 @@ Subagent (general-purpose):
**Reviewer returns:** Spec Compliance verdict (✅/❌/⚠️), Strengths, Issues **Reviewer returns:** Spec Compliance verdict (✅/❌/⚠️), Strengths, Issues
(Critical/Important/Minor), Task quality verdict (Critical/Important/Minor), Task quality verdict
A fix dispatch can address spec gaps and quality findings together;
re-review after fixes covers both verdicts.

2
skills/using-superpowers/references/codex-tools.md
View File

@@ -7,7 +7,7 @@ Add to your Codex config (`~/.codex/config.toml`):
multi_agent = true multi_agent = true
``` ```
This enables `spawn_agent`, `wait_agent`, and `close_agent` for skills like `dispatching-parallel-agents` and `subagent-driven-development`. When using subagent-driven-development, you should always close implementer and reviewer subagents when they have finished all their work. This enables `spawn_agent`, `wait_agent`, and `close_agent` for skills like `dispatching-parallel-agents` and `subagent-driven-development`. When using subagent-driven-development, close reviewer subagents when their review returns. Keep each implementer subagent open until its task's review passes — the fix loop resumes the implementer — then close it. If your harness cannot send another message to a spawned agent, dispatch each fix round as a fresh implementer carrying the brief, the report file, and the findings.
## Environment Detection ## Environment Detection