phased-planning

Phased planning divides large projects into structured phases with clear success criteria and automated progression rules. It generates a master plan document, per-phase prompts, and completion templates that define what each phase delivers and when to move forward.

Yes. Phased planning creates copy-paste ready Claude Code prompts for each phase, enabling you to execute work streams autonomously. Each phase prompt includes context, objectives, and success criteria tailored to that stage.

A phased roadmap includes a master plan document, individual phase prompts, quick-start templates, success criteria checklists, and handoff documentation. These artifacts break complex work into sequential tasks with clear deliverables and progression rules.

Phased planning integrates architecture templates into each phase prompt, ensuring design decisions are documented and validated before moving to implementation. This prevents rework and aligns downstream phases with established architectural patterns.

Use phased planning for complex software, data, or integration projects where dependencies between work streams matter and architecture decisions must precede implementation. Flat lists lose context; phases preserve decision history and enable autonomous progression.

No. Phased planning starts with functional requirements and project goals, then generates master plans and templates. It works from high-level objectives and creates the structured documentation needed to guide implementation.