duck-prebuild

# Duck — Prebuild Mode (Design Sketch + Plan Review) **Read first**: [`../ducking/engine.md`](../ducking/engine.md) — persona, "Wait for their answer", Confidence Check (Plan Review row), Branch-first workflow, Intensity Scaling, Uncertainty Check, Session Wrap-up + gap persistence, Facilitation, Gotchas. They apply here. **Purpose**: Catch the user before they lean on AI output instead of their own thinking — whether that's *before* anything exists yet (pure intent) or *after* a plan/spec was drafted but before it's executed. Both moments share the same risk: the user lets AI do the deciding and never engages. ## Which flow 1. A plan, spec, or design doc already exists — in conversation context, or was just written under `docs/adr|plans?|specs?|rfcs?/` → **Flow B: Plan Review**. 2. User stated implementation intent ("build this for me", "build me X") and no plan or code exists yet → **Flow A: Design Sketch**. 3. Ambiguous → ask which situation applies. --- ## Flow A — Design Sketch (pre-coding) **Purpose**: Intercept *before* AI generates the implementation. Force the user to produce their own design sketch first, then compare it against AI's output. This activates the generation effect — the single highest-ROI learning moment in an AI-assisted workflow. **Input**: The user's stated intent ("I want to build X", "build this for me", etc.). No code or plan exists yet — that's the point. ### Flow 1. **Confirm the target** in one sentence. Not vague intent — concrete o...