brd

Generate a formal BRD from stakeholder input and business context.

1|Updated Mar 31, 2026

Search Tags:#traceability #business requirements #product-management #brd #stakeholder input #documentation-chain

Ready to run

npx skills add https://github.com/shirogin/jesuph-skills --skill brd-shirogin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brd
Source: https://github.com/shirogin/jesuph-skills/tree/main/.agents/skills/brd
Command: npx skills add https://github.com/shirogin/jesuph-skills --skill brd-shirogin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a formal BRD from stakeholder input and business context to capture WHY the project exists, align business objectives, and set measurable requirements.

Core Features & Use Cases

Structured BRD template capturing WHY, business requirements, and traceability to downstream artifacts (PRD, FRD, SOW).
Orchestrates Step 1 of the doc-chain: BRD→PRD→FRD→SOW with clear handoffs and recommended next steps.
Supports traceability and documentation discipline, including executive summaries, stakeholder analyses, assumptions, risk registers, and success criteria.

Quick Start

Provide stakeholder input and specify a save location to start the BRD workflow.

Frequently Asked Questions about brd

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

FAQPage Schema

How do I create a formal Business Requirements Document from stakeholder input?▼

To create a formal Business Requirements Document (BRD), you provide stakeholder input and business context. The system automates generation of a structured BRD capturing project rationale, requirements, and traceability to downstream artifacts.

What is the documentation chain for product management and where does the BRD fit?▼

The documentation chain sequence is BRD to PRD to FRD to SOW. The BRD fits at step one to capture why the project exists, align business objectives, and set measurable requirements for downstream documents.

How do I ensure traceability from business requirements to downstream PRD and FRD artifacts?▼

Traceability to downstream PRD and FRD artifacts is enforced through explicit documentation chain handoffs. The BRD establishes clear traceability links and recommended next steps for subsequent product and functional requirement documents.

Can I use structured BRD templates for diverse business initiatives without manual formatting?▼

Structured BRD templates are applied automatically for diverse business initiatives. By providing stakeholder input and specifying a save location, the workflow enforces template discipline without requiring manual document formatting.

What do I need to start the BRD workflow and generate a formal document?▼

To start the BRD workflow you need stakeholder input and a specified save location. Providing this business context triggers automated generation of the formal BRD artifact with structured templates and risk tracking.

Why does my business requirements documentation lack traceability to downstream artifacts?▼

Business requirements documentation lacks traceability when not using a structured BRD template. Enforcing explicit traceability to downstream PRD, FRD, and SOW documents ensures alignment and clear handoffs across the documentation chain.