requirements-interview
npx machina-cli add skill a5c-ai/babysitter/requirements-interview --openclawRequirements 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.jsPhase 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-generationskill
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/maestro/skills/requirements-interview/SKILL.mdView on GitHub Overview
Requirements Interview conducts interactive PM interviews that adapt to the user's expertise level to elicit clear requirements. It generates structured requirement specifications from dialogue, identifying personas, features, constraints, and acceptance criteria.
How This Skill Works
The engine uses Read to inspect project context, Grep/Glob to locate existing requirements, and Write to produce the final spec. It tailors question depth across beginner, intermediate, and expert modes, and feeds output to the specification-generation skill.
When to Use It
- Kickoff interviews to gather high-level personas, features, and constraints
- Refining requirements when existing specs are sparse or outdated
- Aligning acceptance criteria with stakeholder expectations
- Balancing depth in teams with mixed expertise (beginner to expert)
- Integrating interview outputs into the downstream specification-generation workflow
Quick Start
- Step 1: Use Read to load project context and any existing specs
- Step 2: Run the adaptive PM interview to elicit requirements across personas, features, constraints, and acceptance criteria
- Step 3: Use Write to generate the requirements specification and pass it to specification-generation
Best Practices
- Identify core personas and goals at the start
- Ask open-ended questions, then tighten with acceptance criteria
- Leverage Read/Grep/Glob to connect to existing docs and references
- Adjust depth based on the user role: guided for beginners, balanced for intermediates, concise for experts
- Validate outputs with stakeholders and iterate before finalizing the spec
Example Use Cases
- Interview a junior PM to surface core features for a mobile app
- Interview a software architect to capture system constraints and integrations
- Map customer personas to a feature backlog for an e-commerce checkout
- Consolidate disparate notes into a formal spec using the toolchain
- Coordinate with the downstream specification-generation step to ensure alignment
