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 out-of-scope items for explicit confirmation.

Ask one question at a time rather than batching, attach your hypothesis to each question so the stakeholder can react quickly, and watch for convention-driven answers like "best practice" or "scalable." End with a structured restatement they must explicitly confirm.

Skip it for unambiguous self-contained asks 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 it does not work in CI pipelines or autonomous runs.

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers, locking in wrong framing. One question at a time with an attached guess lets the user react to a concrete hypothesis instead of generating answers from scratch.

Only an explicit yes to a concrete restatement counts. Responses like "whatever you think is best," "sounds good," or silence are delegation or polite exits, not confirmation, and require re-asking with concrete options or a refined restatement.