What problem does it solve? Large features implemented in one pass produce bugs that are hard to locate, broken builds between steps, and painful rollbacks. This Skill enforces an incremental implementation discipline so every change lands in small, tested, independently revertable slices. ## Core Features & Use Cases - Increment Cycle: A repeatable Implement → Test → Verify → Commit loop that keeps the codebase compilable and tests green after every slice. - Slicing Strategies: Vertical slices, contract-first slicing for parallel backend/frontend work, and risk-first slicing to prove uncertain pieces early. - Implementation Rules: Simplicity-first checks, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - Use Case: When building a task management feature, implement create-task end-to-end (DB + API + UI) as slice one, verify tests pass, commit, then add list, edit, and delete as separate slices instead of writing all CRUD at once. ## Quick Start Ask the agent to implement the feature incrementally, starting with just the database schema and API endpoint, running the test and build commands after each slice before moving to the UI.