deep-interview

Transform vague project ideas into explicit, execution-ready specifications.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill deep-interview-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/YeaChan05/Remittance --skill deep-interview-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify vague requests and convert them into explicit, execution-ready specifications through a guided Socratic interview before planning or coding.

Core Features & Use Cases

  • Interactive clarification loop that probes intent, scope, constraints, and success criteria.
  • Generates a structured requirements artifact and decision boundaries for downstream handoffs.
  • Useful for projects with ambiguous goals, missing acceptance criteria, or when alignment is critical before design or implementation.

Quick Start

Describe your idea briefly and begin the Socratic interview when prompted.

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 project ideas into execution-ready specifications?

To turn vague project ideas into execution-ready specifications, this Skill applies a guided Socratic interview process. It probes intent, scope, and constraints through an interactive clarification loop, outputting structured requirements for downstream planning.

What is a Socratic interview for requirements clarification?

A Socratic interview for requirements clarification is a structured questioning process that probes ambiguous inputs to define explicit non-goals and decision boundaries. It ensures alignment by extracting success criteria before design or development begins.

How do I define non-goals and decision boundaries for ambiguous project requests?

To define non-goals and decision boundaries for ambiguous project requests, initiate an interactive clarification loop. The process systematically challenges broad inputs to establish explicit project scope and success criteria before implementation.

When do I need a structured requirements artifact before starting development?

You need a structured requirements artifact before starting development when a project has ambiguous goals or missing acceptance criteria. It provides explicit decision boundaries and handoff support when alignment is critical prior to design.

What is the best way to align stakeholders on project scope before planning?

The best way to align stakeholders on project scope before planning is through a Socratic clarification loop. It transforms vague ideas into structured requirements artifacts with explicit non-goals, ensuring all parties share identical execution-ready specifications.

Can I use this Socratic clarification process for projects with missing acceptance criteria?

Yes, you can use this Socratic clarification process for projects with missing acceptance criteria. It is specifically designed to probe broad or ambiguous inputs, extracting success metrics and generating structured artifacts for downstream execution.