One-click install
npx skills add https://github.com/koolerkx/vibe-react-2d-map-editor-yaml --skill interview-me-koolerkx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/koolerkx/vibe-react-2d-map-editor-yaml/tree/main/.claude/skills/interview-me
Command: npx skills add https://github.com/koolerkx/vibe-react-2d-map-editor-yaml --skill interview-me-koolerkx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts what the user actually wants instead of what they think they should want. It achieves this through a one-question-at-a-time interview until ~95% confidence about the underlying intent.

Core Features & Use Cases

  • Hypothesis-driven discovery: starts from a hypothesis and tests it via targeted questions.
  • One-question-at-a-time probing: surfaces missing details with minimal cognitive load.
  • Restate & confirm: presents a concise restatement of the intended outcome and requires an explicit yes before proceeding.
  • Downstream integration: pairs with other discovery/definition skills like idea-refine or spec-driven-development.

Use cases include clarifying underspecified asks, surfacing who/why/constraints, and guiding safe, incremental decision making.

Quick Start

Start by stating a hypothesis about the user's goal, then ask your first clarifying question.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I clarify user intent during product discovery interviews?

To clarify user intent during product discovery interviews, use a one-question-at-a-time probing approach. This method tests initial hypotheses and surfaces missing details with minimal cognitive load until approximately 95% confidence about the underlying goal is achieved.

What is the best way to uncover actual user needs instead of what they think they want?

Hypothesis-driven discovery extracts actual user needs by asking targeted, one-question-at-a-time prompts. This incremental interview process surfaces hidden constraints and the true underlying intent behind an initial request.

How do I conduct a question-driven discovery workflow for requirements gathering?

Conduct a question-driven discovery workflow by starting with a hypothesis about the user's goal, then asking sequential clarifying questions. Once confidence is high, generate a concise restate of the intended outcome and require an explicit confirmation before proceeding.

Can I use intent clarification to handle underspecified product management requests?

Yes, intent clarification is designed for underspecified product management requests. By probing one question at a time, it safely guides incremental decision making and reveals who, why, and constraint details that are initially missing.

How does the restate and confirm mechanism work in user research?

The restate and confirm mechanism presents a concise restatement of the intended outcome once probing concludes. It requires an explicit yes from the user before moving to downstream steps, ensuring accurate requirements discovery.

When should I not use a one-question-at-a-time interview approach?

Avoid a one-question-at-a-time interview when you already possess over 95% confidence regarding the user's intent, or when downstream definition and specification skills require immediate integration without incremental discovery.