How do I install the Common Business Requirements skill?

Run npx skillmds@latest add hoangnguyen0403/common-business-requirements in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Common Business Requirements safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Common Business Requirements?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Common Business Requirements free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Common Business Requirements?

HoangNguyen0403 (@hoangnguyen0403) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Common Business Requirements by hoangnguyen0403

Name: Common Business Requirements
Rating: 4.666666666666667 (3 reviews)
Author: HoangNguyen0403

Common Business Requirements

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.

HoangNguyen0403 Updated Sep 9, 2026 542 repo stars

File contents

Business Requirements Expert

Priority: P0 (CRITICAL)

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

1. Discovery Workflow

Draft executive summary: purpose, outcome, sponsor, validation owner.
For vague "implement X" requests, draft BRD-lite first and ask only blocking BA questions with recommended defaults.
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.
Handoff Quality: Identify the Handoff Owner (BA Lead) and the next accountable team member (Product Manager).
Add glossary terms when stakeholder or domain language can be misread.
Add Mermaid AS-IS/TO-BE process diagram when workflow complexity affects approval.

2. BRD-lite Drafting

Load references/brd-template.md.
Keep each objective SMART: specific, measurable, achievable, relevant, and time-bound.
Link each BRD objective to a candidate PRD requirement placeholder (REQ-*).
Offshore Ready: Include stakeholder validation plan and acceptance window for remote delivery teams.
Add outcome report seed: feature_status, requirement_trace, completed/missing evidence, decision needed, and recommended next workflow (plan-feature).
Write to docs/brd/brd-[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.
Functional behavior is routed to PRD/SRS, not buried in BRD.

Anti-Patterns

No solution design in BRD.
No vague goals ("improve efficiency") without baseline and target.
No missing owners for objectives or risks.
No coding or QA routing before the BA owner, value metric, and scope fence are clear.
No silent scope expansion after approval.
No jargon without glossary entry.

References

BRD Template
BRD Checklist
Requirements Baseline

---name: common-business-requirementsdescription: 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.--- # Business Requirements Expert ## **Priority: P0 (CRITICAL)** Frame the business "Why" before product or technical specs. ## 1. Discovery Workflow - Draft executive summary: purpose, outcome, sponsor, validation owner. - For vague "implement X" requests, draft BRD-lite first and ask only blocking BA questions with recommended defaults. - 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. - **Handoff Quality**: Identify the **Handoff Owner** (BA Lead) and the next accountable team member (Product Manager). - Add glossary terms when stakeholder or domain language can be misread. - Add Mermaid AS-IS/TO-BE process diagram when workflow complexity affects approval. ## 2. BRD-lite Drafting - Load `references/brd-template.md`. - Keep each objective SMART: specific, measurable, achievable, relevant, and time-bound. - Link each BRD objective to a candidate PRD requirement placeholder (`REQ-*`). - **Offshore Ready**: Include stakeholder validation plan and acceptance window for remote delivery teams. - Add outcome report seed: `feature_status`, `requirement_trace`, completed/missing evidence, decision needed, and recommended next workflow (`plan-feature`). - Write to `docs/brd/brd-[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. - Functional behavior is routed to PRD/SRS, not buried in BRD. ## Anti-Patterns - No solution design in BRD. - No vague goals ("improve efficiency") without baseline and target. - No missing owners for objectives or risks. - No coding or QA routing before the BA owner, value metric, and scope fence are clear. - No silent scope expansion after approval. - No jargon without glossary entry. ## References - [BRD Template](references/brd-template.md) - [BRD Checklist](references/checklist.md) - [Requirements Baseline](references/standards-baseline.md)

Frequently asked questions