interview

Extract goals, constraints, and success criteria through structured interview phases.

2|Updated Jan 16, 2026

Search Tags:#templates #specification #requirements #validation #interview #trade-offs #stakeholders

Ready to run

npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill interview-mysmon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/core/interview
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill interview-mysmon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforming vague user requests into clear, actionable specifications is time-consuming and error-prone. This skill provides a structured interview framework to isolate goals, constraints, and success criteria, ensuring a complete and aligned requirements baseline.

Core Features & Use Cases

Phase-based interview flow (Context Understanding, Functional Requirements, Non-Functional Requirements, Edge Cases, Constraints) to extract comprehensive requirements.
Template-driven questions for technology decisions, scope boundaries, and priority to standardize discovery and capture trade-offs.
Output-ready artifacts including a requirements summary, risk notes, and an explicit acceptance plan for stakeholders.

Quick Start

Initiate a requirements interview with a user to gather goal, scope, constraints, and success metrics and produce a complete requirements summary for further specification.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I clarify vague product requirements into actionable specifications?▼

To clarify vague product requirements, use a structured interview framework to isolate goals, constraints, and success criteria. This enforces a disciplined conversation through phases like context understanding and functional requirements, producing a complete, review-ready requirements summary.

What is the best way to gather edge cases and constraints during requirements validation?▼

The best way to gather edge cases and constraints is through template-driven questions during dedicated interview phases. This standardizes discovery and captures trade-offs across technology decisions, scope boundaries, and priorities to ensure a complete requirements baseline.

Does this requirements interview framework work for system redesigns and new features?▼

Yes, this requirements interview framework works for system redesigns, new features, and product enhancements. It extracts goals, constraints, and success metrics across context, functional, and non-functional aspects to produce an aligned requirements summary.

How do I structure stakeholder interviews to capture functional and non-functional aspects?▼

Structure stakeholder interviews using explicit phases for context understanding, functional requirements, non-functional requirements, and edge cases. This disciplined conversation uses templates and explicit decision boundaries to isolate goals and capture trade-offs.

Why does requirements gathering fail to capture trade-offs and success criteria?▼

Requirements gathering fails to capture trade-offs and success criteria when lacking a structured interview framework. Without template-driven questions and explicit decision boundaries, vague user requests remain error-prone and fail to produce a review-ready requirements summary.