interview-me

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

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill interview-me-jampissarandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/interview-me
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill interview-me-jampissarandev

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 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: 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) that requires an explicit yes before any downstream spec or plan is written. - 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 — a completely different artifact. ## Quick Start Ask the AI to interview you about your request before building anything, for example by saying "interview me about this 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 requirements before writing code?

State a one-sentence hypothesis of what the user wants 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 for explicit confirmation.

What is the best way to handle underspecified feature requests?

Treat requests like "build me a dashboard" as missing who, why, success criteria, and constraints. Interview the user one question at a time rather than filling gaps with assumptions, since assumptions made before coding become expensive rework later.

When should I not use a requirements interview approach?

Skip interviewing for unambiguous self-contained tasks like renames or typo fixes, pure information requests, mechanical operations, and non-interactive contexts like CI pipelines. Also skip when the user explicitly prioritizes speed over verification.

Why do users give misleading answers about what they want?

Users often pattern-match best-practice language like "scalable" or "clean architecture" instead of stating real needs. The counter is asking what they would want if they didn't have to justify it to anyone, which surfaces actual intent.

How do I know when requirements gathering is complete?

You are done when you can predict the user's reaction to the next three questions you would ask. The final gate is an explicit yes to a concrete restatement covering outcome, user, motivation, success, constraint, and out-of-scope items.