Use when you have a PRD or design spec and need a bite-sized, executable implementation plan that any agent can follow without re-deriving structure. Produces `docs/plans/YYYY-MM-DD-<feature>.md` with per-task Files block, complete code per step (no placeholders), and exact verification commands. Rejects "TBD", "TODO", "add error handling", "similar to Task N".
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/15/2026
What it changes
Passed 12 of 17 test cases with the skill, and 7 of 17 without it.
Without skill41%
With skill73%
Checks it passed that the model alone missed
Presents coordinator-direct execution as an execution hand-off option.
Presents wave-executor parallel dispatch as an execution hand-off option.
and 6 more in the full report
7 fixed9 passed either way6 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+135%
Agent turns
0%
Response time
-56%
Model gemini-3.6-flashMeasured 8/15/2026v116 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
We are generating an execution plan today (2026-08-15) for a feature titled 'OAuth2 Single Sign-On Integration'. What exact file path should be used when writing this plan to disk?
What was checked, without and with the skill
Checked
Without skill
With skill
Saves the plan file to docs/plans/2026-08-15-oauth2-single-sign-on-integration.md.
Missed
Passed
case-17 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md229 linessingle file
Write Executable Plan
Bite-sized plans for parallel agents. No placeholders. No vague steps.
When to use
A PRD from /plan feature exists but you need a step-by-step implementation plan
A /brainstorm design is approved and you want to skip the PRD layer
Multiple agents will execute the plan in parallel and need conflict-free task boundaries
The work is complex enough that describing it to an agent loses fidelity
When NOT to use
Trivial 1-file changes (just do them; no plan needed)
Pure exploration (use /brainstorm instead)
Bug investigation (use /debug instead)
The source PRD is vague or unapproved (get PRD approval before planning execution)
Phase 0: Bootstrap Gate
Read skills/_shared/bootstrap-gate.md and execute the gate check. If the gate is CLOSED, invoke skills/bootstrap/SKILL.md and wait for completion before proceeding. If the gate is OPEN, continue to Phase 1.
Phase 1: Source Selection
Accept ONE of the following inputs (in order of preference):
PRD path — docs/prd/YYYY-MM-DD-<feature>.md produced by /plan feature
Design spec path — docs/specs/YYYY-MM-DD-<slug>-design.md produced by /brainstorm
Inline description — user provides a free-text description; prompt for elaboration via AUQ before proceeding
If no source is provided and $ARGUMENTS is empty, ask via AUQ:
AskUserQuestion({
questions: [{
question: "Which source should this plan be based on?",