bmad-create-prd

Name: bmad-create-prd
Availability: InStock
Author: Marc

Forward legacy PRD creation requests to the bmad-prd engine.

Updated Jul 11, 2026

Search Tags:#workflow #documentation #compatibility #migration #prd #bmad

Ready to run

npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-create-prd-marcmontecalvo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-create-prd
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-create-prd-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill serves as a compatibility layer for legacy PRD creation workflows, ensuring that existing project configurations and override files remain functional while transitioning to the unified bmad-prd system.

Core Features & Use Cases

Compatibility Shim: Automatically forwards legacy create-intent requests to the modern bmad-prd engine.
Configuration Resolution: Dynamically resolves user-specific customizations and persistent facts from the project root.
Use Case: Use this if you have existing legacy configuration files in the _bmad/custom directory and need to maintain consistent PRD generation behavior during your migration to the latest version of the BMad framework.

Quick Start

Invoke the bmad-create-prd skill to generate a new product requirements document using your existing project-level configuration and workflow 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 migrate legacy PRD generation workflows to the unified BMad framework?▼

A compatibility shim facilitates migrating legacy PRD generation workflows to the unified BMad framework by delegating execution to the primary bmad-prd engine while managing persistent facts and configuration files.

Do I need existing configuration files to maintain consistent PRD generation behavior during migration?▼

You need existing legacy configuration files in the _bmad/custom directory to maintain consistent PRD generation behavior. The system dynamically resolves these user-specific customizations and persistent facts from the project root.

How does the compatibility layer resolve project-specific customization files for PRD creation?▼

The compatibility layer resolves project-specific customization files by dynamically fetching user-specific customizations and persistent facts directly from the project root before delegating execution to the primary bmad-prd engine.

Can I use my existing automation scripts with the latest version of the BMad framework?▼

You can use existing automation scripts with the latest BMad framework because the compatibility shim ensures backward compatibility for existing automation scripts and user-defined override configurations during the transition.

When should I use a compatibility shim for PRD generation instead of the primary engine directly?▼

Use a compatibility shim for PRD generation when you have legacy configuration files in the _bmad/custom directory and need to maintain consistent behavior while transitioning to the latest BMad framework version.