Task 2: Align the implementer and task-reviewer templates and the Codex reference with resume semantics

Files:

• Modify: skills/subagent-driven-development/implementer-prompt.md (the "After Review Findings" section)
• Modify: skills/subagent-driven-development/task-reviewer-prompt.md (trailing paragraph)
• Modify: skills/using-superpowers/references/codex-tools.md (subagent close timing)

Interfaces:

• Consumes: re-review-prompt.md exists (Task 1).

• Produces: the implementer contract Task 3's fix loop cites ("fix, re-run covering tests, append to your report file, return the short contract").

• [ ] Step 1: Replace the "After Review Findings" section in implementer-prompt.md

Old text (exact):

    ## 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.

New text (exact):

    ## After Review Findings

    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.

• [ ] Step 2: Delete the trailing re-review paragraph in task-reviewer-prompt.md

Delete this text (exact, at end of file):

A fix dispatch can address spec gaps and quality findings together;
re-review after fixes covers both verdicts.

Nothing replaces it — the scoped re-review contract now lives in re-review-prompt.md, and SKILL.md step 4 (Task 3) owns the loop rules.

• [ ] Step 3: Update the Codex subagent close-timing sentence in codex-tools.md

Old text (exact, line 10):

When using subagent-driven-development, you should always close implementer and reviewer subagents when they have finished all their work.

New text (exact):

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.

• [ ] Step 4: Verify no template still references dedicated fix subagents

Run: grep -rn "fix subagent" skills/subagent-driven-development/*.md Expected: no output (SKILL.md still has hits until Task 3 — this command scopes to templates only after Task 3; at this point expect hits ONLY in SKILL.md).

Run: grep -rn "fix subagent" skills/subagent-driven-development/implementer-prompt.md skills/subagent-driven-development/task-reviewer-prompt.md skills/subagent-driven-development/re-review-prompt.md Expected: no output.

• [ ] Step 5: Commit

git add skills/subagent-driven-development/implementer-prompt.md skills/subagent-driven-development/task-reviewer-prompt.md skills/using-superpowers/references/codex-tools.md
git commit -m "feat(sdd): align templates and codex reference with resume-based fix rounds"