GSD Planner

Task breakdown and dependency analysis are automated by generating executable phase plans that assign execution waves to tasks and verify them against goals. The process utilizes a PLAN.md file to structure task creation and dependency resolution for your workflows.

Goal-backward verification in phase planning ensures must-haves are identified first and all generated tasks align directly with your objectives. This mechanism validates that every task within an execution wave contributes to the target goal before execution begins.

Dependency graphs and execution waves are generated by providing context and input to the planner for dependency resolution. It analyzes task relationships within your phase plans and assigns execution waves to map out the sequential feature development roadmap.

Yes, you must provide context and input for dependency resolution and task creation. The planner requires this contextual information to accurately generate dependency graphs, assign execution waves, and verify must-haves against your target objectives.

The best way to outline a feature development roadmap is creating a new plan using structured phase planning with task breakdown. This approach maps dependencies into execution waves and applies goal-backward verification to ensure alignment with development objectives.