What problem does it solve? Large or vague development tasks often lead agents and developers to start coding without a plan, producing 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 what depends on what and orders tasks bottom-up so foundations are built first. - Vertical slicing guidance: Splits work into complete feature slices (schema + API + UI) rather than horizontal layers, so every task delivers testable functionality. - Structured task format: Each task includes acceptance criteria, verification steps, dependencies, files likely touched, and a size estimate (XS through XL), with checkpoints between phases. - Flexible output targets: Writes the plan to tasks/plan.md and the task list to tasks/todo.md by default, or maps tasks onto an external tracker like GitHub Issues, Jira, or Linear when the project designates one. - Use Case: Given a spec for a group trip-planning feature, produce a phased plan where Task 1 delivers account creation end-to-end, Task 2 delivers login, and a checkpoint after every 2-3 tasks verifies tests pass and the build is clean. ## 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.
