What problem does it solve? Large or vaguely defined work items cause agents and developers to start coding without a plan, producing tangled implementations, missed dependencies, and rework. This Skill turns a spec into a written plan with small, testable tasks before any code is written. ## Core Features & Use Cases - Structured Task Decomposition: Maps dependency graphs, slices work vertically into complete feature paths, and sizes each task (XS through XL) so nothing exceeds a single focused session. - Acceptance Criteria and Checkpoints: Every task gets testable acceptance criteria, verification steps, and dependency notes, with checkpoints after every 2-3 tasks to keep the system in a working state. - 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 new user authentication feature, produce an ordered task list covering schema, API, and UI slices, each with acceptance criteria, so implementation can proceed or be parallelized across agents. ## Quick Start Break this feature spec into an ordered task list with acceptance criteria and save the plan to tasks/plan.md.
