doc-brd

Create Layer 1 BRD artifacts defining business needs and strategic objectives.

16|3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-brd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-brd
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-brd
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-brd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates BRD documents that define business needs, objectives, and success metrics, ensuring alignment with downstream PRD, EARS, BDD, and ADR.

Core Features & Use Cases

  • Document business objectives, stakeholders, risks, and success metrics
  • Establish traceability to downstream artifacts
  • Provide structure and templates for BRD creation

Quick Start

Begin with a BRD template to capture business goals, success metrics, and high-level requirements.

Frequently Asked Questions about doc-brd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a BRD and why do I need one for my project?

A Business Requirements Document (BRD) captures high-level business objectives, stakeholder needs, and success metrics to establish strategic alignment before development. It defines what problem you're solving and why, ensuring downstream artifacts like PRDs and technical specifications stay aligned with business goals.

How do I create a BRD with proper traceability to downstream artifacts?

Start with a BRD template to document business objectives, stakeholders, risks, and success metrics. Apply ID formatting rules and traceability references that link to downstream artifacts—PRD, EARS, BDD, and ADR—so each requirement can be tracked through the full workflow.

What should a BRD include to satisfy preflight checks and guidelines?

A complete BRD must document business objectives, stakeholder needs, success metrics, and risks while following ID formatting rules and traceability conventions. It establishes the foundation for downstream artifact planning, ensuring consistency across PRD, EARS, BDD, and ADR documents.

When should I use a BRD in the SDD workflow?

Apply a BRD at the start of new projects or features to capture business objectives and strategic alignment before creating detailed requirements. It's a Layer 1 artifact in the SDD workflow that precedes PRD and technical specification work.

Can a BRD help align stakeholders on project success?

Yes. A BRD documents stakeholder needs, business objectives, and success metrics in a shared format, creating alignment across teams on what defines project success and ensuring everyone understands the strategic rationale before development begins.