Draft business requirements documents with traceable IDs, sign-offs, and dependencies.
npx skills add https://github.com/friedbotstudio/baseline --skill brd-friedbotstudio
Please help me install this Agent Skill. Skill: brd Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/brd Command: npx skills add https://github.com/friedbotstudio/baseline --skill brd-friedbotstudio
This Skill helps you turn a messy, cross-functional request into a clear Business Requirements Document that business stakeholders can review, approve, and trace back to measurable outcomes.
Use the brd skill to draft a sign-off-ready BRD from the intake and stakeholder context in docs/brd/<slug>.md.
High-intent search queries and answers about installing and using this skill.
A business requirements document formalizes complex cross-functional initiatives into traceable business, functional, and non-functional requirements that stakeholders can review, approve, and track against measurable outcomes.
Drafting a sign-off ready BRD requires capturing the business objective, scope, dependencies, risks, and milestones alongside labeled requirements with unique IDs so compliance teams and stakeholders can formally approve and trace the work.
Requirement traceability is structured by assigning unique IDs to business, functional, and non-functional requirements, ensuring downstream specs and tests can reference them precisely back to the approved scope and measurable outcomes.
Formal business analysis is needed for compliance-sensitive changes and cross-functional programs where work must preserve business goals independently of the implementation spec, requiring budget tracking and formal stakeholder sign-off.
Yes, this approach suits multi-team initiatives involving legal review, executive approval, and fixed delivery targets by producing a structured document that aligns stakeholder concerns and traces scope to business objectives.
Business requirements for scope management should include the business objective, labeled requirements with IDs, dependencies, risks, milestones, and open questions to ensure formal stakeholder sign-off and downstream traceability.
saolalabGather and validate stakeholder requirements into a traceability matrix and BRD.
issdandavisConvert Notion specs into implementation plans with linked tasks.
Yukine5377Generate an Impact Analysis package across six BA domains.
farmountainGenerate Product Requirements Documents with user stories and acceptance criteria.
