interview-me

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

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

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 building on those unstated assumptions locks in the wrong solution. This Skill closes the gap between the stated ask and the real intent 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 percentage, 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: Probes past convention-signaling answers ("scalable", "clean architecture", "best practice") to surface what the user actually wants. - Confirmed intent restatement: 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 them and discovers the real need is a personal experiment tracker list — a completely different artifact. ## Quick Start Ask the agent to interview you about your next feature request before writing any spec or code, for example by saying "interview me about the dashboard I want to build."

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 percentage, 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 best way to handle underspecified requirements in AI-assisted development?

Use an intent-extraction interview before any spec or plan exists. Ask questions one at a time, attach hypotheses the user can react to, and stop only when you reach roughly 95% confidence about the underlying intent.

When should I not use a requirements interview approach?

Skip it for unambiguous self-contained tasks 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 runs.

Why does asking multiple questions at once fail in requirements gathering?

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers. One question at a time with an attached guess lets users react quickly and keeps the framing correct as understanding evolves.

How do I know when requirements gathering is complete?

You are done when you can predict the user's reaction to the next three questions you would ask, which indicates roughly 95% confidence. Then write a structured restatement covering outcome, user, motivation, success, constraint, and out-of-scope items, and require an explicit yes.