interview-me

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

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

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 the user can react instead of generating answers from scratch. - Want vs. Should-Want Detection: Probes sophistication-signaling answers ("scalable", "clean", "modern") with the question "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 test. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the agent interviews and discovers the real ask is a personal experiment tracker list — a different artifact entirely. ## Quick Start Ask the agent to interview you about what you actually want before it starts planning or building your request.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I clarify ambiguous 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 is the best way to handle underspecified feature requests?▼

Interview the user before producing any plan, spec, or code. Ask questions one at a time rather than in batches, attach hypotheses to each question, and stop only when the user explicitly confirms a concrete restatement of intent.

When should I not use a requirements interview approach?▼

Skip it for unambiguous self-contained asks like renames or typo fixes, pure information requests, mechanical operations, or when the user explicitly prioritizes speed. It also requires a live user, so it cannot run 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. One question at a time lets the user react to each hypothesis and keeps the framing correct as understanding evolves.

How do I know when requirements gathering is complete?▼

Use the 95% confidence test: you are done when you can predict the user's reaction to the next three questions you would ask. Then write a structured restatement covering outcome, user, why now, success, constraint, and out of scope, and get an explicit yes.