bmad-create-prd

Create product requirement documents via a backward-compatible deprecated interface.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/peshay/portfolixir --skill bmad-create-prd-peshay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/peshay/portfolixir/tree/main/.claude/skills/bmad-create-prd
Command: npx skills add https://github.com/peshay/portfolixir --skill bmad-create-prd-peshay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a way to create product requirement documents using a deprecated approach, ensuring backward compatibility with legacy setups.

Core Features & Use Cases

  • Legacy Compatibility: Allows users to use a deprecated skill to create product requirement documents.
  • Deprecation Notice: Issues a notice about the deprecation of the skill and recommends using the new bmad-prd skill.
  • Customization: Offers customization options through the resolve_customization.py script and config.yaml files.

Quick Start

Use the bmad-create-prd skill to generate a product requirement document for a new feature.

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 product requirement documents while maintaining backward compatibility with legacy setups?

You can create product requirement documents through a backward-compatible interface that forwards requests to the newer bmad-prd skill while supporting existing legacy workflows and configurations.

Can I customize product requirement document generation using config files?

Yes, product requirement document generation supports customization through resolve_customization.py scripts and config.yaml files, allowing user-defined configuration for legacy document creation workflows.

Why am I seeing a deprecation notice when creating product requirement documents?

The deprecation notice appears because this skill uses a deprecated approach to create product requirement documents, recommending migration to the newer bmad-prd skill for future document generation tasks.

Does the deprecation notice support multiple languages for product requirement document creation?

Yes, deprecation notices are emitted in the user's preferred language when creating product requirement documents, ensuring backward compatibility while communicating the migration recommendation clearly.

What's the best way to migrate from deprecated product requirement document creation to the newer skill?

The skill forwards to the newer bmad-prd skill automatically while maintaining backward compatibility, so you can transition gradually by updating your workflows to call the new skill directly when ready.

Are there limitations when using a deprecated skill for product requirement documents?

The deprecated skill maintains backward compatibility but issues deprecation notices, meaning it will continue functioning while recommending migration to avoid relying on deprecated product requirement document creation workflows.