planning-and-task-breakdown

What problem does it solve? Large or vague development tasks often lead to tangled implementations, missed dependencies, and rework. This Skill turns a spec or clear requirements into a written plan of small, verifiable tasks before any code is written. ## Core Features & Use Cases - Dependency-Aware Task Ordering: Maps the dependency graph (schema, API, UI) and orders tasks bottom-up so foundations are built first. - Vertical Slicing: Splits work into complete feature slices that each deliver working, testable functionality instead of horizontal layers. - Structured Task Format: Every task includes acceptance criteria, verification steps, dependencies, files likely touched, and a size estimate (XS through XL). - Flexible Output Targets: Writes the plan to tasks/plan.md and the task list to tasks/todo.md by default, or to an external tracker like GitHub Issues, Jira, or Linear when the project designates one. - Use Case: Given a spec for a new user registration feature, produce a phased plan with tasks for schema, endpoint, and UI, each with testable acceptance criteria and checkpoints between phases. ## Quick Start Ask the agent to read the feature spec and break the work into an ordered task list with acceptance criteria saved to tasks/plan.md and tasks/todo.md.