Requirements Gathering

This is a structured approach to collecting and documenting what you're building before you build it. You get frameworks for stakeholder discovery, elicitation techniques, documentation templates, and a traceability matrix to connect requirements to implementation. The stakeholder categorization (primary, secondary, tertiary) and MoSCoW prioritization method are solid fundamentals. Honestly, the value here is less about novel techniques and more about having a checklist so you don't skip the boring but critical step of getting everyone aligned on paper. Most projects fail because requirements were assumed, not because the code was bad. Use this at project kickoff or when adding major features.

skills.sh installs: 663
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill requirements-gathering --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Effective requirements gathering establishes a shared understanding of what will be built, preventing misalignment and expensive changes later in the project.

When to Use

Project kickoff and planning
Feature development initiation
Product roadmap planning
System modernization projects
Customer discovery
Stakeholder alignment sessions
Writing user stories and acceptance criteria

Quick Start

Minimal working example:

# Identify and analyze stakeholders

class StakeholderDiscovery:
    STAKEHOLDER_CATEGORIES = [
        'End Users',
        'Business Owners',
        'Technical Leads',
        'Operations/Support',
        'Customers',
        'Regulatory Bodies',
        'Integration Partners'
    ]

SKILL.md on GitHub