interview-me

Extracts user intent through one-question-at-a-time interviews until 95% confidence.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill interview-me-22teikk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/22Teikk/22Teikk-Agent-Skills-Hub/tree/main/core/skills/interview-me
Command: npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill interview-me-22teikk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users often ask for conventional solutions ("build me a dashboard") that don't match what they actually want, and agents silently fill in ambiguous requirements with assumptions. This Skill closes the gap between the stated ask and the real intent before any plan, spec, or code exists, when switching costs are still zero. ## Core Features & Use Cases - Hypothesis-driven questioning: States a one-sentence hypothesis with an explicit confidence number, then asks one focused question at a time with a guess attached so the user can react instead of generating answers from scratch. - Want-vs-should detection: Probes sophistication-signaling answers ("scalable", "clean", "best practice") with the question "what would you actually want if you didn't have to justify it?" - Confirmed intent output: Produces a structured restatement (Outcome / User / Why now / Success / Constraint / Out of scope) gated on an explicit yes, with optional persistence to .teikk/intent/[topic].md. - Use Case: A user says "build me a dashboard for our metrics." Two interview rounds reveal the actual need is a personal experiment tracker list, not a dashboard — preventing an entirely wrong build. ## Quick Start Ask the agent to interview you one question at a time about what you actually want before it starts planning or writing any code.

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 requirements before writing code?▼

State a one-sentence hypothesis 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 to the next three questions, then restate the intent and get an explicit yes.

How to stop AI agents from making wrong assumptions about my request?▼

Invoke an interview-style workflow that forces the agent to surface its assumptions as explicit guesses before planning. The agent must commit to a hypothesis you can correct, rather than silently filling gaps in your request.

When should I not use a requirements interview process?▼

Skip it for unambiguous self-contained tasks like renames, typo fixes, or pure information requests, and when the user explicitly prioritizes speed. It also requires a live responsive user, so it cannot run in CI pipelines or autonomous loops.

Why does asking one question at a time work better than a list?▼

Batched questions encourage skim-reading and surface answers, and later questions often depend on earlier answers. One at a time lets the user react to a specific hypothesis, which is faster than generating answers from scratch.

What counts as confirmation of user intent?▼

Only an explicit yes to a concrete restatement covering outcome, user, success criteria, constraint, and out-of-scope items. Responses like "whatever you think" or "sounds good" are delegation or politeness, not confirmation, and require follow-up.