deep-interview

Clarify vague requests into execution-ready specifications with structured questioning.

Updated Apr 20, 2026

Search Tags:#planning #requirements #clarification #interview #scope #socratic

Ready to run

npx skills add https://github.com/hotaq/Sprite_harmess --skill deep-interview-hotaq

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep Interview turns broad, underspecified requests into clear, testable requirements before any planning or implementation begins.

Core Features & Use Cases

Intent-first Socratic questioning to uncover why the change is needed.
Boundary and non-goal discovery to prevent scope creep and misaligned execution.
Ambiguity scoring, pressure testing, and handoff artifacts for downstream planning skills.
Use it when a user brings a vague idea, when brownfield changes need evidence-backed clarification, or when a mission needs a ready-to-execute brief.

Quick Start

Use deep-interview to clarify the goal, boundaries, and success criteria for the request before moving into planning.

Frequently Asked Questions about deep-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn vague ideas into clear execution specs before development?▼

To turn vague ideas into clear execution specs, apply structured Socratic questioning and ambiguity scoring to uncover boundaries, non-goals, and decision ownership before generating handoff-ready artifacts for downstream execution.

What is the best way to clarify brownfield code change requests with ambiguous requirements?▼

Clarifying brownfield code change requests requires intent-first Socratic questioning and pressure testing of assumptions to establish evidence-backed boundaries and prevent scope creep before implementation begins.

How do I define non-goals and success criteria for underspecified feature work?▼

Defining non-goals and success criteria for underspecified feature work involves pressure testing assumptions through structured interviewing to separate core intent from out-of-scope execution.

When do I need Socratic questioning to scope a software engineering project?▼

You need Socratic questioning to scope a software engineering project when a request is broad, lacks testable requirements, or requires explicit boundaries and decision ownership before planning can proceed.

Does this approach work for research-style missions that need strict boundaries?▼

Yes, this approach works for research-style missions by applying ambiguity scoring and boundary discovery to transform open-ended research into a ready-to-execute brief with clear constraints.