interview-me

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

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill interview-me-raishoemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/interview-me
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill interview-me-raishoemi

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: Identifies convention-signaling answers ("scalable", "best practice", "the standard approach") and probes what the user would want if they 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 actual need is a personal experiment tracking list, avoiding building the wrong artifact entirely. ## Quick Start Ask the agent to interview you about your request before it starts planning or writing any code.

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 covering outcome, user, success criteria, and constraints for explicit confirmation.

How to handle users who say 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, and what success looks like, attaching your own guess to each question so the user can react quickly rather than generate answers from scratch.

When should I not use a requirements interview approach?

Skip interviewing 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 runs.

Why do users give answers that sound right but are not what they want?

Users often pattern-match best-practice language like "scalable" or "clean architecture" instead of stating real goals. The counter is asking what they would want if they did not have to justify it to anyone, which surfaces actual intent over convention.

What counts as confirmation of user intent?

Only an explicit yes to a concrete restatement counts. Responses like "whatever you think is best", "sounds good", or silence are delegation or politeness, not confirmation, and require re-asking with concrete options or a sharper restatement.