interview-me

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill interview-me-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/interview-me
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill interview-me-sapatamuku-creator

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 changing direction costs nothing. ## 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 Detection: Probes sophistication-signaling answers ("scalable", "clean", "best practice") 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." Two interview questions reveal the actual need is a personal experiment tracking list, not a dashboard, avoiding building the wrong artifact. ## 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 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.

How to handle users who say "whatever you think is best"?▼

Treat it as delegation, not a decision, since the user lacks confidence too. Re-ask with two concrete options framed as a choice rather than proceeding on an unverified assumption.

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

Why ask one question at a time instead of 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 hypothesis and keeps the framing from locking in wrong assumptions.

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.