What problem does it solve? Large or vague development requests lead agents to make hundreds of invisible decisions that surface as bugs later. This Skill turns a spec or feature request into a structured plan document of small, independently verifiable tasks before any code is written. ## Core Features & Use Cases - Vertical task slicing: Breaks work into complete, testable slices (schema + API + UI) rather than horizontal layers, each passing a six-point "small enough" definition. - Dependency and conflict mapping: Builds a logic map of task dependencies and shared surfaces (files, stores, API contracts) to justify sequential vs. parallel scheduling. - Reuse review: Searches the codebase for existing components, stores, and endpoints so the plan extends what exists instead of duplicating it. - Use Case: Given a request like "add user registration", produce a references/build-registration.md plan with phased tasks, acceptance criteria, review checks, checkpoints, and risk mitigations ready for a builder agent to execute. ## Quick Start Ask the agent to plan the work: "Break the user registration feature into an implementation plan with ordered tasks and acceptance criteria."