spec-firstlisted

# Spec-First Development A structured workflow for LLM-assisted coding that delays implementation until decisions are explicit. ## When This Activates - "Build X" or "Create Y" (new features/projects) - "Implement..." (non-trivial functionality) - "Add a feature that..." (multi-step work) - Any request requiring 3+ files or unclear requirements ## When to Skip - Single-file changes under 50 lines - Typo fixes, log additions, config tweaks - User explicitly says "just do it" or "quick fix" ## Core Principles 1. **Delay implementation until tradeoffs are explicit** — Use conversation to clarify constraints, compare options, surface risks. Only then write code. 2. **Treat the model like a junior engineer with infinite typing speed** — Provide structure: clear interfaces, small tasks, explicit acceptance criteria. Code is cheap; understanding and correctness are scarce. 3. **Specs beat prompts** — For anything non-trivial, create a durable artifact (spec file) that can be re-fed, diffed, and reused across sessions. 4. **Generated code is disposable; tests are not** — Assume rewrites. Design for easy replacement: small modules, minimal coupling, clean seams, strong tests. 5. **The model is over-confident; reality is the judge** — Everything important gets verified by execution: tests, linters, typecheckers, reproducible builds. ## The 6-Stage Workflow ### Stage A: Frame the Problem (conversation mode) **Goal:** Decide before you implement. Prompts that work: - "Lis