prd/standards

Apply BMAD standards to create and validate dual-audience PRDs.

5|3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/NexusSema/omg-marketplace --skill prd-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd/standards
Source: https://github.com/NexusSema/omg-marketplace/tree/main/plugins/sdlc/skills/prd/standards
Command: npx skills add https://github.com/NexusSema/omg-marketplace --skill prd-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

BMAD PRD methodology delivers dual-audience, information-dense product requirements ensuring traceability from vision to development.

Core Features & Use Cases

  • Dual-audience structure aligning human stakeholders and LLM downstream workloads
  • SMART FR/NFR guidance with anti-patterns, traceability, and domain-aware requirements
  • Reference data and templates to accelerate PRD creation and validation

Quick Start

Create a new PRD using BMAD standards and populate the Executive Summary, Success Criteria, Product Scope, User Journeys, FRs, NFRs, and Domain Requirements sections.

Frequently Asked Questions about prd/standards

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

FAQPage Schema
How do I write a PRD with traceability from vision to functional requirements?

To write a PRD with traceability, apply BMAD standards to map product vision directly to functional requirements, user journeys, and success criteria using standardized templates and a consistent Level 2 heading structure.

What is dual-audience PRD documentation for LLM workloads?

Dual-audience PRD documentation is a structured format that aligns information for human stakeholders while providing dense, traceable context for downstream LLM workloads to process architecture and development tasks accurately.

What sections are required for a complete BMAD product requirements document?

A complete BMAD product requirements document requires an Executive Summary, Success Criteria, Product Scope, User Journeys, Functional Requirements, Non-Functional Requirements, Domain Requirements, and Reference Data formats.

How do I validate SMART functional and non-functional requirements in a PRD?

To validate SMART functional and non-functional requirements in a PRD, apply BMAD quality standards that check for anti-patterns, ensure domain-aware specifications, and verify traceability across the product scope.

Can I use BMAD templates for editing existing product and UX requirements?

Yes, you can use BMAD templates for editing existing product, architecture, and UX requirements by validating them against dual-audience quality standards and restructuring them with the standardized Level 2 headings.

What is the best way to structure domain requirements and reference data in a PRD?

The best way to structure domain requirements and reference data in a PRD is to use BMAD standardized templates that enforce a consistent Level 2 heading structure, ensuring information density and downstream traceability.