requirements-elicitation-workshop

Plan and execute structured requirements elicitation sessions using interviews, workshops, and observation.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-elicitation-workshop-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-elicitation-workshop
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/requirements-elicitation-workshop
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-elicitation-workshop-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ad-hoc stakeholder conversations often produce incomplete or inconsistent requirements. This Skill provides a repeatable, structured process for planning, facilitating, documenting, and synthesizing requirements elicitation sessions so nothing important is missed. ## Core Features & Use Cases - Session Planning: Build agendas, participant lists, and question sets for discovery workshops, deep-dive interviews, observation sessions, and review meetings. - Facilitation Guidance: Apply proven techniques like process walkthroughs, sticky-note brainstorming, and scenario walking, with rules for managing dominant participants. - Output Synthesis: Convert raw session notes into user stories, use cases, business rules, and data dictionary entries, then validate them with stakeholders. - Use Case: You have a 3-hour window with 5 stakeholders for a new project. Use this Skill to produce a complete session plan with timed agenda, probing questions, and a post-session documentation checklist. ## Quick Start Help me plan a 3-hour requirements discovery workshop with 5 stakeholders for a new inventory management project.

Frequently Asked Questions about requirements-elicitation-workshop

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

FAQPage Schema
How do I plan a requirements elicitation workshop?▼

Define a single-sentence objective, select 5-10 participants covering each user class, prepare a timed agenda with elicitation activities, and write context-free, context-specific, and solution-oriented questions. Budget 1-2 hours of preparation per session.

What elicitation techniques should I use in a requirements session?▼

Common techniques include process walkthroughs for mapping workflows, sticky-note brainstorming for pain points, scenario walking for edge cases, and MoSCoW or dot voting for prioritization. Combine multiple techniques within one session for broader coverage.

How long should a requirements discovery workshop last?▼

A discovery workshop typically runs 2-4 hours with 5-10 stakeholders, while deep-dive interviews run 1-2 hours with 1-2 domain experts. Longer sessions reduce participant productivity and engagement.

How do I handle a dominant stakeholder in a workshop?▼

Redirect with phrases like "That's helpful. Let's hear from others," and use round-robin formats where each participant shares one need. This prevents requirements from reflecting a single perspective.

What should I do after a requirements elicitation session?▼

Consolidate notes into structured requirements within 24 hours, flag open questions and stakeholder conflicts, map outputs to formats like user stories or use cases, and send drafts to participants within 48 hours for validation.