loop-planner

To generate an execution plan from a feature spec, you provide a spec.md document and the planner reads project context to produce a plan.md with phased tasks, acceptance criteria, and dependencies.

A DAG-based execution graph structures software plan tasks as a directed acyclic graph, enabling safe parallel execution where dependencies allow and coordinating shared resources across project tracks.

Sequencing tasks and dependencies for a new software track involves reading conductor and product references from spec.md and tracks.md to output a plan.md avoiding overlapping work across tracks.

Yes, you can use spec.md and tracks.md to avoid overlapping work because the planner assimilates context from these files and conductor references to ensure coordinated execution across parallel project tracks.

A phased execution plan artifact includes a DAG, phase structure, specific tasks, acceptance criteria, and metadata updates, providing a concrete actionable roadmap translated directly from feature specs.

You need a dependency graph for software project planning when managing new features or tracks that require coordinated task sequencing, safe parallelism, and clear acceptance criteria derived from spec documents.