gsd:plan-phase

You can break down a complex project phase by generating a detailed phase plan that organizes work into phases, waves, and tasks. This produces a validated phase-plan.md file to align teams on execution.

A phase plan is a structured document that breaks project development into manageable waves and tasks with traceability. You need one when initiating new development waves to ensure team alignment and reusable planning patterns.

Yes, you can reuse planning patterns across multiple projects to accelerate onboarding and planning quality. The generated phase plans are designed as reusable structures that maintain consistency in project management.

To generate a phase plan and store it in git, prompt the system to analyze your current wave and map codebase context. The planner agent produces a validated phase-plan.md file that can be committed directly to your repository.

Yes, this planning approach works without external dependencies. It relies on a dedicated planner agent to analyze the wave and map codebase context internally, producing a self-contained phase plan.

Project planning lacks traceability across development waves when phase plans are not structurally validated or committed to git. Generating a standardized phase-plan.md ensures structure validation and enables consistent traceability.