deep-interview

Name: deep-interview
Availability: InStock
Author: orinks

Guide Socratic interviews to convert vague requests into executable specifications.

24|2|Updated Mar 12, 2025

Search Tags:#planning #specification #requirements #clarification #interview #product

Ready to run

npx skills add https://github.com/Orinks/AccessiWeather --skill deep-interview-orinks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill deep-interview-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous user requests into explicit, testable specifications by guiding a Socratic interview that probes intent, boundaries, and acceptance criteria.

Core Features & Use Cases

Guided, one-question-at-a-time interview rounds to elicit intent, outcomes, scope, constraints, and non-goals.
Automatic generation of artifacts: a transcript under .omx/interviews and a formal spec under .omx/specs, with contextual references for brownfield projects.
Supports readiness gates, multiple depth profiles, and escalation modes to stress-test assumptions.
Reuses context snapshots to preserve traceability for downstream handoffs to planning/execution stages.
Optional autoresearch domain (if invoked with autoresearch) to tailor the interview toward mission clarity and research artifacts.

Quick Start

Provide your initial idea and constraints, then run the deep-interview to generate a clear, testable 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 into executable specifications?▼

To clarify vague product requirements into executable specifications, a guided Socratic interview probes intent, scope, constraints, and acceptance criteria. This method extracts explicit, testable boundaries from ambiguous initial requests.

What is the best way to define non-goals and decision boundaries for a new feature?▼

Defining non-goals and decision boundaries is best achieved through structured clarification interviews that stress-test assumptions. This ensures explicit scope limits are documented before downstream planning and execution stages begin.

Can I use a Socratic interview to preserve context for brownfield projects?▼

Yes, you can use a Socratic interview to preserve brownfield context. It reuses context snapshots and generates formal specs with contextual references, ensuring traceability for downstream handoffs in existing codebases.

How do I generate traceable artifacts for downstream planning and execution?▼

Generate traceable artifacts by running a structured clarification process that outputs a transcript under .omx/interviews and a formal spec under .omx/specs. These artifacts store explicit scope and acceptance criteria for handoff.

Does the specification interview process support escalation modes to test assumptions?▼

Yes, the specification interview process supports escalation modes to stress-test assumptions. It also features readiness gates and multiple depth profiles to ensure vague ideas are fully solidified into formal specifications.