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 an increment cycle — implement, test, verify, commit — so every change lands in a working, testable state. ## Core Features & Use Cases - Increment Cycle Discipline: Each slice is implemented, tested, verified, and committed before the next begins, keeping the build green throughout. - Slicing Strategies: Provides vertical, contract-first, and risk-first slicing patterns for breaking features into deliverable pieces. - Scope and Simplicity Rules: Enforces one-thing-at-a-time commits, feature flags for incomplete work, safe defaults, and rollback-friendly changes. - Use Case: When building a task management feature, implement create, list, edit, and delete as four separate tested slices instead of one large commit. ## Quick Start Ask the AI to implement the next task from your plan incrementally, starting with just the backend slice, running the repository's tests after each step, and committing before moving to the UI.