deep-interview

Gather requirements through a structured Socratic clarification loop.

Updated May 25, 2026
One-click install
npx skills add https://github.com/BetaS/swm-gis-workshop --skill deep-interview-betas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/BetaS/swm-gis-workshop/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/BetaS/swm-gis-workshop --skill deep-interview-betas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires omx, and includes scripts (resource) components.

What problem does it solve?

Deep Interview Skill tackles the issue of ambiguity and misaligned intent in requirements gathering by engaging users in a targeted, structured Socratic clarification loop.

Core Features & Use Cases

  • Intent Clarity: Delve into the underlying motivations behind user requests, ensuring a clear and shared understanding.
  • Scope Definition: Help define the boundaries and limitations of a project or task, preventing scope creep.
  • Execution Preparation: Facilitate the creation of execution-ready specifications, minimizing the risk of misalignment during implementation.
  • Use Case: Before proceeding with planning or execution of a new feature, Deep Interview can be used to ensure the project's objectives, scope, and technical requirements are clearly defined and agreed upon.

Quick Start

To initiate a deep interview, run: deep-interview [option] <user's idea or description>

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 project requirements before execution?

You clarify requirements by engaging in a Socratic clarification loop that explores user intent, project scope, constraints, and acceptance criteria through multi-round questioning.

What is Socratic interviewing in requirements engineering?

Socratic interviewing in requirements engineering is a structured, multi-round questioning process that delves into underlying motivations to ensure shared understanding of project scope and technical constraints.

How do I prevent scope creep during project planning?

Prevent scope creep by defining project boundaries and limitations through targeted clarification, ensuring execution-ready specifications are established before implementation begins.

What is the best way to discover user intent for a new software feature?

The best way to discover user intent is using complex multi-round questioning with evidence-backed probing to explore underlying motivations behind user requests and define acceptance criteria.

Do I need the omx dependency to run deep-interview?

Yes, you need the omx dependency installed to run deep-interview, which operates through scripts to facilitate the Socratic requirements gathering process.

When should I not use Socratic interviewing for requirements gathering?

You should avoid Socratic interviewing for requirements gathering when project objectives, scope, and technical requirements are already clearly defined and agreed upon, making multi-round probing unnecessary.