po-brd

Create BRD documentation with problem statements, OKRs, and market analysis.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill po-brd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: po-brd
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/po-brd
Command: npx skills add https://github.com/Yukine5377/common --skill po-brd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BRD writing can be time-consuming and inconsistent across teams, making it hard to secure leadership buy-in and align stakeholders.

Core Features & Use Cases

  • Structured BRD templates covering problem statements, business goals, market analysis, competitive landscape, and product vision.
  • Stakeholder alignment artifacts: RACI-like mapping, OKRs, and review checkpoints.
  • Reusable sections for rapid planning and cross-team communication during discovery, strategy, and execution.

Quick Start

Provide a concise BRD outline with market opportunity, stakeholders, and high-level goals, then flesh out the sections to finalize the document.

Frequently Asked Questions about po-brd

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

FAQPage Schema
How do I write a BRD that secures leadership buy-in and aligns stakeholders?

To write a BRD that secures leadership buy-in, structure your document with enforced sections for problem statements, OKRs, market analysis, competitive analysis, product vision, and risk management to ensure complete stakeholder alignment.

What components should be included in a business requirements document for product discovery?

A business requirements document for product discovery should include problem statements, business goals, market data, stakeholder feedback, competitive landscape analysis, product vision, and a RACI-like mapping for stakeholder alignment.

How do I structure OKRs and market analysis within a product management BRD?

Structure OKRs and market analysis within a BRD by using reusable templates that enforce specific sections for high-level goals, market opportunity, competitive landscape, and review checkpoints to finalize a review-ready document.

Can I use this BRD template for cross-team communication during strategy and execution phases?

Yes, you can use this BRD template for cross-team communication during strategy and execution phases because it provides reusable sections and RACI-like stakeholder mapping artifacts designed for rapid planning.

What is the best way to standardize business requirements documents across multiple product teams?

The best way to standardize business requirements documents across teams is applying a structured template that enforces problem statements, OKRs, market analysis, and risk management to eliminate inconsistencies during discovery and planning.

What inputs do I need to provide to generate a complete BRD for stakeholder review?

To generate a complete BRD for stakeholder review, you need to provide inputs such as problem statements, business goals, market data, and stakeholder feedback to flesh out the review-ready document sections.