What problem does it solve? Large features implemented in one pass produce bugs that are hard to locate, reviews that are hard to read, and rollbacks that are painful. This Skill enforces a disciplined increment cycle so every change lands as a small, tested, working slice. ## Core Features & Use Cases - Increment Cycle: A repeatable Implement → Test → Verify → Commit loop that keeps the codebase buildable after every slice. - Slicing Strategies: Vertical slices, contract-first slicing for parallel backend/frontend work, and risk-first slicing to surface uncertainty early. - Scope and Simplicity Rules: Guardrails against scope creep, premature abstraction, mixed-concern commits, and unflagged incomplete features. - Use Case: When building a task management feature, implement create-task end-to-end first (DB + API + UI), verify tests pass and commit, then move to list, edit, and delete as separate slices. ## Quick Start Ask the agent to implement the next task from the plan as one thin slice, starting with only the database schema and API endpoint, then run the repository's test and build commands before committing.
