deep-interview

Clarify vague requests into testable requirements through a Socratic questioning loop.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill deep-interview-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.codex/skills/deep-interview
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill deep-interview-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview provides a structured, Socratic loop to convert vague requests into concrete, testable requirements, reducing misalignment and rework during project kickoff.

Core Features & Use Cases

  • Socratic clarification loop to surface intent, outcomes, and constraints.
  • Explicitly defines Non-goals and Decision Boundaries for downstream planning.
  • Generates execution-ready specs and context for handoff to planning/execution tools.

Quick Start

Begin the deep interview by clarifying the user’s primary objective and gathering acceptance criteria through a focused Socratic questioning loop.

Frequently Asked Questions about deep-interview

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

FAQPage Schema
How do I clarify vague product ideas into concrete, testable requirements?

Clarifying vague ideas requires a structured Socratic questioning loop that surfaces explicit intent, desired outcomes, non-goals, and decision boundaries to convert ambiguous requests into testable requirements.

What is a Socratic questioning loop for project kickoff?

A Socratic questioning loop for project kickoff is a structured dialogue process that surfaces intent, outcomes, non-goals, and constraints to reduce misalignment and rework during project initiation.

How do I define non-goals and decision boundaries for feature scoping?

Defining non-goals and decision boundaries for feature scoping involves explicitly stating what is excluded from the project and where decision authority lies, ensuring downstream planning respects those limits.

Can I use this approach for broad, ambiguous requests across product planning?

Yes, this Socratic clarification approach applies directly to broad, ambiguous requests across product planning, feature scoping, and project initiation to ensure explicit intent before execution.

What is the best way to reduce misalignment and rework during project initiation?

The best way to reduce misalignment and rework during project initiation is to run a structured Socratic loop that forces explicit articulation of intent, outcomes, and constraints before planning begins.

How do I generate execution-ready specs for handoff to planning tools?

To generate execution-ready specs for handoff, complete a Socratic clarification loop that defines acceptance criteria, non-goals, and decision boundaries, producing explicit context for downstream execution.