refine-plan

To turn a v1 project plan into agent-ready tasks, place the plan in the project root or docs/ directory. The process generates a structured Markdown document with task context, steps, complexity, dependencies, and explicit acceptance criteria.

A task dependency DAG is a directed acyclic graph mapping execution order. During project plan refinement, establishing a valid DAG ensures agent-ready tasks execute in the correct sequence without circular dependencies, starting with a bootstrap Task 0.

Yes, the refined project plan output supports integration with Linear or similar issue-tracking systems. Producing structured task-level artifacts with context and acceptance criteria enables end-to-end project execution within these workflow tools.

The best way to structure a v1 plan for automated task refinement is to place the initial plan document in the project root or docs/ directory. This allows the refinement process to parse the plan and output the structured document at docs/project-plan-refined.md.

Yes, plan refinement generates a Task 0 specifically to bootstrap the execution workflow. This task establishes the foundation of the dependency DAG and prepares the environment for subsequent agent-ready tasks.