What problem does it solve? Large features implemented in one pass produce unreviewable diffs, hidden bugs, and broken builds. This Skill enforces a disciplined workflow where every change is delivered as a small, independently tested and committed slice, keeping the codebase working at every step. ## Core Features & Use Cases - Increment Cycle: A repeatable loop of implement, test, verify, commit, then move to the next slice, with a checklist covering tests, build, type checking, and linting. - Slicing Strategies: Guidance for vertical slices, contract-first slicing for parallel backend/frontend work, and risk-first slicing to de-risk uncertain components early. - Scope and Safety Rules: Enforces simplicity-first design, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - Use Case: When building a multi-file CRUD feature, implement one operation (e.g., create) end-to-end with passing tests and a commit before starting the next operation, instead of writing all four at once. ## Quick Start Ask the agent to implement the next task from the plan incrementally, starting with only the database schema and API endpoint, running the test and build commands after each slice before touching the UI.