addy-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 to the next three questions, then restate the intent for explicit confirmation.

Interview first when the ask is missing who the user is, why they want it, what success looks like, or the binding constraint. Write the spec only after the user explicitly confirms a restated intent, since specs consume the intent this process produces.

No. The skill requires a live, responsive user and must not be invoked in non-interactive contexts like CI pipelines, scheduled runs, or autonomous loops. In those contexts, flag underspecified asks as blockers instead of guessing.

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers. One at a time lets the user react to your hypothesis, keeps framing correct, and spends their limited attention efficiently.

Only an explicit yes to a concrete restatement counts. "Whatever you think", "sounds good", or silence are not confirmation — they signal delegation or disengagement and require re-asking with concrete options or a refined restate.

Skip it for unambiguous self-contained asks like renames or typo fixes, pure information requests, mechanical operations, or when the user explicitly prioritizes speed over verification. Also skip it when you already have roughly 95% confidence.