planner

To turn feature specs into executable tasks, structured specifications located in ai/features/TYPE-XXX-*.md are processed and broken down into bite-sized tasks. This yields a plan_added status and a tasks_count value, preparing the output for an autopilot workflow.

The best way to break down software feature specifications is to enforce architectural structure and task boundaries, converting high-level specs into granular, bite-sized tasks. This process maintains code modularity and generates actionable task lists for sprints.

Yes, the planner supports structured software features with clear specs, specifically applying error handling and task distribution during the breakdown process. It requires feature specs to be located in ai/features/TYPE-XXX-*.md files.

You prepare implementation plans by providing a clear plan for a given feature spec to drive automated task creation. The system transforms the structured feature specifications into actionable, bite-sized tasks suitable for an autopilot workflow.

Feature specifications need to be in ai/features/TYPE-XXX-*.md files because the task generation mechanism relies on locating and parsing structured software features with clear specs from this specific directory structure to ensure accurate task distribution.

Other planning tools in the same category can generate task lists, but this approach specifically enforces architectural structure and task boundaries to maintain code quality. It directly yields a plan_added status and a tasks_count value tailored for the autopilot workflow.