interview-me

Clarify ambiguous user requests through one-question interviews with confidence tracking.

Updated Aug 23, 2026

Search Tags:#requirements #discovery #clarification #interview #alignment #intent

Ready to run

npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill interview-me-meisijiya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/meisijiya/ohMeisijiyaCode/tree/main/skills/interview-me
Command: npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill interview-me-meisijiya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents premature planning by uncovering the user's real intent when a request is vague, conventional, or full of hidden assumptions.

Core Features & Use Cases

One-question interviews: Asks a single focused question at a time so the user can react to a concrete hypothesis instead of a vague survey.
Confidence-based pacing: Tracks when understanding is strong enough to stop, rather than continuing to guess.
Intent restatement: Summarizes outcome, user, why now, success, constraint, and out of scope before any spec or build work begins.
Use case: Use this when someone says "build me X," "make it better," or "stress-test my thinking" and the true goal is still unclear.

Quick Start

Use interview-me to ask one focused question at a time until you can restate the user's intent with high confidence and get an explicit yes.

Frequently Asked Questions about interview-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clarify ambiguous user intent before starting product implementation?▼

To clarify ambiguous user intent, you can use a one-question-at-a-time interviewing approach that tracks confidence and confirms a restatement with explicit scope boundaries before planning begins. This prevents premature implementation driven by hidden assumptions.

What is the best way to stop assumptions from forming too early in requirements discovery?▼

The best way to stop early assumptions in requirements discovery is to apply confidence-based pacing, asking a single focused question at a time so the user reacts to a concrete hypothesis rather than a vague survey, ensuring true alignment on intent.

How do requirements interviews work when a request is vague or convention-driven?▼

Requirements interviews work by sequentially presenting guessed hypotheses based on the vague request, tracking your confidence level, and stopping only when you can restate the outcome, user, and constraints with high certainty.

When do I need to restate intent with scope and out-of-scope boundaries?▼

You need to restate intent with scope and out-of-scope boundaries before any spec or build work begins, specifically when someone asks to build a feature or improve a process and the true goal remains unclear.

Can I use one-question interviews for stress-testing my product thinking?▼

Yes, you can use one-question interviews to stress-test your product thinking by reacting to focused questions that uncover hidden assumptions, validate guessed hypotheses, and ensure your request is fully aligned before execution.

What are the limitations of using intent clarification for underspecified requests?▼

A limitation of intent clarification is that it requires interactive chats to function, meaning it cannot process entirely static or one-way commands without the user's explicit confirmation to finalize the aligned restatement.