gsd-plan-phase

To plan a project phase, you extract phase objectives from your roadmap, identify dependencies, specify deliverables, and generate a detailed execution plan. This creates a structured phase blueprint with verification criteria and rollback options.

Documenting phase objectives involves generating per-phase plans that include descriptions, steps, verifications, and rollback options. The output is a structured markdown overview file that records the phase plan and success criteria.

You generate an execution plan by providing a target phase number. The system then extracts the corresponding roadmap objectives, identifies dependencies, and outputs a comprehensive phase plan document.

Yes, when you generate a phase plan, the system automatically updates your project's state file with the current phase number, ensuring your project tracking reflects the newly planned phase.

Yes, phase planning is designed for complex projects using a phased roadmap, requiring phase objectives, dependencies, deliverables, and verification criteria to organize and execute each distinct phase clearly.

The phase planning output uses markdown files to document the phase overview, plans, dependencies, and success criteria, storing them in a dedicated planning directory structure.