requirements-interview
Interactive PM interview with expertise-adaptive questioning for requirements elicitation
Best use case
requirements-interview is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Interactive PM interview with expertise-adaptive questioning for requirements elicitation
Teams using requirements-interview should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/requirements-interview/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How requirements-interview Compares
| Feature / Agent | requirements-interview | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Interactive PM interview with expertise-adaptive questioning for requirements elicitation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Requirements Interview ## Capabilities Conducts interactive requirements interviews adapted to the user's expertise level. Generates structured requirements specifications from conversation. Identifies user personas, feature lists, constraints, and acceptance criteria. ## Tool Use Instructions - Use **Read** to examine existing spec files or project context - Use **Grep/Glob** to find existing requirements or documentation - Use **Write** to generate the requirements specification document - Use **Bash** to check project structure for context ## Process Integration - Used in `maestro-orchestrator.js` Phase 1 (PM Interview) - Maps to tasks: `maestro-pm-interview` - Agent: Product Manager (PM) - Adapts interview depth: beginner (guided), intermediate (balanced), expert (concise) - Outputs feed into `specification-generation` skill
Related Skills
interview-facilitation
Conduct semi-structured interviews and moderate focus groups with rapport building, probing techniques, and group dynamics management
oral-history-interview-technique
Conduct life history and testimonial interviews with appropriate prompting, active listening, and trauma-informed approaches
requirements-flowdown
Skill for systematic requirements capture, decomposition, and traceability
requirements-traceability-manager
Design control traceability skill for managing user needs, design inputs, design outputs, and verification/validation linkages
requirements-engineering
Automotive requirements management and traceability expertise
requirements-verification
Skill for aerospace requirements verification and validation matrix management
interview-questions
Generate competency-based and behavioral interview questions with legal compliance validation
requirements-quality-analyzer
Specialized skill for analyzing and scoring requirements quality against BABOK and IEEE 29148 standards
interview-simulator
Simulate realistic coding interview experience
interview-problem-bank
Curated bank of interview problems organized by company, pattern, and difficulty. Provides problem recommendations, coverage tracking, weak area identification, and premium problem alternatives for FAANG interview preparation.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)