incremental-implementation

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 prove uncertain pieces early. - Implementation Rules: Enforces simplicity-first design, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - Use Case: When building a task management feature, deliver create, list, edit, and delete as four separate tested slices instead of one large unverified change. ## Quick Start Ask the agent to implement the next task from your plan incrementally, starting with only the database schema and API endpoint, running the repository's test and build commands after each slice before committing.