skills.rest
mol4
mol4COMMUNITY
Explore all skills by this author →
GitHub

bmad-edit-prd

Forward legacy BMAD edit requests into the consolidated bmad-prd workflow.

1|Updated Mar 31, 2026
Search Tags:#migration#prd#product requirements#backward compatibility#bmad#workflow routing
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-edit-prd-mol4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-edit-prd
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-edit-prd-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps older PRD editing workflows working after BMAD consolidation, so teams can revise product requirements without breaking existing invocation patterns.

Core Features & Use Cases

  • Backward Compatibility: Preserves legacy bmad-edit-prd behavior for existing setups and override files.
  • Update Intent Routing: Forwards requests into the bmad-prd workflow using update intent.
  • Migration Guidance: Surfaces a deprecation notice and points users toward the newer customization surface.
  • Use Case: A team with older PRD automation can continue editing documents while gradually migrating to the consolidated skill.

Quick Start

Ask the skill to update the target PRD using the legacy BMAD edit workflow and keep the original user request intact.

Frequently Asked Questions about bmad-edit-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep legacy PRD edits working after a BMAD workflow consolidation?▼

To keep legacy PRD edits working, this Skill forwards older bmad-edit-prd requests into the consolidated bmad-prd workflow. It preserves original user intent while switching to update mode, ensuring existing invocation patterns remain functional during migration.

What is the best way to migrate product requirement documents to the new bmad-prd workflow?▼

The best way to migrate product requirement documents is to use this Skill to route legacy edit requests into the bmad-prd workflow. It surfaces a deprecation notice and provides migration guidance toward the newer customization surface for gradual transitions.

How do I update an existing product requirements document using the legacy BMAD edit workflow?▼

To update an existing product requirements document, ask the Skill to update the target PRD using the legacy BMAD edit workflow. It requires resolving legacy workflow overrides and loading configuration for language and user identity while keeping the original request intact.

Can I use my existing BMAD customization files with the consolidated product requirements workflow?▼

Yes, you can use existing BMAD customization files with the consolidated workflow. This Skill applies to PRD creation, revision, validation, and migration scenarios that need backward compatibility with your current override files and setup configurations.

Why does my legacy bmad-edit-prd invocation trigger a deprecation notice?▼

Your legacy bmad-edit-prd invocation triggers a deprecation notice because the workflow has been consolidated. The Skill forwards your request into the bmad-prd workflow using update intent and points you toward the newer customization surface for future edits.

Related Skills

Explore More Product & Management Skills→
mol4mol4
1

bmad-create-prd

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

Community
Intermediate
tiweentiween

bmad-validate-prd

Validate product requirements documents and forward calls to bmad-prd.

Official
Intermediate
JaronTamJaronTam

bmad-edit-prd

Forward PRD update intents from bmad-edit-prd to bmad-prd.

Community
Basic
peshaypeshay
1

bmad-create-prd

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

Community
Intermediate