What problem does it solve?
It prevents large, risky code drops by enforcing a disciplined approach to implementing changes in small vertical slices that remain working and verifiable after each step.
Core Features & Use Cases
- Increment cycle discipline: Implement, test, verify, then checkpoint or commit with recorded evidence after each slice.
- Vertical slice strategy: Build complete end-to-end paths through the stack (e.g., DB + API + UI) so each increment delivers user-visible value.
- Scope and risk escalation rules: Escalate unclear requirements, missing inputs, environment/permission constraints, and high-risk issues instead of forcing work that can’t be accepted.
- Quality gates per slice: Require build/test/typecheck/lint verification and documented results in project-local task and review files.
Use case examples
- Implementing a multi-file feature where a single PR would be too large to review or too likely to break things.
- Refactoring an existing system where you need ongoing verification to avoid regressions.
- Adding a new capability while backend and frontend must develop in parallel using contract-first slicing.
Quick Start
Use incremental-implementation when you are about to implement a change touching more than one file and you want to land it as a sequence of small, testable slices that leave the project in a buildable state after each increment.
