interview-me

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/assafmanor/waypoint --skill interview-me-assafmanor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/assafmanor/waypoint/tree/main/.claude/skills/interview-me
Command: npx skills add https://github.com/assafmanor/waypoint --skill interview-me-assafmanor

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 changing direction is still cheap. ## 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 detection: Probes past convention-signaling answers ("scalable", "best practice", "whatever you think") to surface what the user actually wants. - 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 list of running experiments — a different artifact entirely. ## Quick Start Ask the agent to interview you about your request before building anything, for example: "Interview me about what I actually want before we start planning this 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 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.

How to handle users who say "whatever you think is best"?▼

Treat it as delegation, not a decision — the user lacks confidence too. Re-ask with two concrete options framed as a choice rather than proceeding on your own assumptions.

When should I not use a requirements interview approach?▼

Skip it for unambiguous self-contained asks like renames or typo fixes, pure information requests, mechanical operations, or when the user explicitly prioritizes speed over verification. It also requires a live, responsive user, so avoid it in CI pipelines or autonomous runs.

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

Batched questions get skimmed and produce 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 from locking in wrong assumptions.

How do I know when requirements gathering is complete?▼

Use the 95% confidence test: you are done when you can predict the user's reaction to the next three questions you would ask. Then write a structured restatement including an explicit out-of-scope line and confirm with an explicit yes.