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 so every change lands as a small, verifiable, revertable slice. ## Core Features & Use Cases - Increment Cycle: Implement, test, verify, commit, then move to the next slice, keeping the codebase compilable and tests green at every step. - Slicing Strategies: Choose vertical slices, contract-first slicing for parallel backend/frontend work, or risk-first slicing to prove the riskiest piece early. - Scope and Simplicity Rules: Enforces one logical change per commit, feature flags for incomplete work, safe defaults, and rollback-friendly changes. - Use Case: When building a task management feature, deliver CRUD as four separate end-to-end slices (create, list, edit, delete), each tested and committed independently instead of one 500-line change. ## Quick Start Implement the next task from the plan incrementally, starting with just the database schema and API endpoint, then run the repository's test and build commands before committing.
