plan-orchestrated

Generating a phased implementation plan involves breaking down software features into sequential and parallelizable phases with dependency graphs and wave-based tasking. It defines goals, non-goals, and complexity ratings, outputting a structured project management roadmap.

Wave-based tasking in project management organizes implementation tasks within phases into sequential waves for efficient parallel execution. It groups related software development tasks together, enabling teams to execute independent code generation activities concurrently.

Implementation planning can mandate a dead code removal and legacy reference review phase before new feature development begins. Including this phase ensures the codebase is cleaned of obsolete references before subsequent software development phases execute.

Yes, you can map task dependencies visually in a software development plan by generating dependency graphs for each phase. Visual dependency mapping represents how implementation tasks and feature phases rely on one another to establish a clear execution order.

The best way to structure goals and non-goals for a coding project is to define them explicitly at the start of a phased implementation plan. Separating project goals from non-goals establishes strict scope boundaries for subsequent software development and task management activities.

The generated implementation plan gets saved directly to the spec/plan.md file. Outputting the project management roadmap, dependency graphs, and task waves to this markdown file ensures the software development documentation remains accessible for future code reference.