deep-interview

Converts vague requirements into structured specifications through Socratic one-question-at-a-time interviews.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/VelkaressiaBlutkrone/spring-python-llm-exam-mng --skill deep-interview-velkaressiablutkrone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/VelkaressiaBlutkrone/spring-python-llm-exam-mng/tree/main/.claude/skills/deep-interview
Command: npx skills add https://github.com/VelkaressiaBlutkrone/spring-python-llm-exam-mng --skill deep-interview-velkaressiablutkrone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague requests like "just build it" lead to building the wrong thing, which is the most expensive mistake in development. This Skill runs a structured Socratic interview before any coding begins, turning ambiguous ideas into a confirmed, prioritized specification. ## Core Features & Use Cases - Socratic Questioning: Asks exactly one question at a time, building each new question on the previous answer while detecting contradictions and gaps in the user's responses. - Five-Phase Interview Flow: Progresses through problem understanding, user context, scope and constraints, edge cases, and success criteria across roughly 5-15 questions. - Structured Specification Output: Produces a summary document with problem definition, target users, prioritized requirements (P0/P1/P2), constraints, edge cases, out-of-scope items, and acceptance criteria, then asks for explicit confirmation. - Use Case: A user says "help me plan a feature" or "I'm not sure what to build." The Skill interviews them about who uses it, what constraints exist, and what edge cases matter, then delivers a confirmed spec ready for implementation. ## Quick Start Type /deep-interview or ask "help me organize my requirements" and answer the interviewer's questions one at a time until a specification summary is produced.

Frequently Asked Questions about deep-interview

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

FAQPage Schema
How do I turn a vague feature idea into a clear specification?▼

Run a structured requirements interview that asks one question at a time across problem definition, target users, scope, edge cases, and success criteria. The answers are consolidated into a prioritized specification with acceptance criteria that you confirm before implementation begins.

What questions should I ask before writing code for a new feature?▼

Ask about the problem's origin, who uses the feature and how often, must-have versus nice-to-have scope, technical and deadline constraints, error and edge-case behavior, and how success will be measured. Typically 5 to 15 questions suffice.

When should I use a requirements interview instead of coding directly?▼

Use it whenever the request is vague, the PRD is thin, or you cannot clearly state what to build. If requirements are already precise and confirmed, skip the interview and proceed to implementation.

What does the requirements interview output look like?▼

The output is a markdown summary containing the problem definition, target users, prioritized requirements labeled P0 through P2, constraints and assumptions, edge cases, explicitly excluded scope, and a checklist of acceptance criteria.

What happens if the user says stop asking and just build it?▼

The interview immediately converges: the information gathered so far is compiled into a quick summary and presented for confirmation. Implementation only starts after the user approves that specification.