deep-interview

Clarify vague project ideas through a Socratic interview into a testable spec.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HaydernCenterpoint/oh-my-qwen --skill deep-interview-hayderncenterpoint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/HaydernCenterpoint/oh-my-qwen/tree/main/skills/deep-interview
Command: npx skills add https://github.com/HaydernCenterpoint/oh-my-qwen --skill deep-interview-hayderncenterpoint

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

  • Socratic questioning to surface intent, outcomes, scope, non-goals, and decision boundaries before execution.
  • Structured, multi-round interview to create a clear, testable spec and the artifacts that accompany it (context snapshot, constraints, acceptance criteria).
  • Use cases include clarifying broad requests, aligning stakeholders, and preparing requirements for downstream plans like deep-interview, ralplan, or autopilot.

Quick Start

Describe your idea briefly to begin the Socratic clarification 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 project ideas into testable specifications before planning?▼

Clarify vague project ideas through a structured Socratic interview that surfaces intent, boundaries, constraints, and acceptance criteria to produce a concrete, testable specification before execution.

What is a Socratic interview for requirements gathering and how does it work?▼

A Socratic interview for requirements gathering uses targeted questioning to surface intent, outcomes, scope, non-goals, and decision boundaries, transforming ambiguous product or technical requests into structured artifacts.

How do I structure multi-round interviews to capture project scope and non-goals?▼

Structure multi-round interviews by asking targeted questions about why a change is needed, how far it should go, and what stays out of scope, capturing context snapshots and decision boundaries to define non-goals.

Does this clarification process work for both product and technical domains?▼

Yes, the clarification process targets ambiguous requests across product, research, and technical domains, surfacing intent and constraints to generate execution-ready specifications for any domain.

What is the best way to align stakeholders on ambiguous project requests?▼

The best way to align stakeholders is conducting a Socratic clarification loop that surfaces intent and decision boundaries, producing a shared, testable specification with clear scope and acceptance criteria.

When should I not use Socratic questioning for specification generation?▼

Avoid Socratic questioning for specification generation when project requirements are already concrete, testable, and fully defined, or when downstream planning lanes require immediate execution without intent clarification.