interview-me

Extracts underlying user intent through one-question-at-a-time interviews before planning or coding.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/visdomtech/skills --skill interview-me-visdomtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/visdomtech/skills/tree/main/interview-me
Command: npx skills add https://github.com/visdomtech/skills --skill interview-me-visdomtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users often ask for what they think they should want rather than what they actually need, and building on those unstated assumptions locks in the wrong solution. This Skill closes the gap between the stated ask and the real intent before any plan, spec, or code exists, when switching costs are still zero. ## Core Features & Use Cases - Hypothesis-Driven Interviewing: States a one-sentence hypothesis with an honest confidence number, then asks one focused question at a time with a guess attached so users can react instead of generating answers from scratch. - Want vs. Should-Want Detection: Probes past convention-signaling answers ("scalable", "best practice") with questions like "what would you actually want if you didn't have to justify it?" - Confirmed Statement of Intent: Produces a structured restate (Outcome, User, Why now, Success, Constraint, Out of scope) gated on an explicit yes, with a 95% confidence stop rule. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the Skill interviews them and discovers the real need is a personal experiment tracker list, avoiding building the wrong artifact entirely. ## Quick Start Say "interview me before we start" or "stress-test my thinking on this request" to begin a one-question-at-a-time intent extraction session.

Frequently Asked Questions about interview-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify vague user requirements before writing code?▼

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.

What should I do when a user says build me X without details?▼

Treat conventional requests like "build me a dashboard" as underspecified and interview before planning. Ask who it is for, why now, what success looks like, and what the binding constraint is, one question at a time.

When should I not use an intent-clarification interview?▼

Skip it for unambiguous self-contained asks like renames or typo fixes, pure information requests, mechanical operations, non-interactive contexts like CI pipelines, or when the user explicitly prioritizes speed over verification.

Why does asking multiple questions at once fail in requirements gathering?▼

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers. One question at a time with an attached guess lets users react quickly and keeps your assumptions visible and correctable.

How do I handle a user who says whatever you think is best?▼

Treat "whatever you think" as delegation, not confirmation, since it signals the user lacks confidence too. Re-ask with two concrete options framed as a choice rather than proceeding on an unverified assumption.