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 in small, verifiable slices that keep the codebase working at all times. ## Core Features & Use Cases - Increment Cycle: A repeatable loop of implement, test, verify, commit, then move to the next slice, with a checklist covering tests, build, type checking, and linting. - Slicing Strategies: Vertical slices for end-to-end functionality, contract-first slicing for parallel backend/frontend work, and risk-first slicing to prove the riskiest piece early. - Implementation Rules: Simplicity-first checks, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits, plus anti-rationalization tables and red flags. - Use Case: When building a task management feature, deliver it as four slices (create, list, edit, delete), each tested and committed independently, 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 and API slice, running the repository's test and build commands before committing each slice.
