Planning

Build a plan through collaborative interrogation, then stress-test it adversarially, before coding starts. The deliverable is always a plan file, never code.

• IS: building a plan from intent through one-question-at-a-time interrogation (Create), and strengthening an existing plan by scoring six dimensions to 5/5 with claim verification (Review). Both write to the plan file.
• IS NOT: implementing or generating code, authoring a PR (use pr-creator), or reviewing a code diff (use pr-reviewer).

Pipeline position: planning (create then review) -> implementation -> pr-reviewer -> pr-creator -> pr-babysitter.

Mode dispatch

Auto-detect; do not ask unless genuinely ambiguous:

• No plan file in scope, or verbs like "create a plan", "plan this", "grill me", "think this through" -> Create mode.
• An existing plan in scope (a path, or a recent file in ~/.claude/plans/), or verbs like "review my plan", "stress test", "is this ready", "get this to 5/5", "verify this claim", "fact-check" -> Review mode.
• If the input turns out to be code or a diff rather than a plan, stop and route to pr-reviewer.

Create naturally hands off to Review; a plan is not ready for implementation until Review passes.