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 missed requirements. This Skill turns a spec into an ordered list of small, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Dependency Mapping: Identifies what depends on what (schema, API, UI) so implementation follows a bottom-up order. - Vertical Slicing: Splits work into complete feature slices rather than horizontal layers, so every task delivers testable functionality. - Task Sizing and Checkpoints: Provides sizing guidelines (XS to XL), a plan document template, and verification checkpoints between phases. - Use Case: Given a spec for a new user registration feature, produce a phased plan where each task lists acceptance criteria, verification commands, dependencies, and files likely touched, with a human review checkpoint before implementation begins. ## Quick Start Ask the agent to read the feature spec and produce an implementation plan with ordered tasks, acceptance criteria, and checkpoints before writing any code.