incremental-implementationlisted

# Incremental Implementation Build in thin vertical slices — implement one piece, test it, verify it, commit, then expand. Each increment leaves the system in a working, testable state. ## The Increment Cycle ``` Implement → Test → Verify → Commit (orchestrator, inline) → Next slice ``` For each slice: 1. **Implement** the smallest complete piece of functionality 2. **Test** — run the test suite (or write a test if none exists) 3. **Verify** — tests pass, build succeeds 4. **Commit** — descriptive message 5. **Next slice** — carry forward, don't restart ## Slicing Strategies **Vertical slices (preferred):** One complete path through the stack per slice. Each delivers working end-to-end functionality. **Risk-first:** Tackle the riskiest or most uncertain piece first. If it fails, you discover it before investing in the rest. **Contract-first:** Define API contract first, then backend and frontend can develop in parallel against it. ## Rules ### Simplicity First Before writing any code: "What is the simplest thing that could work?" Three similar lines is better than a premature abstraction. Implement the naive, obviously-correct version first. ### Scope Discipline Touch only what the task requires. Don't clean up adjacent code, refactor imports in files you're not modifying, or add features not in the spec. If you notice something worth improving, note it — don't fix it. ### One Thing at a Time Each increment changes one logical thing. Don't mix a new component, a r