deep-interview

Clarify ambiguous software requests through a structured Socratic interview.

264|27|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/PacificStudio/openase --skill deep-interview-pacificstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/deep-interview
Command: npx skills add https://github.com/PacificStudio/openase --skill deep-interview-pacificstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn vague or ambiguous requests into concrete, execution-ready briefs before planning.

Core Features & Use Cases

  • Structured, one-question-at-a-time interview to elicit intent, outcome, and scope.
  • Guardrails to surface constraints, non-goals, and acceptance criteria early.
  • Use Case: When a ticket is unclear, run the interview to crystallize a precise brief before implementation.

Quick Start

Start a Socratic interview to crystallize the intent and acceptance criteria for the requested change.

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

Clarifying ambiguous requirements is done through a structured Socratic interview that extracts intent, scope, non-goals, constraints, and acceptance criteria to form an execution-ready brief.

What is a Socratic interview for product management and when do I need it?▼

A Socratic interview for product management is a focused, one-question-at-a-time technique used to surface decision boundaries and crystallize precise briefs when tickets or broad ideas lack clear scope.

How do I extract acceptance criteria from unclear project tickets?▼

Extracting acceptance criteria from unclear tickets involves conducting a sequential inquiry that identifies desired outcomes, explicit non-goals, and decision boundaries to ensure precise project scope.

Does this requirement clarification approach work for broad ideas with missing scope?▼

Yes, this requirement clarification approach works for broad ideas with missing scope by applying guardrails that surface constraints and decision boundaries early, turning vague requests into execution-ready briefs.

What's the best way to define non-goals and constraints for a vague software project?▼

The best way to define non-goals and constraints is through a focused Socratic inquiry that isolates decision boundaries and collects missing scope before any planning or implementation starts.

Why does planning fail when acceptance criteria are unclear?▼

Planning fails when acceptance criteria are unclear because vague requests lack defined scope and decision boundaries, which a structured Socratic interview must extract before execution-ready planning can begin.