interview-me

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

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/authrain-cloud-abdullahformuli/agent-skills --skill interview-me-authrain-cloud-abdullahformuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/authrain-cloud-abdullahformuli/agent-skills/tree/main/skills/interview-me
Command: npx skills add https://github.com/authrain-cloud-abdullahformuli/agent-skills --skill interview-me-authrain-cloud-abdullahformuli

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, locking in the wrong solution before any plan, spec, or code exists. ## 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 of what the user would want if they 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 condition. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the skill interviews and discovers the real need is a personal experiment tracker list, avoiding building the wrong artifact. ## Quick Start Say "interview me before we start" or "stress-test my thinking" when your request is underspecified, and answer the agent's questions one at a time until it restates your intent for confirmation.

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.

What is the interview-me skill used for?

It extracts what users actually want instead of what they think they should want, using iterative questioning until roughly 95% confidence about the underlying intent. It runs before spec-writing, planning, or implementation skills.

When should I not use requirements interviewing?

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

Why does asking one question at a time work better than 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 attached guess, which is faster than generating answers from scratch.

How do I handle users who say whatever you think is best?

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