Create business requirements documents from product ideas, stakeholder requests, meeting notes, strategy context, opportunity briefs, customer signals, or synthesized intake. Use before PRD creation when the business objective, target segment, success metrics, constraints, ownership, and approval path need to be clarified.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-management-tools:brd-createThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `../../references/product-management-principles.md` for general product
Use ../../references/product-management-principles.md for general product
management principles. Apply discovery, metrics, prioritization, delivery, and
common failure mode sections when creating a business requirements document.
Treat the BRD as the bridge between strategy and product execution. The goal is not to specify every feature; it is to justify the investment, define business outcomes, clarify constraints, and create a decision-ready basis for PRD work.
Use this default structure unless the user provides a house format:
Return a concise BRD plus:
business-requirements-review, artifact-alignment,
or prd-create.The BRD should allow leadership, product, design, engineering, GTM, operations, and support to understand the business case and decide whether PRD work should begin.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub iam-jonny/jonny-agent-skills --plugin product-management-tools