What problem does it solve? Large features and multi-file changes often fail because too much code is written before anything is tested, making bugs hard to locate and rollbacks painful. This Skill enforces an incremental delivery discipline so every change lands in small, verified, revertable steps. ## Core Features & Use Cases - Increment Cycle: Implements one thin slice at a time, then tests, verifies, and commits before moving to the next slice. - Slicing Strategies: Provides vertical slicing, contract-first slicing, and risk-first slicing patterns for different project shapes. - Implementation Rules: Enforces simplicity-first design, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - Use Case: When building a new CRUD feature spanning database, API, and UI, deliver it as four end-to-end slices (create, list, edit, delete), each leaving the build green and the test suite passing. ## Quick Start Ask the agent to implement the next task from your plan incrementally, starting with only the database schema and API endpoint, running tests and the build before committing each slice.
