interview-me

Extracts underlying user intent through one-question-at-a-time interviews until 95% confidence.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/yourlabpt/yourlabpt_website --skill interview-me-yourlabpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/yourlabpt/yourlabpt_website/tree/main/projects/skills/interview-me
Command: npx skills add https://github.com/yourlabpt/yourlabpt_website --skill interview-me-yourlabpt

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 an explicit hypothesis with a 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-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) gated on an explicit yes, ready for handoff to spec-writing or planning skills. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the Skill interviews them and discovers the real need is a personal experiment tracker list, avoiding building the wrong artifact entirely. ## Quick Start Ask the agent to interview you about your request before writing any plan, spec, or code, for example by saying "interview me about this feature idea before we start."

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 to your next three questions, then restate the intent for explicit confirmation.

What is the best way to gather requirements from stakeholders?▼

Ask questions one at a time rather than in batches, and attach a hypothesis to each so stakeholders react instead of generating answers from scratch. Watch for convention-based answers like "best practice" and probe what they would want without justification.

When should I not use an intent-clarification interview?▼

Skip it for unambiguous self-contained asks like renames or typo fixes, pure information requests, mechanical operations, and non-interactive contexts like CI pipelines or scheduled runs. Also skip it when the user explicitly prioritizes speed over verification.

Why does requirement gathering fail even after the user says yes?▼

Answers like "whatever you think" or "sounds good" are delegation or polite exits, not confirmation. Restate the intent concretely with outcome, user, success criteria, constraints, and out-of-scope items, then require an explicit yes.

How do I know when I have asked enough discovery questions?▼

Use the 95% confidence test: you are done when you can predict the user's reactions to the next three questions you would ask. If several rounds pass without rising confidence, stop and tell the user something foundational is missing.