implementlisted

# Implement Execute the work described by a spec or tickets in thin vertical slices. Each slice cuts a complete path through every layer (schema, API, UI, tests) and lands green. Drive TDD within each slice; verify framework-specific patterns against official docs; subject non-trivial decisions to a fresh-context doubt cycle before they stand. ## When to use - Implementing work described by a spec, plan, or set of tickets. - Multi-file changes that should land one vertical slice at a time. - Framework-specific code where current docs determine correct patterns. - High-stakes or unfamiliar code where correctness matters more than speed. - Lightweight changes that don't need a spec — small config edits, mechanical renames/moves, project scaffolding (see `references/lightweight-changes.md`). **Not for:** changes needing design decisions (use `spec`); system architecture (use `architecture`); pure test-driven exploration or bugfix-via-test with no spec — red-green-refactor as the whole task (use `tdd`). Have a spec and want slice-by-slice implementation? That stays here, with TDD driven within each slice. ## Steps 1. **Read the spec or tickets.** Orient on what "done" means. Note any pre-agreed TDD seams — integration points where tests must exist before code lands. If versions are missing or ambiguous, ask; the version determines which patterns are correct. 2. **Slice the work vertically.** One demoable end-to-end path per slice, sized to a single fresh contex