What problem does it solve? Large features and multi-file changes often get written in one pass, leaving bugs hidden across hundreds of lines and the codebase broken between edits. This Skill enforces a disciplined implement-test-verify-commit cycle so every increment leaves the system in a working, testable state. ## Core Features & Use Cases - Increment Cycle: Implements the smallest complete piece, runs tests, verifies the build, commits, then moves 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, feature flags for incomplete work, safe defaults, rollback-friendly changes, and no out-of-scope cleanup. - Use Case: When adding a CRUD feature to a Flutter app, build one slice at a time (create, list, edit, delete), running flutter analyze and focused tests after each slice and committing each working increment separately. ## Quick Start Ask the agent to implement the next task incrementally, starting with only the data layer, running tests after each slice, and committing each verified increment before continuing.
