interview-me

Extracts true user intent through one-question-at-a-time interviews before any plan or code exists.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/ulebule/claude-skills --skill interview-me-ulebule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/ulebule/claude-skills/tree/main/plugins/interview-me/skills/interview-me
Command: npx skills add https://github.com/ulebule/claude-skills --skill interview-me-ulebule

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 with assumptions. 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 detection: Probes convention-signaling answers ("scalable", "best practice") with questions like "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 Skill interviews and discovers the real ask is a personal experiment tracker list — a completely different artifact. ## Quick Start Ask the agent to interview you about your next underspecified request, for example by saying "interview me before we start building the reporting feature."

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 and get an explicit yes.

How to run a requirements interview with a user one question at a time?

Ask a single focused question per message and attach your hypothesized answer with reasoning. Batching questions encourages skim-reading and locks in wrong framings; reacting to a wrong guess is faster for users than generating answers from scratch.

When should I not use a requirements interview process?

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

Why does asking users what they want produce wrong answers?

Users often state what a thoughtful answer sounds like — buzzwords like "scalable" or "best practice" — rather than what they actually want. Probe with "what would you want if you didn't have to justify it to anyone?" to surface real intent.

What are the limitations of interview-based intent extraction?

It depends on an interactive user and cannot run in non-interactive contexts like scheduled jobs. Polite users may agree with guesses to be agreeable, and vague confirmations like "sounds good" or "whatever you think" do not count as validated intent.