BRD Gathering
This skill provides structured guidance for gathering comprehensive business requirements for a Business Requirements Document (BRD).
Description
Use this skill to systematically collect all necessary information needed to create a complete BRD. The skill helps identify stakeholders, business objectives, functional requirements, non-functional requirements, and other critical components.
Instructions
When activated, follow this process:
- •
Confirm the outcome: Ask what the user wants at the end of this exercise:
- •A full BRD (Markdown), a BRD outline, or just a validated requirements list
- •Audience and approval process (who signs off)
- •
Problem + Current State (As-Is):
- •What problem are we solving?
- •What exists today (systems, workflows, docs, pain points, constraints)?
- •What happens if we do nothing?
- •
Desired Outcome (To-Be):
- •What should be true when the project is done?
- •What are the top 3 user/business outcomes?
- •
Stakeholder Analysis + Decision Makers:
- •Business owner / sponsor
- •Primary users
- •Approvers / compliance
- •Technical owners
- •External dependencies
- •
Business Objectives + Benefits:
- •Benefits/value (cost savings, revenue, risk reduction, time saved)
- •Expected impact and who benefits
- •Why now?
- •
Scope (In/Out):
- •In scope: what capabilities are included
- •Out of scope: what is explicitly not included
- •Phasing: v1 vs later
- •
Success Metrics + Acceptance Criteria:
- •Success metrics (KPIs) with targets and measurement method
- •Acceptance criteria per major requirement
- •
Functional Requirements: Collect detailed requirements about:
- •Business processes to be supported
- •User interactions and workflows
- •Data requirements and processing
- •
Non-Functional Requirements: Identify:
- •Performance requirements
- •Security and compliance needs
- •Usability and accessibility requirements
- •Integration requirements
- •
Constraints, Assumptions, Dependencies: Document:
- •Technical constraints
- •Budget and timeline constraints
- •Business assumptions and dependencies
- •
Risk Assessment: Identify potential risks and mitigation strategies.
- •
Confirm completeness: Summarize findings as a short “BRD Brief”, list open questions (TBDs), and ask the user to confirm/correct.
Ask probing questions to ensure completeness and clarity. Use follow-up questions when information is vague or incomplete.
Examples
Example usage: "Help me gather requirements for a new customer management system."