Menu
Use when a plan has parallel tasks and the harness supports dispatching subagents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.
Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists.
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.
Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
Use when the goal is vague or vision-level and can't be defined well enough for design questions.
| name | subagents |
| description | Use when a plan has parallel tasks and the harness supports dispatching subagents. |
Fresh context per task. No session history.
Subagents have file-read tools. Don't inline what they can read.
TASK: <one sentence>
FILES: <paths>
SPEC: <docs/staging/specs/...#anchor>
ACCEPTANCE: <test or cmd>
EXTRA: <only what's NOT in referenced files>
Pasting >10 lines from the spec? Stop - let the subagent read it.
Expand milestone -> atomic steps at dispatch time, not in the plan.
implementer -> on DONE: spec-reviewer (matches spec?) -> quality-reviewer (review) -> mark complete, continue.
The coordinator marks - [x], never the subagent.
DONE_WITH_CONCERNS - address if correctness; note if observation.NEEDS_CONTEXT - supply the fact, re-dispatch.BLOCKED - diagnose (missing context / stronger model / too big / plan wrong). Never silently retry.1-2 files mechanical -> cheap. Multi-file integration -> standard. Design/review -> strongest.
All done -> review whole diff -> ship.