common-business-requirements git:20260522.3df717fA

Immutable. This exact content is served forever at /api/v1/blob/64b221f52b836ce9.

---
name: common-business-requirements
description: Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
metadata:
  triggers:
    files:
    - 'BRD.md'
    - 'docs/specs/product-brief-*.md'
    - 'specs/*.md'
    keywords:
    - create brd
    - business requirements
    - business case
    - stakeholder impact
    - as-is to to-be
    - roi justification
---
# Business Requirements Expert

## **Priority: P0 (CRITICAL)**

Frame the business "Why" before product or technical specs.

## 1. Discovery Workflow

- Confirm business objective and success metric.
- Identify sponsor, decision-maker, and impacted stakeholders.
- Capture AS-IS process pain and TO-BE target state.
- Define scope boundary, exclusions, assumptions, and constraints.
- Record value hypothesis: cost, revenue, risk, compliance, or cycle-time impact.

## 2. BRD-lite Drafting

- Load `references/brd-template.md`.
- Keep each objective measurable and time-bound.
- Link each BRD objective to a candidate PRD requirement placeholder (`REQ-*`).
- Write to `docs/specs/product-brief-[slug].md`.

## 3. Quality Gate

- Every objective has an owner and KPI target.
- Every in-scope item has a rationale and out-of-scope pair.
- Risk register includes mitigation owner.
- Stakeholder approvals and unresolved decisions are explicit.

## Anti-Patterns

- No solution design in BRD.
- No vague goals ("improve efficiency") without baseline and target.
- No missing owners for objectives or risks.
- No silent scope expansion after approval.

## References

- [BRD Template](references/brd-template.md)
- [BRD Checklist](references/checklist.md)
- [Requirements Baseline](references/standards-baseline.md)