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, tested, committed state. ## Core Features & Use Cases - Increment Cycle: Implement, test, verify, commit, then move to the next slice, keeping the codebase compilable at every step. - Slicing Strategies: Choose vertical slices, contract-first slicing for parallel backend/frontend work, or risk-first slicing to de-risk uncertain components early. - Guardrails: Rules for simplicity, scope discipline, feature flags, safe defaults, and rollback-friendly commits, plus red flags and common rationalizations to avoid. - Use Case: When building a task management feature, deliver it as four slices (create, list, edit, delete), each passing tests and committed separately, 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 schema and API endpoint, running tests and the build before moving to the UI slice.
