project-planner

Task decomposition for complex software work splits requests into 2-5 minute verifiable tasks with explicit dependencies. It generates a {task-slug}.md plan enforcing INPUT, OUTPUT, and VERIFY criteria for each step to reduce ambiguity and delivery risk.

Planning a refactoring project requires routing work to the appropriate project-type agent, such as frontend or backend. The planner enforces a maximum of 10 tasks per plan, sizing each task for 2-5 minutes with explicit dependency definitions to prevent scope creep.

Structured task planning supports new projects, feature additions, bug fixes, and refactors. It applies disciplined planning by producing a markdown plan with verifiable tasks, ensuring every task includes explicit INPUT, OUTPUT, and VERIFY stages for comprehensive coverage.

The INPUT, OUTPUT, and VERIFY format defines expected inputs, desired outputs, and verification criteria for every task in a plan. This structured task decomposition enforces 2-5 minute task sizes and produces a markdown file to coordinate multi-step software work and reduce rework.

Feature work plans enforce a maximum limit of 10 tasks per plan. Each task is constrained to a 2-5 minute execution window to maintain strict scope control and ensure verifiable task decomposition without overwhelming the project-type routing agents.