deep-interview
/deep-interview
Socratic deep interview with mathematical ambiguity gating. Activate when user says: deep interview, interview me, ask me everything, don't assume, make sure you understand, ouroboros, socratic, I have a vague idea, not sure exactly what I want.
- Author
- zereight ↗
- Repository
- gitlab-mcp ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Socratic deep interview with mathematical ambiguity gating. Activate when user says: deep interview, interview me, ask me everything, don't assume, make sure you understand, ouroboros, socratic, I have a vague idea, not sure exactly what I want.
Arguments
/deep-interview [--quick|--standard|--deep] <idea or vague description>
Original author description
Socratic deep interview with mathematical ambiguity gating. Activate when user says: deep interview, interview me, ask me everything, don't assume, make sure you understand, ouroboros, socratic, I have a vague idea, not sure exactly what I want.
How it works
- Pipeline
- When to Use
- When NOT to Use
- Phases
- Rules
SKILL.md preview
---
name: deep-interview
description: >
Socratic deep interview with mathematical ambiguity gating.
Activate when user says: deep interview, interview me, ask me everything,
don't assume, make sure you understand, ouroboros, socratic,
I have a vague idea, not sure exactly what I want.
argument-hint: "[--quick|--standard|--deep] <idea or vague description>"
---
# Deep Interview
Ouroboros-inspired Socratic questioning with mathematical ambiguity scoring. Replaces vague ideas with crystal-clear specifications by asking targeted questions that expose hidden assumptions.
## Pipeline
`deep-interview` → `ralplan` (consensus refinement) → `omg-autopilot` (execution)
## When to Use
- User has a vague idea and wants thorough requirements gathering
- Task is complex enough that jumping to code would waste cycles
- User wants mathematically-validated clarity before execution
## When NOT to Use
- Detailed specific request with file paths → execute directly
- Quick fix → delegate to @executor or `/ralph`
- User says "just do it" → respect their intent
## Phases
### Phase 1: Initialize
1. Parse the user's idea
2. Detect brownfield vs greenfield (use @explore to check codebase)
3. For brownfield: map relevant codebase areas
4. Initialize ambiguity score at 100%
### Phase 2: Interview Loop
Repeat until ambiguity <= 20% or user exits early:
1. **Generate question** targeting the WEAKEST clarity dimension
2. **Ask ONE question at a time** with current ambiguity context
3. **Score ambiguity** across dimensions:
- Goal Clarity (40% weight for greenfield, 35% brownfield)
- Constraint Clarity (30% / 25%)
- Success Criteria (30% / 25%)
- Context Clarity (N/A / 15% for brownfield)
4. **Report progress** with dimension scores and gaps
5. **Track ontology** (key entities, stability ratio)
### Phase 3: Challenge Agents
- Round 4+: **Contrarian** - challenge core assumptions
- Round 6+: **Simplifier** - probe for complexity removal
- Round 8+: **Ontologist** - find the essence (if ambiguity > 30%)
### Phase 4: Crystallize Spec
When ambiguity <= threshold, generate spec to `.omc/specs/deep-interview-{slug}.md`:
- Goal, Constraints, Non-Goals, Acceptance Criteria
- Assumptions Exposed & Resolved
- Ontology (Key Entities) with convergence tracking
- Interview Transcript
### Phase 5: Execution Bridge
Present options:
1. **Ralplan → OMG Autopilot** (Recommended): consensus-refine then execute
2. **Execute with omg-autopilot** (skip ralplan)
3. **Execute with ralph**: persistence loop
4. **Execute with team**: parallel agents
5. **Refine further**: continue interviewing
## Rules
- Ask ONE question at a time
- Target the WEAKEST clarity dimension each round
- Gather codebase facts via @explore BEFORE asking user
- Score ambiguity after every answer
- Do not proceed until ambiguity <= threshold (default 20%)
- Hard cap at 20 rounds, soft warning at 10
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · zereight/gitlab-mcp | 90 | MIT |
| dlwlgus9125/ezpowers | 100 | MIT |
| jscraik/Agent-Skills | 100 | Apache-2.0 |
| OXI-717/ai-native-toolkit | 100 | MIT |
| propstreet/claude-powerpack | 100 | MIT |
| tranhieutt/software_development_department | 95 | MIT |
| sean2077/skills | 85 | MIT |
Database snapshot: 13.11.2026 · package version 5e664f9a9de7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95jarvis-deep-interview
Convergent Socratic interview that turns vague requirements into a production-grade specification via 8-15 narrowing rounds with mathematical ambiguity gating. Inspired by Sorbh/interview-me, adds Contrarian/Simplifier Challenge Mode and JSONL decision log. Use when an idea… - 100interview
Socratic interview and ambiguity scoring. Use for "interview", "question", "socratic", and "ambiguity". - 100interview
Use when the user wants to build or change something but the request is vague or open-ended: 'help me figure out what to build', 'I'm not sure what it should do', 'add X' with no details, or no clear definition of done. Runs a short Socratic interview that turns the idea into… - 100dev-deep-interview
Socratic questioning to crystallize vague requirements into a testable spec. Use when input is ambiguous, when the user asks for "deep interview", or before dev-autopilot if the brief is too broad. Pairs with @echo-analyst. - 95interview
Use when the requested deliverable is vague, broad, ambiguous, requirement-light, or missing users, constraints, or acceptance criteria and needs requirements discovery before implementation planning or execution. - 100v1-interview-me
Use when an idea, feature request, or ticket needs structured questioning before planning. Triggers on "interview me", "flesh out this idea", or "help me spec this".