Menu
plan-it: the planner that plans it before build-it builds it
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
Turn a fuzzy idea, brain-dump, or transcription into a COMPLETE spec set + agile delivery package, ready to hand to /build-it. The front-end to /build-it: plan-it plans it, build-it builds it. Runs a ~10-phase discovery → spec → agile-split pipeline — pre-grounds the codebase, fans out parallel Claude teams (xhigh) to research independent subsystems, authors the design docs in dependency order, pauses at ONE batched human-decision gate, then freezes a shared CONTRACT and fans out squad teams to write PRDs + epics against it — each epic ending in a BINDING Test Contract (up to ~20 type-selected use-cases/scenarios the build must pass 100% before "done", per Specification by Example / Eval-Driven Development). Auto-sizes from a single feature (1 design note + 1 PRD + 1 epic set) to a from-scratch program (full 7-doc set + 4 squads + waves). Use when the user says "/plan-it", "plan this", "plan-it this", "spec this out", "turn this into a delivery package", "create the PRDs/epics", "do discovery and planning", "
Turn a fuzzy idea, brain-dump, or transcription into a COMPLETE spec set + agile delivery package, ready to hand to /build-it. The front-end to /build-it: plan-it plans it, build-it builds it. Runs a ~10-phase discovery → spec → agile-split pipeline — pre-grounds the codebase, fans out parallel Claude teams (xhigh) to research independent subsystems, authors the design docs in dependency order, pauses at ONE batched human-decision gate, then freezes a shared CONTRACT and fans out squad teams to write PRDs + epics against it — each epic ending in a BINDING Test Contract (up to ~20 type-selected use-cases/scenarios the build must pass 100% before "done", per Specification by Example / Eval-Driven Development). Auto-sizes from a single feature (1 design note + 1 PRD + 1 epic set) to a from-scratch program (full 7-doc set + 4 squads + waves). Use when the user says "/plan-it", "plan this", "plan-it this", "spec this out", "turn this into a delivery package", "create the PRDs/epics", "do discovery and planning", "
A perfectly parseable frontmatter whose name does not match its directory.
does the thing: with an unquoted colon that breaks YAML frontmatter parsing
| name | demo |
| description | plan-it: the planner that plans it before build-it builds it |
Body of the demo skill.
