interview-me

Extracts true user intent through one-question-at-a-time interviews before any plan or code exists.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill interview-me-qiuyi-hong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/Qiuyi-Hong/addyosmani-skills/tree/main/skills/interview-me
Command: npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill interview-me-qiuyi-hong

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 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 like "scalable" or "best practice" to surface what the user actually wants. - 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 tracker list, avoiding building the wrong artifact entirely. ## Quick Start Ask the agent to interview you about what you actually want before it starts planning or building your next feature.

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 feature requests 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, then restate the intent and get an explicit yes before planning or coding.

How to handle users who say build me X without details?

Treat conventional requests like "build me a dashboard" as underspecified. Interview the user about who it is for, why now, what success looks like, and the binding constraint before proposing any solution or architecture.

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 interactive user, so avoid it in CI pipelines or autonomous loops.

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

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 exposes your assumptions.

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. Re-ask with two concrete options or a sharper restatement until the user clearly confirms.