What problem does it solve? Large or vaguely defined work items cause agents and developers to produce tangled, unverifiable implementations. This Skill turns a spec or clear requirements into an ordered set of small, testable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Structured Planning Process: Guides read-only plan mode, dependency graph mapping, and vertical slicing so each task delivers working, testable functionality. - Task Templates and Sizing: Provides a standard task format (description, acceptance criteria, verification, dependencies, files touched) plus sizing rules from XS to XL, with guidance on when to break tasks down further. - Flexible Output Targets: Writes the plan to tasks/plan.md and the task list to tasks/todo.md by default, or maps tasks onto external trackers like GitHub Issues, Jira, Linear, or beads when the project designates one. - Use Case: Given a spec for a new user registration feature, produce a phased plan where each task (schema, API, UI) is a vertical slice with acceptance criteria, ordered by dependency, with checkpoints after every 2-3 tasks. ## 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.
