deep-interviewlisted

<Purpose> 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. </Purpose> <Use_When> - The request is broad, ambiguous, or missing concrete acceptance criteria - The user says "deep interview", "interview me", "ask me everything", "don't assume", or "ouroboros" - The user wants to avoid misaligned implementation from underspecified requirements - You need a requirements artifact before handing off to `ralplan`, `autopilot`, `ralph`, or `team` </Use_When> <Do_Not_Use_When> - The request already has concrete file/symbol targets and clear acceptance criteria - The user explicitly asks to skip planning/interview and execute immediately - The user asks for lightweight brainstorming only (use `plan` instead) - A complete PRD/plan already exists and execution should start </Do_Not_Use_When> <Why_This_Exists> Execution quality is usually bottlenecked by intent clarity, not just missing implementation detail. A single expansion pass often misses why the user wants a change, where the scope should stop, which tradeoffs are unacceptable, and which decisions still require user approval. This workflow applies Socratic pressure + quantitative ambiguity scoring so orchestration modes begin with an explicit, testable, intent-alig