babok-elicitation

Facilitate structured requirements elicitation and classification using BABOK v3 techniques.

2|Updated May 4, 2026

Search Tags:#requirements #analysis #stakeholder #elicitation #software #business #BABOK

Ready to run

npx skills add https://github.com/volodchenkov/claude-sdlc-agents --skill babok-elicitation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: babok-elicitation
Source: https://github.com/volodchenkov/claude-sdlc-agents/tree/main/skills/babok-elicitation
Command: npx skills add https://github.com/volodchenkov/claude-sdlc-agents --skill babok-elicitation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Business Analysts efficiently elicit clear and structured requirements from stakeholders, reducing ambiguity and improving communication.

Core Features & Use Cases

Requirement Elicitation: Implements BABOK techniques like interviews, document analysis, and stakeholder analysis to gather comprehensive requirements.
Requirement Classification: Categorizes needs into Business, Stakeholder, Solution, and Transition types to ensure complete coverage.
Use Case Scenario: A Business Analyst conducts a structured interview to determine the scope of a new order tracking feature, accurately capturing functional and transition needs to facilitate development.

Quick Start

Use the babok-elicitation skill to analyze stakeholder needs for a new feature and categorize requirements accordingly.

Frequently Asked Questions about babok-elicitation

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

FAQPage Schema

How do I elicit structured requirements from stakeholders for a software project?▼

Structured requirements elicitation uses BABOK v3 techniques like interviews, document analysis, and stakeholder mapping to capture categorized needs, reducing ambiguity and improving communication for project success.

What is the best way to classify business and stakeholder needs during analysis?▼

Classifying business and stakeholder needs involves categorizing elicited requirements into Business, Stakeholder, Solution, and Transition types to ensure complete project coverage and facilitate accurate development.

How do I conduct a root cause analysis for software requirements gathering?▼

Root cause analysis for requirements gathering is facilitated by applying structured elicitation techniques to identify underlying stakeholder needs, ensuring a comprehensive understanding of the project scope.

Does this requirements elicitation approach support transition requirements for new features?▼

Yes, this requirements elicitation approach supports transition requirements by categorizing captured needs into Business, Stakeholder, Solution, and Transition types to facilitate comprehensive software development.

Can I use document analysis to determine the scope of a new software feature?▼

Document analysis is a supported elicitation technique used alongside stakeholder interviews to determine the scope of new features, accurately capturing functional and transition requirements for development.