plan

To convert a design into a phased implementation plan, provide the chosen design to generate a plan.md file alongside phase-XX-*.md files. This codifies milestones, ownership, deliverables, and review history for repeatable execution.

Phased planning for project management breaks a decided approach into sequenced phases with explicit tasks, milestones, and artifacts. It generates documentation including plan.md and phase-XX-*.md files to track ownership, dependencies, and success criteria.

You document project risks and dependencies by generating phase-XX-*.md files during the planning process. These artifacts codify phase definitions, ownership, dependencies, success criteria, and risk notes for each implementation stage.

Yes, the planning mode affects the generated artifacts by adjusting the scope and risk depth. You can choose quick, default, or deep modes to match your project requirements when generating the plan.md and phase-XX-*.md files.

To generate a concrete implementation plan, you need a complete, actionable design as input. Feeding this design into the planner produces the plan.md and per-phase artifacts required to define milestones, file changes, and success criteria.

You should use deep planning mode instead of quick mode when your project scope and risk levels are high. Deep mode provides a more thorough breakdown of phases, tasks, and artifacts compared to the quick mode for streamlined execution.