interview-me

State a one-sentence hypothesis with a confidence number, then ask one focused question at a time with your best guess attached. Continue until you can predict the user's reactions, then restate the intent covering outcome, user, success criteria, and constraints for explicit confirmation.

Treat conventional requests like "build me a dashboard" as underspecified and interview before planning. Attach guesses to each question so users react rather than generate answers, and watch for answers that pattern-match best practices instead of stating real needs.

Skip it for unambiguous self-contained tasks like renames or typo fixes, pure information requests, mechanical operations, or when the user explicitly prioritizes speed. It also requires a live responsive user, so avoid it in CI pipelines or autonomous runs.

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers. Single questions with attached guesses let users react quickly, expose your assumptions, and keep the framing correct as the interview progresses.

Confirmation requires an explicit yes to a concrete restatement covering outcome, user, why now, success, constraint, and out of scope. Responses like "whatever you think" or "sounds good" are delegation or ambiguity, not confirmation, and require re-asking with concrete options.