dev-deep-interview

Converts vague product requirements into testable specs via guided Socratic questioning.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-deep-interview-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-deep-interview
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-deep-interview
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-deep-interview-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev Deep Interview eliminates ambiguity by asking focused, one-at-a-time questions so the output becomes a clear, testable specification instead of an underspecified plan.

Core Features & Use Cases

  • Socratic questioning: Identifies the lowest-clarity dimensions (domain, scope, success criteria, constraints, stakeholders) and resolves them with targeted follow-ups.
  • Decision guardrails: Skips the interview when inputs are already sufficiently clear and stops after a maximum of 8 questions to prevent “interrogation” fatigue.
  • Persistent spec output: Always writes a spec file to workspace with an ambiguity score and a suggested next step for downstream agents.
  • Use case: Before starting implementation, use it to clarify requirements for a “build me something” request that lacks scope, constraints, or acceptance criteria.

Quick Start

Run the deep interview to clarify a vague feature request for an executor agent to implement without further back-and-forth.

Frequently Asked Questions about dev-deep-interview

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

FAQPage Schema
How do I turn vague software requirements into testable specifications?

To turn vague requirements into testable specifications, the deep interview process uses guided Socratic questioning to resolve missing scope, constraints, stakeholders, and success criteria, generating a deterministic spec file for downstream execution.

What is the best way to reduce ambiguity in product requirements before development?

Reducing ambiguity in product requirements is best achieved by applying dimension scoring to target the lowest-clarity areas and asking focused follow-up questions until a clear, testable specification is produced.

How many questions does Socratic questioning ask to clarify a feature request?

Socratic questioning for feature clarification asks a maximum of eight single questions in a loop, preventing interrogation fatigue while ensuring enough information is gathered to write a complete specification.

Does the specification interview skip questions if the request is already clear?

Yes, the specification interview includes decision guardrails that skip the questioning loop entirely when the initial input already provides sufficiently clear scope, constraints, and acceptance criteria.

Where are generated specification files saved for downstream agents?

Generated specification files are saved persistently in the workspace/projects/specs directory, including an ambiguity score and suggested next steps to guide downstream executor agents.