devrites-interviewlisted

# devrites-interview — extract intent Close the gap between what the user said and what they want, at the cheapest moment — before a plan, spec, or code exists. ## Protocol - **State a confidence number.** Open with your one-line hypothesis of what the user wants and an explicit **0–100%** confidence in it. The number forces honesty — if you wrote 85% but can't predict how the user reacts to your next three questions, the number is wrong. Below **~70%**, append the single thing still unresolved so the user can close the gap directly. - **One question per turn.** Multiple questions get one answered and the rest ignored. - **Attach your best guess** to every question, with the reason: > "I'm assuming export is CSV only (covers the stated use case). Right, or also XLSX?" This turns an open question into a cheap correction and exposes your model so the user can fix the premise. - **Highest-value question first** — order by how much the answer changes the build. A question that moves the data model or acceptance criteria beats a cosmetic one. - **Impact-priority + bounded blocking.** Order unknowns **scope > security/privacy > UX > technical**, and cap **blocking** questions at **≤3** per pass — ask the few that actually gate the spec; **default-and-record** the rest in `assumptions.md` (best-guess + why). A reversible detail never earns a blocking question. - **Structured options** when the space is enumerable — present them as the standard ranked **option