interview-me

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

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/nntoan/ultra-omp --skill interview-me-nntoan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/nntoan/ultra-omp/tree/main/packages/proflow/skills/interview-me
Command: npx skills add https://github.com/nntoan/ultra-omp --skill interview-me-nntoan

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 changing direction is still cheap. ## 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 the user can react instead of generating answers from scratch. - Want vs. Should-Want Detection: Probes convention-signaling answers ("scalable", "best practice") with questions like "what would you want if you didn't have to justify it?" - Confirmed Intent Restatement: Produces a structured restatement (Outcome, User, Why now, Success, Constraint, Out of scope) gated on an explicit yes, with a 95% confidence stop test. - 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 Ask the agent to interview you about your request before starting any planning or implementation work.

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

What is the best way to handle underspecified feature requests?▼

Treat the request as a hypothesis to test rather than a spec to implement. Interview the user one question at a time, watch for convention-signaling answers like "scalable" or "best practice", and confirm a structured restatement covering outcome, user, success, and constraints.

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 over verification. It also requires a live responsive user, so avoid it in CI pipelines or autonomous loops.

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, locking in wrong framing. One question at a time with an attached guess lets the user react quickly and keeps your assumptions visible.

How do I know when requirements gathering is complete?▼

You are done when you can predict the user's reaction to the next three questions you would ask, roughly 95% confidence. The final gate is an explicit yes to a concrete restatement; "whatever you think" or "sounds good" do not count as confirmation.