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 increment cycle — implement, test, verify, commit — so every change lands in small, working, revertable slices. ## Core Features & Use Cases - Increment Cycle: A repeatable loop of implementing the smallest complete piece, running tests, verifying the build, and committing before moving to the next slice. - Slicing Strategies: Vertical slices for end-to-end functionality, contract-first slicing for parallel backend/frontend work, and risk-first slicing to validate the riskiest piece early. - Implementation Rules: Simplicity-first checks, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - 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 change. ## Quick Start Ask the agent to implement the next task from your plan incrementally, starting with just the database schema and API endpoint, running the test and build commands after each slice before touching the UI.
