Skip to content

An agentic skills framework & software development methodology that works.

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

Jesse Vincent28882fcbc358
diff --git a/skills/subagent-driven-development/implementer-prompt.md b/skills/subagent-driven-development/implementer-prompt.md
index 218fcfeb5..fbe441e20 100644
--- a/skills/subagent-driven-development/implementer-prompt.md
+++ b/skills/subagent-driven-development/implementer-prompt.md
@@ -106,9 +106,12 @@ Subagent (general-purpose):
## After Review Findings
- If a reviewer finds issues and you fix them, re-run the tests that cover
- the amended code and append the results to your report file. Reviewers
- will not re-run tests for you — your report is the test evidence.
+ If the task review finds issues, you will be resumed with the findings.
+ Fix them, re-run the tests that cover the amended code, and append a fix
+ 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
diff --git a/skills/subagent-driven-development/task-reviewer-prompt.md b/skills/subagent-driven-development/task-reviewer-prompt.md
index 9fb24c408..fefaea8a7 100644
--- a/skills/subagent-driven-development/task-reviewer-prompt.md
+++ b/skills/subagent-driven-development/task-reviewer-prompt.md
@@ -183,6 +183,3 @@ Subagent (general-purpose):
**Reviewer returns:** Spec Compliance verdict (✅/❌/⚠️), Strengths, Issues
(Critical/Important/Minor), Task quality verdict
-
-A fix dispatch can address spec gaps and quality findings together;
-re-review after fixes covers both verdicts.
diff --git a/skills/using-superpowers/references/codex-tools.md b/skills/using-superpowers/references/codex-tools.md
index 1897cc3bb..b14b58582 100644
--- a/skills/using-superpowers/references/codex-tools.md
+++ b/skills/using-superpowers/references/codex-tools.md
@@ -7,7 +7,7 @@ Add to your Codex config (`~/.codex/config.toml`):
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