loop-planner

To generate an execution plan from a spec file, you input your `spec.md` and project context. The system reads these inputs to automatically produce a `plan.md` file containing all necessary tasks and their acceptance criteria.

A dependency DAG maps task relationships to support both parallel and sequential execution. By creating a Directed Acyclic Graph, it identifies which development tasks can run simultaneously and which must wait, resolving potential execution conflicts.

The best way to prevent scope creep is through automated scope validation. This process identifies and flags any overlap with previously completed work, ensuring your development track stays within its original boundaries.

Yes, you can use this for managing agile development workflows. It automates creating detailed, phased execution plans that map dependencies and manage scope boundaries, ensuring all project requirements are met efficiently.

Yes, automated planning works with existing project context by reading it alongside your specifications. This allows the system to accurately identify scope boundaries and flag potential overlaps with work that has already been completed.

You should avoid automated dependency mapping for simple, linear tasks that do not require parallel execution or complex conflict resolution. It is designed for phased development tracks where managing overlapping scope and complex task sequences is necessary.