What problem does it solve? Large features implemented in one pass produce bugs that are hard to locate, reviews that are hard to read, and rollbacks that are painful. This Skill enforces a disciplined implement-test-verify-commit cycle so every change lands as a small, working, independently revertable increment. ## Core Features & Use Cases - Increment Cycle: A repeatable loop of implement, test, verify, commit, then move to the next slice, keeping the codebase compilable at every step. - Slicing Strategies: Vertical slices for end-to-end functionality, contract-first slicing for parallel backend/frontend work, and risk-first slicing to de-risk uncertain components early. - Scope and Simplicity Rules: Guardrails against scope creep, premature abstraction, mixed-concern commits, and unflagged incomplete features. - Use Case: When building a task management feature, deliver it as four slices (create, list, edit, delete), each tested and committed separately, instead of one 500-line changeset. ## Quick Start Ask the agent to implement the next task from your plan incrementally, starting with just the database schema and API endpoint, running tests after each slice before touching the UI.
