planning-and-task-breakdown

What problem does it solve? Large or vague work items cause agents and developers to start coding without a plan, producing tangled implementations and rework. This Skill turns a spec into a written plan with small, dependency-ordered tasks that each leave the system in a working state. ## Core Features & Use Cases - Structured Planning Process: Read-only plan mode, dependency graph mapping, and vertical slicing so each task delivers a complete, testable feature path. - Task Templates and Sizing: A standard task format with acceptance criteria, verification steps, dependencies, and XS-to-XL sizing rules that force oversized tasks to be split. - Plan and Task List Outputs: Saves the plan to tasks/plan.md and tasks to tasks/todo.md or an external tracker, with checkpoints between phases and protection against overwriting incomplete plans. - Use Case: Given a feature spec for user authentication, produce a phased plan where registration, login, and session handling are separate vertical slices, each with testable acceptance criteria and explicit checkpoints. ## Quick Start Ask the agent to read the feature spec and create an implementation plan with a broken-down task list in tasks/plan.md and tasks/todo.md before writing any code.