coder:plan-phase

An executable phase plan links project CONTEXT, ROADMAP, and STATE to define goals, tasks, and waves. It generates a PLAN.md file with must-haves and runtime verification criteria, ensuring implementation aligns with current project constraints and decisions.

Validating a phase plan involves running a plan-check validation step after generation. This process triggers revision loops if issues arise, ensuring the plan meets completion gates and runtime verification criteria before implementation begins.

Context-aware planning integrates by reading existing CONTEXT.md, ROADMAP.md, and STATE.md files. This ensures the generated phase plan reflects current architectural decisions, project state, and overarching milestones rather than planning in isolation.

Research documents are integrated through a research depth detection step during the workflow. The planner spawns subagents as needed to gather necessary context, ensuring the final plan includes accurate runtime verification criteria and must-haves.

A completion gate is a validation checkpoint defined in the phase plan output. It ensures that all must-haves and runtime verification criteria specified in the PLAN.md file are met before the phase is considered complete.

Structuring tasks into waves involves assigning implementation steps sequentially within the phase plan. The planner generates wave assignments alongside must-haves in the PLAN.md file, coordinating execution and runtime verification across the project phase.