interview-me

Clarify user intent through structured one-question-at-a-time interviews.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/Lauughter/Python_training --skill interview-me-lauughter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/Lauughter/Python_training/tree/main/.claude/skills/interview-me
Command: npx skills add https://github.com/Lauughter/Python_training --skill interview-me-lauughter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies user intent by conducting a structured, one-question-at-a-time interview until high confidence about the underlying need is reached.

Core Features & Use Cases

  • Hypothesis-driven questioning with attached guesses to surface assumptions early.
  • One-question-at-a-time iteration until near 95% confidence on intent is achieved.
  • Explicit restatement and required confirmation to lock in scope before proceeding.
  • Works best for underspecified asks or when the user invokes prompts like "interview me" or "grill me".

Quick Start

Begin by stating your hypothesis and confidence, then ask a single focused question with an attached guess and await the user's reaction.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I clarify underspecified requirements before building a plan?

Clarify underspecified requirements by conducting a structured, one-question-at-a-time interview that requires an upfront hypothesis and confidence level to surface assumptions before proceeding with any plan.

What is hypothesis-driven discovery and how does it work for stakeholder interviews?

Hypothesis-driven discovery is a clarification method where you state an initial assumption and confidence level, ask a single focused question with a guessed answer, and iterate until reaching near 95% confidence on user intent.

When should I use a one-question-at-a-time interview for requirements discovery?

Use a one-question-at-a-time interview when user asks are underspecified, when explicitly invoking interviewing prompts, or when you catch yourself filling in ambiguous requirements before any plan exists.

How do I ensure scope is locked in after clarifying user intent?

Ensure scope is locked in by using a final restatement of explicit outcomes for confirmation, which requires the user to validate the documented needs before moving forward with the project.

Does requirements clarification work without documenting an initial hypothesis?

Requirements clarification requires an upfront hypothesis and confidence level to function correctly, as the structured interview relies on attached guesses to surface assumptions and validate the underlying need.