planner-dependency-graph

Wave analysis assigns tasks to execution phases within a dependency graph to maximize parallelism. It coordinates checkpoints and prefers vertical slices over horizontal layers to reduce bottlenecks and improve concurrent throughput.

To build a dependency graph, assign needs and creates for each task to map dependencies. Apply wave analysis to compute execution phases, grouping tasks into vertical slices to maximize parallel execution and minimize cross-feature delays.

Vertical slices are preferred over horizontal layers in task planning to maximize concurrent execution. Slicing vertically minimizes cross-feature delays and bottlenecks by enabling independent task completion within each dependency graph wave.

Specify file ownership for each task when constructing the dependency graph to avoid conflicts during parallel task execution. Assigning explicit ownership ensures deterministic planning and prevents overlapping modifications across execution waves.

Yes, dependency validation is supported through a CLI workflow that ensures deterministic planning. The workflow guides dependency detection and integration with the overall planning engine to validate the dependency graph before execution.

Dependency graph planning requires accurately recording all needs and creates for each task. Incomplete dependency mapping or unspecified file ownership will reduce parallelism and introduce execution conflicts, limiting the effectiveness of wave analysis.