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 implementation discipline so every change lands in small, verified, reversible 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 for parallel backend/frontend work, and risk-first slicing to de-risk uncertain components early. - Scope and Simplicity Rules: Enforces one logical change per commit, keeps the build green between slices, uses feature flags for incomplete work, and prevents out-of-scope refactoring. - Use Case: When building a task management feature, implement create-task end-to-end first (DB, API, UI), verify tests pass and commit, then add list, edit, and delete as separate committed slices. ## Quick Start Ask the agent to implement the feature incrementally, starting with just the database schema and API endpoint, running tests and the build before moving to the UI slice.
