bmad-create-prd

Creates comprehensive product requirements documents through a structured 12-step workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-create-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/KatTate/Bmad-for-Replit/tree/main/.agents/skills/bmad-create-prd
Command: npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-create-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive Product Requirements Documents (PRDs) by guiding users through a structured planning workflow.

Core Features & Use Cases

  • Structured Workflow Facilitation: Guides users through 12 distinct steps for PRD creation, including discovery, metrics, user journeys, and requirements.
  • Comprehensive Documentation: Ensures all critical aspects of a product are considered, from initial concept to non-functional requirements.
  • Use Case: When a user needs to define requirements for a new software feature, they can activate this skill to ensure a thorough and well-documented PRD is generated.

Quick Start

Use the bmad-create-prd skill to start creating a product requirements document.

Frequently Asked Questions about bmad-create-prd

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

FAQPage Schema
What is the best way to structure a product requirements document?

This Skill guides PRD creation through 12 distinct steps, including discovery, metrics, user journeys, and functional requirements. It ensures document coherence and completeness via dedicated polish and completion steps.

How do I write functional and non-functional requirements for a new software feature?

You can generate functional and non-functional requirements by activating the bmad-create-prd skill. It automates comprehensive PRD creation by guiding you through a structured, multi-step workflow covering all critical product aspects.

Do I need any specific tools to generate product requirements documentation?

No external tools are needed. The Skill operates independently without dependencies, allowing you to start creating a product requirements document directly through its structured planning workflow.

What should be included in product planning discovery and scoping?

Product planning discovery and scoping should include initial concept analysis, success metrics, user journeys, and domain modeling. Addressing these ensures a comprehensive and well-documented product plan.

How does a multi-step workflow improve requirements gathering?

A multi-step workflow improves requirements gathering by breaking product planning into distinct phases like discovery and user journeys. This structured approach ensures document coherence, completeness, and thorough functional coverage.

Can I use this approach to document innovation analysis and domain modeling?

Yes, you can document innovation analysis and domain modeling. The workflow explicitly covers these areas to ensure all critical product aspects are considered from the initial concept through to final non-functional requirements.