interview-me

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

1|Updated Sep 4, 2026
One-click install
npx skills add https://github.com/SanHsien/agent-skills --skill interview-me-sanhsien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/SanHsien/agent-skills/tree/main/skills/interview-me
Command: npx skills add https://github.com/SanHsien/agent-skills --skill interview-me-sanhsien

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 agents silently fill in ambiguous requirements. This Skill closes that gap 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 explicit 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 Intent Output: Produces a structured restatement (Outcome, User, Why now, Success, Constraint, Out of scope) gated on an explicit yes, with a 95% confidence stop condition. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the agent interviews and discovers the real need is a personal experiment tracking list — a completely different artifact. ## Quick Start Ask the agent to interview you about an underspecified request, for example: "Interview me before we start — I think I want a reporting dashboard for the team."

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 software requirements before coding?

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 and get an explicit yes before writing any spec or code.

How to handle underspecified requests like "build me a dashboard"?

Treat conventional requests as hypotheses, not specifications. Ask who it is for, why now, and what success looks like, one question at a time. The interview often reveals the real need differs from the stated artifact, such as a list instead of a dashboard.

When should I not use a requirements interview approach?

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 it does not work in CI pipelines or autonomous loops.

Why does asking one question at a time work better than a batch?

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 attached guess, which is faster than generating answers from scratch and keeps your assumptions visible.

What counts as confirmation of user intent?

Only an explicit yes to a concrete restatement counts. "Whatever you think", "sounds good", or silence are delegation or polite exits, not confirmation. Restate with Outcome, User, Why now, Success, Constraint, and Out of scope, then re-confirm.