interview-me

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

Updated May 21, 2026
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill interview-me-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/interview-me
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill interview-me-nicorevo

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. This Skill closes that gap before any plan, spec, or code exists, when changing direction costs nothing. ## 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 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 agent interviews 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 request before writing any spec, plan, 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, 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. Re-ask with two concrete options framed as a choice, since the user delegating means they lack confidence too. Never accept it as a terminal answer to an intent interview.

When should I not use an intent interview before coding?▼

Skip it for unambiguous self-contained asks like renames or typo fixes, pure information requests, mechanical operations, or when the user explicitly prioritizes speed. Also avoid it in non-interactive contexts like CI pipelines or autonomous loops.

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.

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 out-of-scope items and require an explicit yes, not "sounds good."