dev-plan

To turn design docs into actionable dev plans, provide your setup.yaml and design artifacts to generate concrete task lists, per-task TDD prompts, and a parent-agent integration prompt for orchestration. It automatically translates these inputs into a structured implementation plan.

Yes, you can automate task splitting from a design document by processing it alongside setup.yaml. The system reads these inputs to produce a task breakdown with defined dependencies, parallelizable groups, and acceptance criteria to guide completion.

You generate parent-agent prompts for development orchestration by feeding design-document and dev-design outputs into the planning process. It creates individual task prompts with TDD guidance and an integration prompt to coordinate the parent agent.

The best way to manage dependencies in a development task plan is to enforce acceptance criteria from setup.yaml during generation. This defines parallelizable groups and updates the design document with structured references for traceability.

Yes, you need setup.yaml to generate a task list with TDD guidance. It provides the required acceptance criteria to guide task completion, while the system reads setup.yaml and design artifacts to produce the task breakdown and prompts.