ba-elicitation

Plan and execute BABOK elicitation activities to gather and confirm stakeholder requirements.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill ba-elicitation-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba-elicitation
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/ba-elicitation
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill ba-elicitation-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Business analysts often collect stakeholder information without structure, leading to unconfirmed findings, biased interview questions, and requirements that reflect the sponsor's view rather than real user needs. This Skill operationalizes the BABOK v3 Elicitation & Collaboration knowledge area so elicitation results are planned, executed, and confirmed before feeding requirements work. ## Core Features & Use Cases - Technique Selection Guidance: Compares seven BABOK elicitation techniques (interviews, JAD workshops, shadowing, document analysis, surveys, focus groups, brainstorming) with when-to-use criteria, advantages, and limitations. - Execution Protocols: Provides step-by-step protocols for effective interview questions, JAD workshop phases, and shadowing observation, including questions to avoid that bias responses. - Mandatory Confirmation Workflow: Defines confirmation methods and deadlines per technique so findings are validated with stakeholders before propagating into requirements. - Use Case: A business analyst starting discovery on a call center system uses this Skill to plan interviews with supervisors, shadow agents, run a JAD workshop to resolve conflicts, and produce a confirmed elicitation notes document with articulated needs and identified gaps. ## Quick Start Ask the assistant to plan and run a BABOK elicitation cycle for your project, producing a confirmed elicitation notes document with stakeholder needs and gaps.

Frequently Asked Questions about ba-elicitation

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

FAQPage Schema
How do I plan stakeholder elicitation activities using BABOK?▼

Start from a BA plan with a defined stakeholder engagement approach, then select elicitation techniques matched to your context, such as interviews for depth or JAD workshops for alignment. Execute each technique, confirm results with stakeholders, and document findings in an elicitation notes artifact.

What elicitation technique should I use for requirements gathering?▼

Use interviews for deep exploration with key stakeholders, JAD workshops to align multiple stakeholders and resolve conflicts, shadowing to observe real processes, surveys to scale across many respondents, and document analysis when existing documentation is available.

How do I confirm elicitation results with stakeholders?▼

Send an interview summary by email within 48 hours, distribute JAD workshop minutes within 24 hours, and share shadowing observation summaries with the observed user within 24 to 48 hours. Confirmation ensures the analyst's interpretation is correct before requirements work begins.

What interview questions should business analysts avoid?▼

Avoid leading questions that suggest a solution, premature technical questions about dashboards or reports, and closed yes/no questions. Replace them with open prompts like asking the stakeholder to describe the current process step by step.

When should I not run an elicitation step?▼

Skip elicitation when requirements are already documented and confirmed, in which case move to requirements analysis, or when the task is evaluating whether an existing solution met needs, which belongs to solution evaluation.