design-first

# Design-First (Progressive Design Facilitation) ## The Problem AI jump requirement→implementation, make all design decision silent. Result: you review code while evaluate scope, architecture, integration, contracts, quality -- all tangled. Catch scope mismatch in 2-min design talk way cheaper than find buried in 400 lines generated code. Solution: rebuild whiteboard talk human pairs do natural -- progressive design levels before code. ## The 5 Levels Five levels, abstract→concrete. Each level surface decision category that otherwise buried in generated code. ### Level 1: Capabilities (The "What") **Purpose**: Confirm scope. Surface user-facing outcomes system need deliver. Shared vocabulary check -- ensure human and AI talk same feature, same boundaries. **Output format**: Numbered list user-facing capabilities, max 5. Each capability plain-language outcome, not implementation detail. **Boundary**: No components, no architecture, no technical detail. If capability mention specific technology, class, or data structure -- belong later level. This level answer only "what user get?" **Checkpoint**: "Does this Level 1 (Capabilities) look correct? Should I proceed to Level 2 (Components)?" ### Level 2: Components (The "Who") **Purpose**: Identify building blocks. What major pieces system, what each one responsible for? **Output format**: 3-5 components, each with single responsibility and one-line description. Include ASCII or Mermaid diagram showing how relate. Note ...