interview-me

Conduct one-question-at-a-time interviews to extract user intent with confidence scoring.

1|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Borisserz/FoodTracker --skill interview-me-borisserz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/Borisserz/FoodTracker/tree/main/.agents/skills/skills/interview-me
Command: npx skills add https://github.com/Borisserz/FoodTracker --skill interview-me-borisserz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you uncover the true user intent by guiding a focused, one-question-at-a-time interview until you achieve high confidence about the underlying goal.

Core Features & Use Cases

  • Hypothesis-driven questioning: start with a stated guess and attach a confidence score to surface gaps.
  • One-question-at-a-time flow: prevents batching and reduces assumption-driven design.
  • Restate and confirm: delivers a concrete, explicit intent ready for downstream planning or execution.

Quick Start

State a hypothesis and ask one clarifying question to begin the interview.

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 starting a project?▼

You can clarify underspecified requirements by conducting a one-question-at-a-time interview to extract true user intent, generating hypotheses, and scoring confidence until it reaches approximately 95% for explicit confirmation.

How do I conduct a one-question-at-a-time interview to surface hidden requirements?▼

Start by stating a hypothesis with an attached confidence score, then ask one clarifying question at a time, updating your confidence level until it reaches roughly 95% to trigger a structured restate for explicit confirmation.

When should I use hypothesis-driven questioning for requirement gathering?▼

Use hypothesis-driven questioning when requests are underspecified or when you explicitly invoke interrogation to surface hidden requirements, ensuring you attach a confidence score to your initial guess to identify and address information gaps.

What is the best way to reach high confidence in user intent without asking multiple questions at once?▼

The best way to reach high confidence is through sequential one-question prompts combined with continuous confidence scoring, stopping the interview process only when your confidence level hits around 95%.

Does this requirement interrogation approach work without batching multiple queries together?▼

Yes, the approach strictly enforces a one-question-at-a-time flow to prevent batching, deliberately reducing assumption-driven design by guiding a focused interview that surfaces the true underlying goal incrementally.