Requirements Gathering

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Systematically collect, document, and validate requirements from stakeholders. Ensure clarity, completeness, and agreement before development begins to reduce scope creep and rework.

Instructions onlyProductivity & Workflow

AI-generated overview

Guides systematic collection, documentation, and validation of project requirements from stakeholders before development starts.

What it does: This skill provides guidance for gathering requirements from stakeholders, covering stakeholder discovery, elicitation techniques, documentation, validation and sign-off, and traceability matrices. It includes reference guides and a process template to structure the work. The output is a documented, validated set of requirements with acceptance criteria and stakeholder agreement.
When to use it: Use it at project kickoff, feature initiation, roadmap planning, system modernization, or customer discovery sessions. It fits situations where requirements must be clarified, documented, and agreed upon before development begins.
Requirements: No scripts or special tools are required; it is instructions and reference documents only. The agent needs access to the skill's reference guides and templates.

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:

python

# Identify and analyze stakeholders
class StakeholderDiscovery:    STAKEHOLDER_CATEGORIES = [        'End Users',        'Business Owners',        'Technical Leads',        'Operations/Support',        'Customers',        'Regulatory Bodies',        'Integration Partners'    ]
    def identify_stakeholders(self, project):        """Map all stakeholder groups"""        return {            'primary': self.get_primary_stakeholders(project),            'secondary': self.get_secondary_stakeholders(project),            'tertiary': self.get_tertiary_stakeholders(project),            'total_to_engage': self.calculate_engagement_strategy(project)        }
    def analyze_stakeholder_needs(self, stakeholder):        """Understand what each stakeholder needs"""        return {// ... (see reference guides for full implementation)

# Identify and analyze stakeholders
class StakeholderDiscovery:    STAKEHOLDER_CATEGORIES = [        'End Users',        'Business Owners',        'Technical Leads',        'Operations/Support',        'Customers',        'Regulatory Bodies',        'Integration Partners'    ]
    def identify_stakeholders(self, project):        """Map all stakeholder groups"""        return {            'primary': self.get_primary_stakeholders(project),            'secondary': self.get_secondary_stakeholders(project),            'tertiary': self.get_tertiary_stakeholders(project),            'total_to_engage': self.calculate_engagement_strategy(project)        }
    def analyze_stakeholder_needs(self, stakeholder):        """Understand what each stakeholder needs"""        return {// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
Stakeholder Discovery [blocked]	Stakeholder Discovery
Requirements Elicitation Techniques [blocked]	Requirements Elicitation Techniques
Requirements Documentation [blocked]	Requirements Documentation
Requirement Validation & Sign-Off [blocked]	Requirement Validation & Sign-Off
Requirements Traceability Matrix [blocked]	Requirements Traceability Matrix

Best Practices

✅ DO

Engage all key stakeholders early
Document requirements in writing
Use specific, measurable language
Define acceptance criteria
Prioritize using MoSCoW method
Get stakeholder sign-off
Create traceability matrix
Review requirements regularly
Distinguish must-haves from nice-to-haves
Document assumptions and constraints

❌ DON'T

Rely on memory or verbal agreements
Create requirements without stakeholder input
Use ambiguous language (quickly, easily, etc.)
Skip non-functional requirements
Ignore constraints and dependencies
Over-document trivial details
Rush through requirements phase
Build without stakeholder agreement
Make scope changes without process
Forget about edge cases and error conditions

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/requirements-gatheringat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Requirements Gathering

Requirements Gathering

Table of Contents

Overview

When to Use

Quick Start

Reference Guides

Best Practices

✅ DO

❌ DON'T

Source and attribution

More from aj-geddes/useful-ai-prompts

Xss Prevention

Wireframe Prototyping

Web Performance Optimization

Vue Application Structure

Visual Regression Testing

User Persona Creation

More in Productivity & Workflow

Dd Meeting Prep

Dd Checklist

Deal Tracker

Client Review

Morning Note

Notion Spec To Implementation