skills.rest
ozby
ozbyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

deep-interview

Clarify ambiguous user requests through sequential Socratic questioning into a testable spec.

1|Updated Mar 17, 2025
Search Tags:#planning#specification#requirements#clarification#interview#stakeholders#omx
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill deep-interview-ozby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/ozby/node-pubsub --skill deep-interview-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview enables a structured Socratic clarification loop to convert vague ideas into precise, execution-ready specs before planning or coding.

Core Features & Use Cases

  • Socratic clarification loop: sequential questions surface intent, boundaries, and acceptance criteria to reduce ambiguity.
  • Depth profiles: quick, standard, and deep interview modes with configurable rounds and escalation paths.
  • Artifact generation: outputs a formal spec and transcripts stored under .omx for downstream handoff to planning/execution teams.
  • Workflow alignment: integrates with execution lanes like ralplan, autopilot, ralph, and team for seamless handoffs.

Quick Start

Ask targeted clarifying questions to turn vague ideas into a testable, execution-ready 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 ambiguous user requests before writing a specification?▼

To clarify ambiguous user requests, this Skill applies a Socratic questioning loop to sequentially surface intent and boundaries, converting vague ideas into a concrete, testable specification ready for execution handoff.

What is the best way to turn vague ideas into execution-ready specs for stakeholders?▼

Turning vague ideas into execution-ready specs requires a structured, phase-based interview that tracks ambiguity across dimensions and outputs a formal specification artifact alongside readiness transcripts for stakeholder review.

How do I generate a validator-ready spec from broad project requirements?▼

Generating a validator-ready spec from broad requirements involves conducting sequential Socratic clarification rounds to define precise acceptance criteria and reduce ambiguity before any planning or coding begins.

Can I use different interview modes to gather requirements depending on project complexity?▼

Yes, you can use quick, standard, or deep interview modes with configurable rounds and escalation paths to gather requirements, allowing you to match the clarification depth to your specific project complexity.

Does the specification output integrate with downstream planning and execution workflows?▼

Yes, the specification output integrates with downstream execution workflows by storing finalized specs and transcripts under the .omx directory, enabling seamless handoffs to planning and execution lanes.

Related Skills

Explore More Product & Management Skills→
eszxcvfdeszxcvfd

deep-interview

Identifies ambiguity in requests through guided Socratic clarification loops with quantitative scoring.

Community
Advanced
OrinksOrinks
24

deep-interview

Guide Socratic interviews to convert vague requests into executable specifications.

Community
Advanced
dropsyoondropsyoon

ralplan

Create consensus plans for vague execution requests using a Planner-Architect-Critic loop.

Community
Advanced
tuandzungtuandzung

deep-interview

Clarify user ideas into detailed specifications via Socratic questioning.

Community
Advanced