deep-interview

Refine vague product ideas into precise specifications through iterative Socratic questioning.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/jimmi2051/oh-my-copilot --skill deep-interview-jimmi2051
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/jimmi2051/oh-my-copilot/tree/main/plugins/omc-copilot/skills/deep-interview
Command: npx skills add https://github.com/jimmi2051/oh-my-copilot --skill deep-interview-jimmi2051

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview provides a structured, one-question-at-a-time Socratic interviewing process to convert vague ideas into explicit, actionable specifications before any autonomous execution.

Core Features & Use Cases

  • Iterative ambiguity scoring and ontology tracking to surface hidden assumptions.
  • Phase-driven workflow that feeds into plan generation and automated execution pipelines (ralplan → autopilot).
  • Works when requirements are unclear, enabling safer, higher-quality engineering outcomes.

Quick Start

Provide a vague idea and I will start a one-question-at-a-time interview to crystallize a full spec.

Frequently Asked Questions about deep-interview

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

FAQPage Schema
How do I turn vague product ideas into precise specifications?

To turn vague product ideas into precise specifications, use a structured Socratic interviewing process that asks one question at a time. This method iteratively scores ambiguity and tracks assumptions to crystallize ill-defined requirements into explicit, actionable specs.

What is Socratic questioning for requirement elicitation?

Socratic questioning for requirement elicitation is an iterative technique that surfaces hidden assumptions in ambiguous ideas. By enforcing a one-question-at-a-time workflow, it systematically scores ambiguity across dimensions to refine unclear concepts into rigorous specifications.

How do I start refining ambiguous requirements before automation?

To start refining ambiguous requirements before automation, simply provide a vague idea to initiate the interview. The system will guide you through a phase-driven workflow, asking targeted questions to extract explicit requirements before generating an execution plan.

Does this structured interview approach work for unclear product specifications?

Yes, this structured interview approach specifically works when product specifications are unclear or ill-defined. It enforces rigorous requirement elicitation through phase-driven questioning, ensuring safer, higher-quality engineering outcomes before autonomous execution.

What is the best way to reduce ambiguity in product planning?

The best way to reduce ambiguity in product planning is through iterative Socratic questioning with ontology tracking. This approach systematically surfaces hidden assumptions and scores ambiguity across dimensions to convert vague ideas into actionable specifications.

Where are the finalized specifications saved after the interview?

Finalized specifications are saved as a markdown file at `.omc/specs/deep-interview-{slug}.md`. This ensures the crystallized spec is stored locally and ready to feed into downstream plan generation and automated execution pipelines.