deep-interview

Clarify ambiguous project ideas into detailed specifications through Socratic questioning.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/zhaozengqing4364-bit/sales-training-qoder --skill deep-interview-zhaozengqing4364-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/zhaozengqing4364-bit/sales-training-qoder/tree/main/.codex/skills/deep-interview
Command: npx skills add https://github.com/zhaozengqing4364-bit/sales-training-qoder --skill deep-interview-zhaozengqing4364-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Deep Interview helps convert ambiguous or broad project ideas into detailed, execution-ready specifications by engaging in an intent-first Socratic clarification loop.

Core Features & Use Cases

  • Clarifies project scope and requirements: Uses targeted questions to dissect unclear user requests, ensuring precise understanding.
  • Facilitates requirement gathering: Supports teams in creating comprehensive, testable specifications before development begins.
  • Use Case: A product team receives a vague feature idea; Deep Interview guides them to articulate goals, constraints, and success criteria, producing a detailed spec ready for planning or implementation.

Quick Start

Ask Deep Interview to clarify a project concept by providing a vague idea or requirement description, prompting it to generate targeted questions for refinement.

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 project requirements into actionable specifications?

To clarify vague project requirements into actionable specifications, use a Socratic questioning loop to uncover intent, scope, constraints, and success metrics. This systematic clarification produces detailed, testable specs ready for development.

What is Socratic questioning for requirements gathering?

Socratic questioning for requirements gathering is a technique that uses targeted questions to dissect unclear project ideas. It helps teams articulate goals and constraints, transforming ambiguous feature requests into comprehensive, execution-ready specifications.

How do I define project scope when the initial feature idea is ambiguous?

To define project scope from an ambiguous feature idea, apply an intent-first clarification process that asks targeted questions. This uncovers specific success criteria and constraints, ensuring precise understanding before development begins.

Can I use Socratic questioning to create testable specifications before development?

Yes, you can use Socratic questioning to create testable specifications before development. By systematically dissecting broad ideas to articulate goals and constraints, it ensures the final requirements are detailed and actionable for planning.

Does Socratic requirements clarification work for any project management context?

Socratic requirements clarification works for any project management context where ideas remain vague. It systematically guides product teams to extract intent, scope, and success metrics regardless of the specific development environment.

When should I not use Socratic questioning for project specifications?

You should not use Socratic questioning for project specifications when requirements are already highly detailed and execution-ready. The approach targets ambiguous ideas needing intent discovery, adding unnecessary overhead to clearly defined scopes.