interview-me

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

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill interview-me-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/interview-me
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill interview-me-moofonli

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-Want Detection: Identifies convention-signaling answers ("scalable", "best practice", "the standard approach") and probes what the user would want if they 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 condition. - Use Case: A user says "build me a dashboard for our metrics." Instead of proposing chart libraries, the Skill interviews them and discovers the actual 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 it starts planning, for example by saying "interview me about this feature idea before we write any code."

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.

When should I use requirements elicitation before specification?

Use it when the ask is missing who the user is, why they want it, what success looks like, or the binding constraint. It runs before spec-writing skills, since those assume you already know roughly what you want.

Can this interview approach run in CI pipelines or automated loops?

No. It requires a live, responsive user and must not run in non-interactive contexts like CI pipelines, scheduled runs, or autonomous loops. In those contexts, flag the underspecified ask as a blocker instead of guessing.

Why does one-question-at-a-time interviewing beat batching questions?

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers. Asking one at a time with a guess attached lets the user react quickly and keeps the framing from locking in wrong assumptions.

What are the limitations of intent-clarification interviews?

They add no value for unambiguous, self-contained tasks like renames or typo fixes, pure information requests, or mechanical operations. They also fail when users want speed over verification or when several rounds pass without confidence rising.