Skip to content
requirements-elicitation logo

Requirements Elicitation Skill

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.

aiskillstore/marketplace0installs430stars

SKILL.md

Full skill instructions

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

High Value + Low Effort  = Do First (Quick Wins)
High Value + High Effort = Do Second (Major Projects)
Low Value + Low Effort   = Do Later (Fill-ins)
Low Value + High Effort  = Don't Do (Time Wasters)

Gap Analysis Process

  1. Document As-Is State: Current capabilities
  2. Define To-Be State: Desired capabilities
  3. Identify Gaps: Missing capabilities
  4. Prioritize Gaps: By business value
  5. Create Requirements: To close gaps

Validation Techniques

Requirement Quality Checks

Each requirement should be:

  • Complete: All necessary information included
  • Consistent: No conflicts with other requirements
  • Unambiguous: Single clear interpretation
  • Verifiable: Can be tested/​measured
  • Traceable: Linked to business objective

SMART Criteria

  • Specific: Clear and precise
  • Measurable: Quantifiable success criteria
  • Achievable: Technically feasible
  • Relevant: Aligned with business goals
  • Time-bound: Has timeline context

INVEST Criteria (for User Stories)

  • Independent: Can be developed separately
  • Negotiable: Open to discussion
  • Valuable: Delivers user/​business value
  • Estimable: Can be sized
  • Small: Fits in a sprint
  • Testable: Has clear acceptance criteria

Stakeholder Analysis

Stakeholder Categories

  1. End Users: Direct system users
  2. Business Owners: Decision makers
  3. Technical Team: Developers, architects
  4. Operations: Support, maintenance
  5. External: Regulators, partners, customers

Stakeholder Mapping

For each stakeholder identify:

  • Role and responsibilities
  • Interest level (High/​Medium/​Low)
  • Influence level (High/​Medium/​Low)
  • Key concerns and priorities
  • Communication preferences

Output Artifacts

Requirements List

| ID | Category | Description | Priority | Status |
|----|----------|-------------|----------|--------|
| FR-001 | Functional | User can login with email | Must | Confirmed |
| NFR-001 | Performance | Page load < 3 seconds | Should | Pending |

User Story Format

As a [role]
I want [capability]
So that [business value]

Acceptance Criteria:
- Given [context]
- When [action]
- Then [outcome]

Requirement Traceability

Business Objective -> Requirement -> User Story -> Test Case

See question-templates.md for structured interview questions.

More skills from aiskillstore

docx logo
aiskillstore/marketplace

docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

430 216
View
agent-development logo
aiskillstore/marketplace

agent-development

This handles everything around building autonomous agents for Claude Code plugins.

430 197
View
doc-coauthoring logo
aiskillstore/marketplace

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

430 196
View
skill-development logo
aiskillstore/marketplace

skill-development

This is the meta-skill for building skills themselves.

430 196
View
canvas-design logo
aiskillstore/marketplace

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

430 193
View
webapp-testing logo
aiskillstore/marketplace

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

430 191
View
hook-development logo
aiskillstore/marketplace

hook-development

Helps you build event-driven automation for Claude Code using hooks that trigger on tool use, session events, and stop conditions.

430 187
View
algorithmic-art logo
aiskillstore/marketplace

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

430 185
View
command-development logo
aiskillstore/marketplace

command-development

Shows Claude Code how to build slash commands from markdown files, covering the YAML frontmatter options, dynamic arguments with $1/$2...

430 185
View
plugin-structure logo
aiskillstore/marketplace

plugin-structure

This is your reference when scaffolding Claude Code plugins or figuring out why components aren't loading.

430 183
View
skill-installer logo
aiskillstore/marketplace

skill-installer

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

430 180
View
web-artifacts-builder logo
aiskillstore/marketplace

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

430 177
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View