bmad-create-prd

Create product requirements documents from discovery inputs and project artifacts.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-create-prd-imaginerlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/ImaginerLabs/skill-manager/tree/main/.trae/skills/bmad-create-prd
Command: npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-create-prd-imaginerlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates ad-hoc PRD drafting by guiding product teams through a disciplined, step-file workflow that discovers input documents, enforces sequence and state tracking, and produces a traceable, LLM-friendly Product Requirements Document.

Core Features & Use Cases

  • Step-file orchestration: Sequential step files that must be read and executed in order, with strict continuation and state-management rules.
  • Template-driven output: Initializes PRD from a template, tracks inputDocuments and stepsCompleted in frontmatter, and appends approved sections to an output file.
  • Discovery & domain awareness: Discovers planning artifacts, optional domain-specific checks, project-type configuration lookups, and supports brownfield vs greenfield flows.
  • Use case: A PM importing existing project docs to create a compliant PRD that traces vision → success criteria → journeys → functional and non-functional requirements while preserving review gates.

Quick Start

Invoke the bmad-create-prd workflow and follow the step-01-init prompts to initialize the PRD workspace and load any input documents.

Frequently Asked Questions about bmad-create-prd

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

FAQPage Schema
How do I create a structured product requirements document from existing project artifacts?

A structured PRD workflow discovers your planning artifacts and enforces a sequential step-file process with state tracking to generate a traceable document. It initializes from a template, tracks inputs in frontmatter, and appends approved sections to produce a polished output.

What is the best way to map user journeys and define success criteria during product discovery?

To map user journeys and define success criteria, use a structured discovery workflow that synthesizes planning artifacts into functional requirements. This process enforces sequential review gates to ensure vision, success criteria, and journeys are traceable in the final document.

Can I generate a PRD for both greenfield and brownfield projects?

Yes, you can generate a PRD for both greenfield and brownfield projects. The workflow includes optional domain-specific checks and project-type configuration lookups to adapt the document generation process to your existing project context.

How do I maintain review gates when drafting product requirements?

You maintain review gates when drafting product requirements by using a workflow with explicit continue and approval controls. This ensures safe, reviewable appends to the output file only after each sequential step is explicitly approved.

Does this PRD workflow require specific input document formats?

No specific input document formats are required, but the workflow discovers planning artifacts from your workspace to initialize the process. It tracks these input documents in the frontmatter of the generated template to maintain traceability.