deep-interview

Name: deep-interview
Availability: InStock
Author: tornado1014

Analyze SPEC documents and codebases to generate structured interview questions.

Updated Jan 9, 2026

Search Tags:#documentation #codebase #specification #requirements #analysis #interview #AskUserQuestion

Ready to run

npx skills add https://github.com/tornado1014/patent-translator-agent --skill deep-interview

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/tornado1014/patent-translator-agent/tree/main/.claude/skills/deep-interview
Command: npx skills add https://github.com/tornado1014/patent-translator-agent --skill deep-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to conduct in-depth interviews to elicit and refine software requirements by analyzing SPEC documents and codebases, reducing ambiguity and scope creep.

Core Features & Use Cases

Spec analysis & gap detection: Analyzes SPEC documents and codebases to identify gaps, ambiguities, and critical concerns.
Structured interview loops: Conducts multi-category interviews (technical, UI/UX, concerns, trade-offs) to surface requirements and risks.
Output-ready specifications: Produces a completed spec ready for stakeholder review and implementation planning.

Quick Start

Trigger the Deep Interview: run the command /deep-interview with a SPEC file path or start with the default SPEC.md in the project root, then follow the guided interview prompts.

Frequently Asked Questions about deep-interview

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

FAQPage Schema

How do I refine software requirements and reduce ambiguity in my SPEC documents?▼

To refine software requirements, you can initiate a structured interview process that analyzes your SPEC documents and codebase to detect gaps, conducts multi-category loops across technical and UI/UX domains, and outputs a refined specification ready for stakeholder review.

What is the best way to gather stakeholder alignment and explore technical trade-offs for a new feature?▼

The best way to gather stakeholder alignment is to use a multi-phase interview process that generates context-aware questions, explicitly exploring trade-offs across technical implementation, UI/UX, and risk assessment to surface critical concerns.

Can I analyze my existing codebase to identify specification gaps and scope creep?▼

Yes, you can analyze your existing codebase alongside a SPEC file to identify specification gaps, ambiguities, and critical concerns, effectively reducing scope creep by ensuring requirements are thoroughly validated before implementation.

How do I conduct a multi-category interview to surface software project risks and UI/UX requirements?▼

You can conduct a multi-category interview by triggering a guided command with a SPEC file path, which then orchestrates structured interview loops to systematically surface technical requirements, UI/UX needs, concerns, and trade-offs.

Do I need a pre-existing SPEC document to start analyzing software requirements?▼

No, you do not need a pre-existing document; you can start the analysis with the default SPEC.md file in the project root, or provide a specific SPEC file path to guide the interview and requirement elicitation process.