interview

Conduct structured interviews to produce a SPEC.md requirements document.

Updated Jan 21, 2026

Search Tags:#specification #requirements #interview #product-management #acceptance-criteria #stakeholders

Ready to run

npx skills add https://github.com/breeze4/claude-config --skill interview-breeze4

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/breeze4/claude-config/tree/main/skills/interview
Command: npx skills add https://github.com/breeze4/claude-config --skill interview-breeze4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interviews are used to elicit, validate, and document requirements from stakeholders, reducing ambiguity and scope creep during project initiation.

Core Features & Use Cases

Structured questioning framework to uncover goals, constraints, and success criteria
Documentation of decisions, assumptions, and acceptance criteria for handoffs
Conversation-to-spec conversion that outputs a ready-to-use SPEC.md

Quick Start

Begin by outlining the project context and goals, then let the interviewer guide the session with targeted questions.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I gather requirements through stakeholder interviews for a new project?▼

Stakeholder interviews gather and clarify requirements through a structured questioning framework to uncover project goals, constraints, and success criteria. This conversational approach reduces ambiguity and scope creep during project initiation.

What is the best way to document acceptance criteria and project specifications?▼

Documenting acceptance criteria is best achieved through conversation-to-spec conversion, which records stakeholder decisions and assumptions. This process outputs a ready-to-use specification document containing project overview, requirements, and edge-case guidance.

How do I turn stakeholder conversations into a ready-to-use SPEC.md file?▼

You turn stakeholder conversations into a ready-to-use specification document by applying a repeatable interview protocol. The session records answers and automatically structures them into a comprehensive SPEC.md with data considerations and acceptance criteria.

When do I need to conduct in-depth requirement interviews for product management?▼

You need to conduct in-depth requirement interviews at the start of new features, projects, or complex tasks. This structured questioning captures essential goals, constraints, and success criteria to prevent scope creep before development begins.

Does a structured interview protocol help define edge-case guidance for complex tasks?▼

Yes, a structured interview protocol helps define edge-case guidance by systematically uncovering constraints and project assumptions. It ensures complex tasks capture comprehensive requirements and data considerations through targeted questioning.

What are the limitations of using interviews to elicit product management requirements?▼

Interviews to elicit product management requirements depend heavily on stakeholder availability and clear communication. While they reduce ambiguity, limitations include potential bias in stakeholder answers and the need for a structured protocol to ensure all edge cases are captured.