interview-me

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users often ask for what they think they should want rather than what they actually need, leading to misaligned specs, plans, and code. This Skill closes the gap between the stated ask and the real intent before any building begins, 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 the user can react instead of generating answers from scratch. - Want vs. Should-Want Detection: Identifies convention-signaling and sophistication-signaling answers ("scalable", "best practice") and probes 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) that requires an explicit yes before any downstream spec or plan is written. - 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 entirely. ## Quick Start Ask the AI to interview you about your request before it starts planning, for example by saying "interview me before we start building this."

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, then restate the intent and get an explicit yes before planning.

When should I use an intent-clarification interview instead of just building?▼

Use it when the ask is missing who it's for, why it's needed, what success looks like, or the binding constraint. Skip it for unambiguous mechanical tasks like renames, typo fixes, or pure information requests.

Why ask one question at a time instead of a batch of questions?▼

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 correct as understanding evolves.

What counts as confirmation of user intent?▼

Only an explicit yes to a concrete restatement counts. "Whatever you think," "sounds good," or silence are delegation or polite exits, not confirmation, and should trigger a follow-up with concrete options.

Can this interview approach run in automated or CI pipelines?▼

No. It requires a live, responsive user and must not run in non-interactive contexts like CI pipelines, scheduled runs, or autonomous loops. In those contexts, flag the underspecified ask as a blocker instead of guessing.