bmad-create-prd

Forwards legacy PRD creation invocations to the bmad-prd workflow with create intent.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-create-prd-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/2-plan-workflows/bmad-create-prd
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-create-prd-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing projects and customization files that still reference the retired bmad-create-prd skill would break after upgrading BMAD; this compatibility shim keeps those invocations working while guiding users to the consolidated bmad-prd workflow. ## Core Features & Use Cases - Backward Compatibility: Resolves legacy bmad-create-prd.toml and bmad-create-prd.user.toml overrides so existing customizations keep working. - Deprecation Notice: Emits a localized warning telling users to migrate their customization files to bmad-prd.toml before v7 removes this skill. - Intent Forwarding: Invokes bmad-prd with a fixed create intent, passing pre-resolved legacy fields and the original user input verbatim. - Use Case: A team upgraded BMAD but still has _bmad/custom/bmad-create-prd.toml in their repo; invoking the old skill name still produces a PRD while warning them to migrate. ## Quick Start Invoke the bmad-create-prd skill by name and it will show a deprecation notice, then run the bmad-prd workflow in create mode using your existing customization overrides.

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 PRD with BMAD after bmad-create-prd was deprecated?▼

Invoke bmad-prd directly instead of bmad-create-prd. The bmad-prd workflow detects create, update, or validate intent from the conversation, so asking it to create a PRD produces the same result as the old skill.

What happens to my bmad-create-prd.toml customization file?▼

The shim still resolves legacy fields like activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete from bmad-create-prd.toml. Migrate the file to _bmad/custom/bmad-prd.toml to silence the deprecation notice and access new fields.

When will bmad-create-prd be removed?▼

The skill is marked deprecated and scheduled for removal in BMAD v7. It currently exists only as a thin compatibility shim that forwards all work to bmad-prd.

Why do I see a deprecation notice when running bmad-create-prd?▼

The notice appears because the skill was consolidated into bmad-prd. It is emitted in your configured communication language and explains how to migrate your customization file to bmad-prd.toml to silence it.

Does bmad-create-prd still execute the PRD workflow itself?▼

No. After resolving legacy customization and loading config, it forwards everything to bmad-prd with create intent and the original user input, then stops. All PRD generation logic lives in bmad-prd.