deep-interview

Clarify ambiguous user ideas through structured Socratic questioning into a testable requirements brief.

1|Updated Sep 22, 2025

Search Tags:#specification #requirements #clarification #ambiguity #product-management #deep-interview

Ready to run

npx skills add https://github.com/prthik/prathik-astro --skill deep-interview-prthik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/prthik/prathik-astro/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/prthik/prathik-astro --skill deep-interview-prthik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview is an intent-first Socratic clarification loop before planning or implementation. It turns vague ideas into execution-ready specifications by asking targeted questions about why the user wants a change, how far it should go, what should stay out of scope, and what OMX may decide without confirmation.

Core Features & Use Cases

Deep Interview prompts systematic clarification to extract intent, boundaries, and acceptance criteria for downstream work.
It generates an execution-ready spec, acceptance criteria, and scope definitions suitable for handoffs to planning or execution lanes.
It supports multiple interrogation depths (quick, standard, deep) and autoresearch pathways when required.

Quick Start

Provide a vague idea and initiate the standard deep-interview to produce a ready-to-use spec.

Frequently Asked Questions about deep-interview

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

FAQPage Schema

How do I clarify ambiguous product ideas into execution-ready specifications?▼

To turn vague requests into specifications, undergo a structured Socratic questioning protocol that reveals scope, intent, and constraints, yielding an execution-ready spec suitable for planning handoffs.

What is the best way to define acceptance criteria for broad, underspecified requests?▼

The best way to define acceptance criteria for broad requests is to apply a targeted clarification loop that interrogates why a change is needed, how far it should go, and what must stay out of scope.

How do I extract project boundaries and scope definitions from a vague initial idea?▼

You extract project boundaries from a vague idea by enforcing a questioning protocol that systematically prompts clarification, capturing evidence and context to determine what stays out of scope.

Can I adjust the interrogation depth when clarifying requirements for product management?▼

Yes, you can adjust interrogation depth when clarifying requirements, as the process supports multiple levels including quick, standard, and deep pathways to match the needed specification detail.

When do I need a Socratic clarification loop for product definition and planning?▼

You need a Socratic clarification loop for product definition when facing broad, underspecified requests that lack clear intent, requiring systematic extraction of context before generating canonical artifacts for execution.