skills.rest
andrew-t-james
andrew-t-jamesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

deep-interview

Guide Socratic questioning to produce execution-ready specifications with acceptance criteria.

Updated Jul 3, 2025
Search Tags:#workflow#planning#specification#requirements#clarification#interview
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill deep-interview-andrew-t-james
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_codex/skills/deep-interview
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill deep-interview-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify ambiguous requests using a structured Socratic interview to transform vague ideas into explicit, execution-ready specifications.

Core Features & Use Cases

  • Guided questioning to reveal intent, boundaries, and acceptance criteria.
  • Generates a formal requirements artifact and readiness gates before handoff to planning/execution tools.
  • Supports optional autoresearch modes and depth profiles for scalable discovery.

Quick Start

Ask the user for the initial idea and run a one-shot clarifying interaction to produce a concrete spec.

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 executable specifications?▼

Executable specifications are produced by guiding a Socratic questioning process to reveal underlying assumptions, define scope and constraints, and establish clear acceptance criteria for your vague ideas.

What is a Socratic interview for requirements clarification?▼

Requirements clarification via a Socratic interview uses guided questioning to reveal user intent, project boundaries, and non-goals, transforming ambiguous requests into formal, execution-ready artifacts.

How do I define scope and non-goals before handing off to planning tools?▼

Scope and non-goals are defined through structured questioning that establishes readiness gates and a formal requirements artifact, ensuring a structured trajectory for handoffs to planning or execution tools.

Can I use autoresearch mode to gather information during the specification process?▼

Autoresearch mode is supported as an optional feature to assist the specification process, offering scalable discovery alongside depth profiles to articulate goals and produce formal requirements.

What is the best way to structure acceptance criteria for a new project idea?▼

Acceptance criteria are structured by identifying the user's goal and articulating constraints through a one-shot clarifying interaction, producing a concrete spec with formal readiness gates.

When should I not use a Socratic interview for requirements gathering?▼

Socratic interviews are less suitable when initial ideas are already well-defined with explicit constraints, as the structured questioning process targets transforming vague concepts into execution-ready specifications.

Related Skills

Explore More Product & Management Skills→
koasis89koasis89

deep-interview

Execute a Socratic clarification loop to transform ideas into executable specifications.

Community
Advanced
shayne-snapshayne-snap
3

deep-interview

Converts vague requests into execution-ready specifications via iterative Socratic clarification and ambiguity scoring.

Community
Advanced
Hyeonjun0527Hyeonjun0527
1

deep-interview

Guide users through Socratic questioning with ambiguity scoring to clarify requirements.

Community
Advanced
heltondoriaheltondoria
1

discovery

Guide project discovery through Golden Circle questioning to define purpose and strategy.

Community
Intermediate