01 ▸ Workflow Position
User Request (Vague)
│
▼
Clarification
│
▼
┌─────────────────────────────┐
│ plan-crafting (ACTIVE) │
│ Plan Creation + Code │
└──────────────┬──────────────┘
│
▼
run-plan
│
▼
review-work
02 ▸ When to use?
Immediately after Clarification is completed with a Simple (5-8 points) verdict. Or call directly when the scope is already clear.
Key Triggers
- When
"make a plan" or "create plan" commands are used
- When a Context Brief file is ready
- When you have a clear goal + scope and need a step-by-step plan
Input/Output
Input: Context Brief file (output of clarification)
Output: Executable plan document (file mapping + task decomposition)
03 ▸ How it works?
Core Principle: A plan is an execution document. A step without code is a plan defect.
Execution Steps
- Explore Verification Infrastructure: e2e, integration, test suites, builds — find the highest level of verification to determine the Final Verification Task.
- Map File Structure: Group related file changes in the same task, separate different responsibilities.
- Task Decomposition — Worker-Validator structure: Serial tasks for the same file, parallel tasks for independent work.
- Actual Code in Every Step: TBD, TODO, "Add appropriate error handling" — all forbidden.
- Self-Review: Check specification coverage, type consistency, dependency verification, and validation coverage.
04 ▸ Forbidden Placeholders
TBD, TODO, implement later — plan defects- "Add appropriate error handling" — defect without specific code
- "Similar to Task N" — actual code must be repeated
05 ▸ Hard Gates
- Every step must be executable: Placeholders are never allowed.
- Prevent Task Collisions: Tasks modifying the same file cannot run in parallel.
- Mandatory Self-Review: Must verify completeness of the plan after drafting.
- Minimum Functional Decomposition: Each task must produce one clear artifact.