interview-me

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill interview-me-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/templates/skills/interview-me
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill interview-me-kunj-sharma03

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 agents to build the wrong artifact from underspecified requests. 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 explicit 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 Detection: Probes sophistication-signaling answers ("scalable", "clean", "best practice") with the question "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 checkable stop condition based on predicting the user's next three reactions. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the agent interviews 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 starting any planning or coding, for example by saying "interview me before we start building 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 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 your next three questions, then restate the intent for explicit confirmation.

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

Treat it as delegation, not a decision, since the user lacks confidence too. Re-ask with two concrete options framed as a choice rather than proceeding on an unconfirmed assumption.

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

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

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.

How do I know when requirements gathering is complete?

Use the checkable test: can you predict the user's reaction to the next three questions you would ask? If yes, restate the intent and get an explicit yes. If several rounds pass without rising confidence, step back and flag that something foundational is missing.