planning-and-task-breakdown

What problem does it solve? Large or vague work items cause agents and developers to produce tangled, unverifiable implementations. This Skill turns a spec into an ordered plan of small tasks, each with explicit acceptance criteria, verification steps, and dependency mapping, so work stays reviewable and resumable across sessions. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits work into complete feature paths (schema + API + UI) instead of horizontal layers, so every task delivers testable functionality. - Task Sizing Guidelines: Classifies tasks from XS to XL with file-count heuristics and rules for when to break a task down further. - Plan Document Template: Provides a ready-to-use Markdown template with phases, checkpoints, risk tables, and open questions. - Use Case: Given a spec for a user registration feature, produce a task list where Task 1 covers the schema and model, Task 2 the API endpoint, and Task 3 the UI form, each with acceptance criteria and a checkpoint after Task 3. ## Quick Start Ask the agent to read the feature spec and produce an implementation plan with vertically sliced tasks, acceptance criteria, and checkpoints before writing any code.