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 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 so the codebase never stays broken. - Slicing Strategies: Choose vertical slices, contract-first slicing for parallel backend/frontend work, or risk-first slicing to prove uncertain pieces early. - Implementation Rules: Simplicity first, scope discipline, 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 create, list, edit, and delete as four separate end-to-end slices, each tested and committed, instead of one 500-line change. ## Quick Start Ask the agent to implement the next task from your plan incrementally, starting with only the database schema and API endpoint, then running the repository's test and build commands before moving to the UI slice.
