bmad-create-prd

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

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/tiween/tiween --skill bmad-create-prd-tiween
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/tiween/tiween/tree/main/.agents/skills/bmad-create-prd
Command: npx skills add https://github.com/tiween/tiween --skill bmad-create-prd-tiween

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps streamline the process of creating Product Requirements Documents (PRDs) by consolidating the workflow and providing a compatibility layer for legacy integrations.

Core Features & Use Cases

  • Consolidated Workflow: Consolidates the creation of PRDs into a single Skill, reducing complexity.
  • Compatibility Layer: Retains compatibility with legacy systems by forwarding to the bmad-prd Skill.
  • Legacy Support: Retains the ability to use legacy customization files and configurations.

Quick Start

Use the bmad-create-prd Skill to initiate the creation of a new PRD.

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 using a consolidated workflow?▼

This consolidated workflow streamlines PRD creation by reducing complexity and centralizing the process. It provides a compatibility layer that forwards legacy requests to the bmad-prd Skill with predefined context.

Does this PRD creation workflow support legacy customization files?▼

Yes, this PRD creation workflow supports legacy customization files and configurations. It retains compatibility by forwarding legacy requests to the core bmad-prd Skill with predefined context.

What is a compatibility layer for legacy PRD integrations?▼

A compatibility layer for legacy PRD integrations bridges existing customization files with the current workflow. It forwards legacy requests to the core PRD Skill using predefined context to maintain system continuity.

Can I use legacy configurations with the new PRD creation skill?▼

Yes, you can use legacy configurations with the new PRD creation skill. It explicitly retains the ability to use legacy customization files by routing legacy requests through a compatibility layer.

Why does my PRD creation workflow need to forward to another skill?▼

Forwarding PRD creation to another skill centralizes the core logic while maintaining a single entry point. This compatibility layer approach ensures legacy customization files remain supported without duplicating functionality.

What are the limitations of using a consolidated workflow for PRD creation?▼

The main limitation is its dependency on forwarding requests to the bmad-prd Skill, meaning core functionality relies on that integration. However, it successfully retains support for legacy customization files within this architecture.