Conduct structured interviews to produce a SPEC.md requirements document.
npx skills add https://github.com/breeze4/claude-config --skill interview-breeze4
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
Interviews are used to elicit, validate, and document requirements from stakeholders, reducing ambiguity and scope creep during project initiation.
Begin by outlining the project context and goals, then let the interviewer guide the session with targeted questions.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
cshyangPlan and execute a project discovery phase to define requirements and scope.
gihwan-devParse SPEC.md and plan.md to generate phased milestones with completion criteria.
JaviMontanoGenerate a project communication plan with stakeholder matrices, cadences, channels, and templates.
tiweenCreate and validate Product Requirement Documents through structured interviews and stakeholder alignment.
