interview-me

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

665|3|Updated Sep 12, 2026
One-click install
npx skills add https://github.com/rizqinrr/viserys-agent --skill interview-me-rizqinrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/rizqinrr/viserys-agent/tree/main/skills/interview-me
Command: npx skills add https://github.com/rizqinrr/viserys-agent --skill interview-me-rizqinrr

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 before any plan or code exists. This skill closes that gap by interviewing the user one question at a time until the underlying intent is confirmed, preventing costly rework from building the wrong thing. ## Core Features & Use Cases - Hypothesis-Driven Questioning: 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: Probes past 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 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 one question at a time about what you actually want before it starts planning or writing 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 requirements before starting a project?

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 the next three questions, then restate the intent and get an explicit yes.

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 confirmation.

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. It also requires a live interactive user, so avoid it in CI pipelines or autonomous loops.

Why do users give answers that sound right but aren't what they want?

Users often pattern-match best-practice talk like "scalable" or "clean architecture" instead of stating actual needs. Counter this by asking what they would want if they didn't have to justify it to anyone.

What comes after confirming user intent in a development workflow?

Hand off to downstream skills based on the confirmed intent: idea-refine if the scope needs exploration, or spec-driven-development if the intent is concrete enough to write down as requirements. Planning and task breakdown follow after the spec.