deep-interview

Conduct Socratic interviews to clarify vague requirements into inspectable specs.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/officechbusinessservices-creator/CompliCore --skill deep-interview-officechbusinessservices-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/officechbusinessservices-creator/CompliCore/tree/main/packages/oh-my-claudecode/skills/deep-interview
Command: npx skills add https://github.com/officechbusinessservices-creator/CompliCore --skill deep-interview-officechbusinessservices-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview implements Ouroboros-inspired Socratic questioning with mathematical ambiguity scoring. It replaces vague ideas with crystal-clear specifications by asking targeted questions that expose hidden assumptions, measuring clarity across weighted dimensions, and refusing to proceed until ambiguity drops below a configurable threshold (default: 20%). The output feeds into a 3-stage pipeline: deep-interview → ralplan (consensus refinement) → autopilot (execution), ensuring maximum clarity at every stage.

Core Features & Use Cases

  • One-question-at-a-time Socratic interviewing to surface hidden assumptions and progressively clarify requirements.
  • Mathematical ambiguity scoring with explicit thresholds and weak-dimension targeting to guide the interview.
  • Brownfield and greenfield context handling, with optional codebase exploration and ontology tracking to stabilize concepts.
  • Multi-stage execution bridge (deep-interview → omc-plan → autopilot) with state persistence and transcript/documentation of decisions.

Quick Start

Provide your initial idea and I will start one-question-at-a-time Socratic questioning until ambiguity is <= 20%, then generate and save the spec.

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 requirements before starting development?▼

To clarify vague requirements, you can use Socratic questioning to conduct a one-question-at-a-time interview that exposes hidden assumptions and progressively crystallizes ideas into a concrete specification.

What is the best way to measure ambiguity in a project specification?▼

Measuring ambiguity involves applying mathematical scoring across weighted dimensions, targeting weak areas with specific questions, and refusing to proceed until clarity drops below a configurable threshold like 20%.

How do I handle requirement gathering for brownfield versus greenfield projects?▼

Handling brownfield and greenfield projects requires a Socratic interview that supports optional codebase exploration and ontology tracking to stabilize concepts and map existing architecture into the specification.

Can I use Socratic questioning to bridge specification and execution pipelines?▼

Yes, Socratic questioning can bridge execution pipelines by feeding crystallized specifications into a three-stage process with state persistence and documented decisions for consensus refinement and automated execution.

Why does my requirement specification process fail to surface hidden assumptions?▼

Requirement specification fails to surface hidden assumptions when it lacks a disciplined, one-question-at-a-time interview framework with explicit ambiguity scoring and weak-dimension targeting to force clarity.

Does this requirement crystallization approach work for architecture and automation projects?▼

Yes, this requirement crystallization approach applies to product, architecture, and automation projects, using ontology tracking and state persistence to stabilize concepts across both greenfield and brownfield contexts.