Agent skill · product strategy · aiskillstore
requirements-elicitation
Requirements gathering and elicitation techniques for business analysis. Use when conducting stakeholder interviews, gathering functional/non-functional requirements, or identifying gaps in requirements.
Why this skill is useful
Provides structured techniques for gathering and analyzing requirements that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Requirements Elicitation Skill Overview This skill provides structured techniques for gathering, analyzing, and documenting software requirements from stakeholders and existing systems. Elicitation Techniques 1. Structured Interviews Use predefined question sets organized by category: Start with open-ended questions to understand context Follow with specific questions to gather details End with validation questions to confirm understanding 2. Adaptive Questioning Dynamically adjust questions based on: Previous answers provided Domain context discovered Gaps identified in requirements Stakeholder role and expertise level 3. Document Analysis Extract requirements from existing: Business process documents User manuals Training materials Support tickets and feedback 4. Observation Understand requirements by observing: Current system usage User workflows Pain points and workarounds Requirement Categories Functional Requirements (FR) What the system must DO: Features and capabilities Business rules and logic Data processing requirements User interactions Non-Functional Requirements (NFR) How the system must BEHAVE: FURPS+ Model Functionality: Security, compliance Usability: Accessibility, learnability Reliability: Availability, fault tolerance Performance: Response time, throughput Supportability: Maintainability, testability +Constraints: Design, implementation, interface Constraints Limitations on the solution: Budget constraints Timeline constraints Technology constraints Regulatory constraints Resource constraints Assumptions Conditions assumed to be true: User capabilities Infrastructure availability Third-party dependencies Business conditions Prioritization Methods MoSCoW Method Must Have: Critical for success, non-negotiable Should Have: Important but not critical Could Have: Nice to have, low impact if absent Won't Have: Out of scope for current release Value vs Effort Matrix Gap Analysis Process 1. Document As-Is State: Current capabilities 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/requirements-elicitation