interview-me

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill interview-me-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/MSC72m/DevForge/tree/main/skills/interview-me
Command: npx skills add https://github.com/MSC72m/DevForge --skill interview-me-msc72m

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, locking in the wrong solution before any plan, spec, or code exists. ## Core Features & Use Cases - Hypothesis-Driven Interviewing: States a one-sentence hypothesis with an honest confidence number, then asks one focused question at a time with a guess attached. - Want vs. Should-Want Detection: Probes convention-signaling answers ("scalable", "best practice") to surface what the user actually wants. - Confirmed Statement of Intent: Produces a structured restate (Outcome, User, Why now, Success, Constraint, Out of scope) gated on an explicit yes. - 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, avoiding building the wrong artifact. ## Quick Start Say "interview me before we start" or "stress-test my thinking" when your request feels underspecified, and answer the agent's questions one at a time until it restates your intent for confirmation.

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 an intent-clarification interview skill?▼

Use it when a request is missing who the user is, why they want it, what success looks like, or the binding constraint. Skip it for unambiguous mechanical tasks like renames, typo fixes, or pure information requests.

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.

Can this skill run in CI pipelines or autonomous loops?▼

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

What counts as confirmation of user intent?▼

Only an explicit yes to a concrete restatement counts. Responses like "whatever you think is best", "sounds good", or silence are delegation or polite exits, not confirmation, and require follow-up with concrete options or refinement.

What are the limitations of interview-based requirement gathering?▼

It depends on user availability and honest engagement, and polite users may agree with guesses to be agreeable. If several rounds pass without rising confidence, something foundational is missing and the interview should pause to reframe.