bmad-create-prd

Migrate legacy PRD creation requests into the unified bmad-prd workflow.

1|Updated Mar 31, 2026

Search Tags:#workflow #markdown #spec-driven development #prd #product requirements #bmad

Ready to run

npx skills add https://github.com/mol4/BMAD-Board --skill bmad-create-prd-mol4

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-create-prd
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-create-prd-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create product requirements documents without juggling legacy entry points, keeping PRD creation consistent across BMAD projects.

Core Features & Use Cases

Legacy Compatibility: Preserves older bmad-create-prd invocations while directing them into the current bmad-prd workflow.
Config-Aware PRD Creation: Loads project configuration and legacy customization values so existing overrides still apply.
Deactivation Guidance: Notifies users that the old skill is deprecated and points them to the supported path.
Use Case: A team with existing automation or custom overrides can keep generating PRDs while gradually migrating to the newer workflow.

Quick Start

Ask the assistant to create a PRD for your BMAD project using the current workflow and existing customization settings.

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 for a BMAD project?▼

To create a product requirements document for a BMAD project, this skill loads your project configuration and forwards your request into the unified bmad-prd workflow, preserving any existing legacy customizations.

What is spec-driven development workflow migration for markdown PRDs?▼

Spec-driven development workflow migration redirects legacy product requirements document creation requests into a unified markdown workflow while preserving older customization overrides and emitting a deprecation notice.

How do I update or validate an existing PRD with legacy customization overrides?▼

Updating or validating an existing PRD applies your resolved legacy workflow settings and configuration overrides by forwarding your original intent into the current create mode workflow.

Can I use legacy bmad-create-prd invocations with the newer workflow?▼

Yes, legacy bmad-create-prd invocations are supported through compatibility routing that preserves older requests while directing them into the current bmad-prd workflow with a deprecation notice.

Why does my PRD creation request show a deprecation notice?▼

A deprecation notice appears because the old PRD creation skill is deprecated, pointing you to the supported unified workflow path while still processing your request using existing settings.

Do I need to reconfigure my BMAD repository settings to generate product requirements?▼

No, you do not need to reconfigure settings because the skill loads existing BMAD configuration and resolves legacy workflow settings automatically to apply your current overrides during PRD generation.