incremental-implementation

What problem does it solve? Large code changes written in one pass are hard to test, review, and revert. This Skill enforces a disciplined increment cycle so every slice of a feature is implemented, tested, verified, and committed before moving to the next. ## Core Features & Use Cases - Increment Cycle: A repeatable Implement → Test → Verify → Commit loop that keeps the codebase compilable and tests green after every slice. - Slicing Strategies: Vertical slices for end-to-end functionality, contract-first slicing for parallel backend/frontend work, and risk-first slicing to surface uncertainty early. - Implementation Rules: Simplicity-first checks, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - Use Case: When building a task management feature, implement create, list, edit, and delete as four separate verified slices instead of one large unreviewable change. ## Quick Start Ask the agent to implement the next task from the plan incrementally, starting with only the database schema and API endpoint, then running the test suite and build before moving to the UI slice.