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/JohnnyWang1998/job-market-tracker --skill bmad-create-prd-johnnywang1998
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/JohnnyWang1998/job-market-tracker/tree/main/_bmad/core/tasks/bmad-create-prd
Command: npx skills add https://github.com/JohnnyWang1998/job-market-tracker --skill bmad-create-prd-johnnywang1998

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs), ensuring clarity, alignment, and a solid foundation for product development.

Core Features & Use Cases

  • Structured Workflow: Guides users through a step-by-step process for defining vision, scope, requirements, and more.
  • Collaborative Facilitation: Acts as a PM facilitator, prompting for essential details and ensuring all critical aspects are covered.
  • Use Case: A product manager needs to create a PRD for a new feature. They activate this Skill, which walks them through defining the problem, target users, success criteria, functional and non-functional requirements, and finally polishes the document for downstream use.

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

To create a product requirements document, this Skill facilitates a structured, multi-step workflow guiding you through vision, scope, functional requirements, and user journeys to ensure a comprehensive output.

What should be included in a PRD for downstream development?▼

A PRD for downstream development should include vision, success criteria, user journeys, and both functional and non-functional requirements, which this Skill systematically covers and polishes.

Can I use this workflow to define non-functional requirements and success criteria?▼

Yes, you can define non-functional requirements and success criteria using this Skill, as it explicitly prompts for these essential details during its step-by-step product management facilitation process.

What is the best way to structure product vision and scoping for a new feature?▼

The best way to structure product vision and scoping is through a collaborative facilitation process, which guides you step-by-step to define the problem, target users, and project boundaries.

Does this PRD generator require any specific frameworks or dependencies to run?▼

No specific frameworks or dependencies are required to run this PRD generator, as it operates independently using internal scripts and references to guide the requirements gathering workflow.

Why use a structured workflow for product requirements gathering instead of a standard template?▼

A structured workflow for product requirements gathering ensures clarity and alignment by actively prompting for essential details across all critical aspects, preventing gaps that static templates often miss.