deep-interview

Convert vague intents into execution-ready specifications via Socratic questioning.

Updated May 18, 2026
One-click install
npx skills add https://github.com/solitude6060/Yao-skills --skill deep-interview-solitude6060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/solitude6060/Yao-skills/tree/main/skills/deep-interview
Command: npx skills add https://github.com/solitude6060/Yao-skills --skill deep-interview-solitude6060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview prevents wasted execution by converting vague or ambiguous ideas into mathematically gated, unambiguous specifications before any autonomous work begins.

Core Features & Use Cases

  • Socratic ambiguity reduction: Asks one targeted question at a time to expose assumptions and clarify the weakest dimension until ambiguity falls below a configured threshold.
  • Explicit ambiguity scoring: Scores goal clarity, constraint clarity, and success-criteria clarity (and context clarity for brownfield) after each answer, transparently showing progress.
  • Brownfield-first code grounding: Uses a codebase exploration step before asking user confirmation questions when extending existing systems.
  • Execution readiness gate: Produces a spec artifact only when clarity is sufficient, then routes into the next pipeline stage.

Common use cases include requirements discovery for complex initiatives, preventing “that’s not what I meant” outcomes in autonomous development, and safely handling incident triage when details are uncertain.

Quick Start

Run deep-interview to convert your vague idea into a ready-to-execute spec by answering the first Socratic question about what exactly should happen.

Frequently Asked Questions about deep-interview

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

FAQPage Schema
How do I turn vague product ideas into clear execution-ready specifications?

To turn vague ideas into clear specifications, use a Socratic interview process that asks one targeted question at a time. This reduces ambiguity by scoring goal, constraint, and success-criteria clarity until a resolved threshold is met.

How do I gather requirements for extending an existing codebase without causing misalignment?

Requirements gathering for existing codebases requires a codebase exploration step before asking confirmation questions. This grounds the interview in actual code evidence, preventing misalignment when extending existing systems.

What is Socratic questioning for requirements discovery and when do I need it?

Socratic questioning for requirements discovery is a technique that exposes hidden assumptions by targeting the weakest clarity dimension. You need it when scope, constraints, or success criteria are uncertain before initiating autonomous development.

Can I use automated specification generation for incident triage when details are uncertain?

Automated specification generation handles incident triage with uncertain details by applying ambiguity gating. It refuses to proceed until clarity scoring confirms the ambiguity is below a resolved threshold for the run.

What is the best way to prevent 'that's not what I meant' outcomes in autonomous development?

The best way to prevent misalignment in autonomous development is applying an execution readiness gate. This produces a spec artifact only when explicit per-dimension clarity scoring confirms sufficient detail.

Why does my specification process stall and refuse to proceed during requirements interviews?

A specification process stalls because ambiguity gating requires explicit per-dimension clarity scoring to fall below a resolved threshold. It refuses to proceed by design until the weakest dimension passes targeted questioning.