bmad-prd

Generate structured PRDs, architecture documents, epics, and user stories.

7|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/webdevtodayjason/titanium-plugins --skill bmad-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-prd
Source: https://github.com/webdevtodayjason/titanium-plugins/tree/main/plugins/titanium-toolkit/skills/bmad-methodology
Command: npx skills add https://github.com/webdevtodayjason/titanium-plugins --skill bmad-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This BMAD skill guides creating PRDs, Architecture Documents, Epics, and User Stories using the BMAD methodology, ensuring deep context, human-in-the-loop refinement, and hyper-detailed deliverables.

Core Features & Use Cases

  • Human-in-the-Loop Refinement: Collaborative clarification questions to sharpen requirements.
  • Context-Rich Documentation: Deep, decision-rich documentation rather than generic outputs.
  • Hyper-Detailed Stories: Each story contains implementation details, acceptance criteria, and design considerations.
  • No Generic Output: Avoid bland responses; dig into specifics.
  • Document Hierarchy: Project Brief (optional) → PRD → Architecture Document → Epics → User Stories.
  • Creating a Project Brief: Purpose, structure, best practices.
  • Creating a PRD: Goals, functional vs non-functional requirements, epics and stories.
  • BMAD Best Practices: discovery questions; be specific; reference supporting documents.

Quick Start

Initiate a BMAD session to draft a Project Brief for your product, then generate a PRD, architecture doc, epics, and user stories with unique identifiers and detailed acceptance criteria.

Frequently Asked Questions about bmad-prd

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

FAQPage Schema
How do I create structured PRDs with detailed requirements and user stories?

BMAD automates creation of structured PRDs, architecture documents, epics, and user stories with deep context, decision rationales, and hyper-detailed acceptance criteria—avoiding generic boilerplate through human-in-the-loop refinement and domain-specific templates.

What's the best way to organize product documentation from brief through epics to stories?

Follow the BMAD document hierarchy: Project Brief (optional) → PRD → Architecture Document → Epics → User Stories. Each level builds context and traceability, with unique identifiers and implementation details ensuring alignment across planning stages.

How do I write user stories with acceptance criteria and design considerations?

BMAD generates hyper-detailed user stories that include implementation details, acceptance criteria, design considerations, and decision rationales specific to your architecture and requirements—not generic templates.

Can I collaborate with stakeholders while refining requirements and PRDs?

Yes. BMAD uses human-in-the-loop refinement with collaborative clarification questions to sharpen requirements, ensuring stakeholder input shapes context-rich documentation rather than producing pre-formed outputs.

What's included in a BMAD architecture document for product planning?

BMAD architecture documents provide decision-rich specifications derived from PRD goals, functional and non-functional requirements, and epic-to-story traceability—supporting agile workflows requiring deep technical context and rationale.

When should I use BMAD methodology instead of lightweight requirement formats?

Use BMAD for projects requiring deep context, traceability, and hyper-detailed narratives across discovery, planning, and execution—especially when generic boilerplate risks missing critical design decisions and implementation details.