incremental

# Incremental Implementation ## Overview Build in thin vertical slices. Implement one piece, test it, verify it, then expand. Each increment MUST leave the system in a working, testable state. Slicing this way keeps large features tractable. ## When to Use - Implementing any multi-file change - Building a new feature from a task breakdown - Refactoring existing code - Any time you're tempted to write more than ~100 lines before testing **When NOT to use:** Single-file, single-function changes where the scope is already minimal. ## The Increment Cycle ``` ┌──────────────────────────────────────┐ │ │ │ Implement ──→ Test ──→ Verify ──┐ │ │ ▲ │ │ │ └───── Commit ◄─────────────┘ │ │ │ │ │ ▼ │ │ 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**: confirm the slice works: tests pass, build succeeds, manual check holds. 4. **Commit**: save progress with a descriptive message; keep the commit atomic (one logical change). 5. **Move to the next slice**: carry forward, never restart. ## Slicing Strategies ### Vertical Slices (preferred) Build one complete path through the stack: ``` Slice 1: Create ...