bmad-create-prd

Guide users through a structured workflow to create Product Requirements Documents.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/geekdesign27/travailleursisoles --skill bmad-create-prd-geekdesign27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/geekdesign27/travailleursisoles/tree/main/_bmad/core/tasks/bmad-create-prd
Command: npx skills add https://github.com/geekdesign27/travailleursisoles --skill bmad-create-prd-geekdesign27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Product Requirements Documents (PRDs) from initial concept to polished artifact, ensuring comprehensive coverage and structured output.

Core Features & Use Cases

  • Guided Workflow: Follows a step-by-step process to gather all necessary information for a PRD.
  • Content Generation: Drafts sections like Executive Summary, Success Criteria, User Journeys, Functional Requirements, and Non-Functional Requirements.
  • Use Case: When a user wants to create a new product requirements document, this Skill will guide them through defining the product vision, scope, requirements, and ensuring a polished, ready-to-use document.

Quick Start

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

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 product requirements document from scratch?

Yes, a guided workflow helps draft a PRD by facilitating collaborative discovery to define product vision, scope, and functional requirements. It ensures the output is both human-readable and LLM-consumable.

What sections should be included in a product requirements document?

A PRD should include an Executive Summary, Success Criteria, User Journeys, Functional Requirements, and Non-Functional Requirements. Structuring these sections ensures comprehensive coverage and a ready-to-use document.

How do I gather requirements for a new product vision?

Gather requirements for a product vision through collaborative discovery. This structured process guides you step-by-step to define success criteria, user journeys, and project scope, translating the initial concept into functional requirements.

Can I generate an LLM-consumable PRD for product management workflows?

Yes, you can generate an LLM-consumable PRD by leveraging step-file architecture during the document creation process. This ensures the final product requirements output is structured for both human readability and automated processing.

What is the best way to structure functional and non-functional requirements?

The best way to structure functional and non-functional requirements is through a step-by-step workflow that separates these elements clearly. This approach ensures your PRD covers all necessary project scope details and success criteria.