deep-interview

Guide Socratic clarification loops to resolve ambiguous user intent into explicit requirements.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/RJJJJ/project2 --skill deep-interview-rjjjj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/RJJJJ/project2 --skill deep-interview-rjjjj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview provides a disciplined, Socratic clarification loop to turn vague ideas into explicit, testable requirements before planning or execution.

Core Features & Use Cases

  • Guided questioning to elicit intent, outcomes, scope, constraints, and decision boundaries.
  • Artifact generation including interview transcripts and execution specs for downstream handoff.
  • Ready-to-use pathway to move from interview to planning or execution with explicit readiness gates.

Quick Start

Initiate a standard deep-interview session with a vague user prompt.

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 requirements before starting project planning?

To clarify ambiguous requirements before project planning, you can use a Socratic clarification loop to identify intent, scope, and constraints. This approach applies structured, multi-round questioning to resolve broad requests and establish explicit decision boundaries before execution.

What is a Socratic interview for requirements gathering?

A Socratic interview for requirements gathering is a structured protocol that elicits user intent through targeted questioning. It transforms vague ideas into explicit, testable acceptance criteria by defining non-goals, scope, and escalation paths to ensure actionable downstream outcomes.

How do I generate execution specs and transcripts for handoff?

You generate execution specs and transcripts for handoff by running a structured clarification process that produces explicit artifacts. These documents capture the resolved intent, outcomes, and constraints required to support downstream planning and execution readiness gates.

When should I use a structured questioning protocol for requirement clarification?

You should use a structured questioning protocol for requirement clarification when initial requests are broad, ambiguous, or missing concrete acceptance criteria. It enforces multi-round questioning to expose missing details and prepares explicit artifacts for downstream execution.

Does deep-interview work for vague prompts without concrete acceptance criteria?

Yes, deep-interview specifically applies to vague prompts lacking concrete acceptance criteria. It uses a Socratic clarification loop to extract decision boundaries and non-goals, ensuring high-quality, actionable requirements are established before any planning begins.