deep-interview

Clarify vague requirements through one-question-at-a-time interviews and output a structured summary.

Updated Aug 17, 2025
One-click install
npx skills add https://github.com/gzyxds/cloudcvm.com --skill deep-interview-gzyxds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/gzyxds/cloudcvm.com/tree/main/.trae/skills/deep-interview
Command: npx skills add https://github.com/gzyxds/cloudcvm.com --skill deep-interview-gzyxds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify vague requirements and explore user intent by guiding a focused, step-by-step questioning process that reveals goals, non-goals, and constraints.

Core Features & Use Cases

  • Phase-based interview framework (Intent Discovery, Boundary Setting, Constraint Mapping, Context Gathering) to structure conversations.
  • One-question-at-a-time questioning to reduce ambiguity and collect precise requirements.
  • Output an actionable interview summary suitable for planning and stakeholder alignment.

Quick Start

Start a deep-interview session by asking one clarifying question to reveal the core goal, boundaries, and constraints.

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 with stakeholders?

To clarify vague requirements with stakeholders, use a phase-based interview framework that asks one question at a time. This stepwise discovery process maps intent, boundaries, and constraints to produce a structured summary for planning and alignment.

What is the best way to explore user intent for ambiguous scope?

Exploring user intent for ambiguous scope involves targeted interviews covering Intent Discovery, Boundary Setting, Constraint Mapping, and Context Gathering. This step-by-step questioning reduces ambiguity and collects precise requirements for greenfield or brownfield projects.

How do I start a step-by-step interview to define project boundaries?

Start defining project boundaries by asking a single clarifying question to reveal the core goal. Progress through focused phases, mapping constraints and gathering context sequentially to ensure precise requirement collection without overwhelming the respondent.

Does this structured interview approach work for both new ideas and existing system changes?

Yes, this structured interview approach works for both greenfield ideas and brownfield changes. It applies whenever a request is unclear, boundaries are undefined, or scope is ambiguous, successfully mapping constraints and intent for any project phase.

What do I get from a focused requirements clarification session?

From a focused requirements clarification session you get an actionable interview summary suitable for planning. This structured output captures discovered goals, non-goals, and constraints to ensure stakeholder alignment before development begins.

When should I use a one-question-at-a-time interview instead of a standard questionnaire?

Use a one-question-at-a-time interview when a request is unclear and boundaries are undefined. This focused method prevents overwhelming stakeholders, progressively revealing non-goals and constraints that a standard questionnaire might miss due to its static nature.