deep-interview

Clarify vague user ideas into concrete, executable specifications.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/wmasfoe/notch-pet --skill deep-interview-wmasfoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/wmasfoe/notch-pet/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/wmasfoe/notch-pet --skill deep-interview-wmasfoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify vague user ideas into concrete, executable specifications.

Core Features & Use Cases

  • Structured Socratic questioning to surface intent, boundaries, and acceptance criteria.
  • Generates a canonical, execution-ready spec suitable for planning tools and handoffs.
  • Supports Quick, Standard, and Deep profiling with optional autoresearch workflows.

Quick Start

Provide a vague idea and let the Socratic interviewer refine it into a precise, executable specification ready for planning and execution.

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 ideas into concrete specifications?

To clarify vague ideas into concrete specifications, use structured Socratic questioning to surface intent, boundaries, and acceptance criteria. This produces a formal, execution-ready spec capturing scope, constraints, and success criteria to ensure alignment before planning or handoff.

What is the best way to define requirements for an ambiguous project request?

Defining requirements for an ambiguous project request involves applying Socratic questioning to extract decision boundaries and acceptance criteria. This process transforms broad requests lacking clear outcomes into a canonical, execution-ready specification with an explicit readiness gate for planning.

How do I write an executable specification ready for handoff?

Writing an executable specification ready for handoff requires capturing intent, outcome, scope, constraints, and success criteria. Applying structured profiling to the initial request produces a canonical document with decision boundaries and an explicit readiness gate for downstream planning and execution.

Does this specification clarification process support autoresearch workflows?

Yes, the specification clarification process supports optional autoresearch workflows. It offers Quick, Standard, and Deep profiling modes to refine ambiguous ideas, ensuring the generated formal specification integrates with automated research and downstream planning execution.

When do I need to use a Socratic interviewer for requirements gathering?

You need to use a Socratic interviewer for requirements gathering when facing broad or ambiguous requests lacking acceptance criteria. It surfaces hidden intent and decision boundaries before planning or handoff, preventing misalignment by generating a formal spec with an explicit readiness gate.