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, testable 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. - 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 tested end-to-end and committed separately instead of one 500-line change. ## Quick Start Ask the agent to implement the feature incrementally, starting with just the database schema and API endpoint, running tests and the build before moving to the UI slice.