incremental-implementation

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 — implement, test, verify, commit — so every change lands in small, working, revertable slices. ## Core Features & Use Cases - Increment Cycle Discipline: Each slice is implemented, tested, verified, and committed before moving to the next, keeping the codebase always buildable. - Slicing Strategies: Provides vertical slicing, contract-first slicing for parallel frontend/backend work, and risk-first slicing to surface uncertainty early. - Scope and Simplicity Rules: Enforces 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 it as four slices — create, list, edit, delete — each passing tests and committed separately, instead of one 500-line change. ## Quick Start Implement the next task from my plan incrementally, starting with just the database schema and API endpoint, and run the test suite after each slice before committing.