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 commits that are painful to review or revert. This Skill enforces a disciplined increment cycle so every change lands in a working, tested state. ## Core Features & Use Cases - Increment Cycle: Implements one small slice, then tests, verifies, and commits before moving to the next slice. - Slicing Strategies: Provides vertical slicing, contract-first slicing for parallel frontend/backend work, and risk-first slicing for uncertain components. - 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, implement create, list, edit, and delete as four separate end-to-end slices, each verified with the repository's test and build commands before committing. ## Quick Start Ask the agent to implement the feature incrementally, starting with only the database schema and API endpoint, running the test and build commands after each slice before moving on.