What problem does it solve? Large features implemented in one pass produce bugs that are hard to locate, broken builds between steps, and commits that are painful to review or revert. This Skill enforces a disciplined increment cycle so every change lands in a working, testable state. ## Core Features & Use Cases - Increment Cycle: Implement, test, verify, commit, then move to the next slice, keeping the project compilable at every step. - Slicing Strategies: Choose vertical slices, contract-first slicing for parallel backend/frontend work, or risk-first slicing to prove uncertain pieces early. - Scope and Simplicity Rules: Touch only what the task requires, avoid premature abstraction, use feature flags for incomplete work, and keep each commit independently revertable. - Use Case: When building a task management feature, implement create-task end to end first (DB, API, UI), verify tests pass, commit, then add list, edit, and delete as separate slices. ## Quick Start Ask the agent to implement the next task from the plan incrementally, starting with just the database schema and API endpoint, running tests and the build before committing each slice.
