incremental-implementationlisted

# Incremental Implementation Build one working slice at a time. Never do everything in one pass. ## Progress Checklist - [ ] Break work into vertical slices - [ ] For each slice: implement, test, verify, commit - [ ] Codebase always in working state between slices - [ ] Self-review before PR (trigger code-review) - [ ] Create PR (trigger make-pr) ## What's a Vertical Slice? A slice delivers a working increment of user-facing behavior, cutting through all layers: **Good slices** (vertical - end to end): - "User can log in with email and password" - "Dashboard shows a list of projects" - "API returns paginated search results" **Bad slices** (horizontal - one layer only): - "Add auth middleware" (no endpoint uses it yet) - "Create database schema" (no code reads from it yet) - "Build the form component" (no API to submit to) Each slice should be deployable on its own, even if the full feature isn't complete. ## How to Slice 1. Start with the simplest end-to-end path (happy path) 2. Add error handling and edge cases as subsequent slices 3. Add optimization and polish as final slices Example for "user registration": 1. Slice 1: Form submits, API creates user, returns success 2. Slice 2: Input validation (client and server) 3. Slice 3: Email verification flow 4. Slice 4: Error handling (duplicate email, network failure) 5. Slice 5: Loading states, success feedback, redirect ## The Loop For each slice: ### 1. Implement Write the minimum code for this slice. Don't half-