skills.rest
peshay
peshayCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-edit-prd

Update PRDs with legacy configuration compatibility and deprecation notices.

1|Updated Apr 27, 2026
Search Tags:#workflow#compatibility#deprecation#PRD#update
One-click install
npx skills add https://github.com/peshay/portfolixir --skill bmad-edit-prd-peshay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/peshay/portfolixir/tree/main/.claude/skills/bmad-edit-prd
Command: npx skills add https://github.com/peshay/portfolixir --skill bmad-edit-prd-peshay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of updating Product Requirements Documents (PRDs) while providing a deprecation notice for legacy support.

Core Features & Use Cases

  • Update Intent: Automatically invoke the bmad-prd update intent.
  • Legacy Support: Retains compatibility with legacy bmad-edit-prd configurations.
  • Deprecation Notice: Issues a notice to users about the upcoming removal of bmad-edit-prd.
  • Use Case: For teams transitioning from bmad-edit-prd to bmad-prd, this Skill ensures a smooth transition with notice and support for existing configurations.

Quick Start

Activate the bmad-edit-prd Skill to update a PRD while receiving a deprecation notice.

Frequently Asked Questions about bmad-edit-prd

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

FAQPage Schema
How do I update a PRD while keeping legacy configurations compatible?▼

You can update a PRD with legacy support by using a compatibility layer that retains existing configurations while automatically invoking the new bmad-prd update intent for a smooth transition.

What happens when the bmad-edit-prd workflow is deprecated?▼

The bmad-edit-prd workflow issues a deprecation notice about its upcoming removal, warning users to transition to the new bmad-prd update intent while still maintaining support for legacy configurations.

How do I transition from a legacy PRD update workflow to a new one?▼

To transition from a legacy PRD update workflow, activate the compatibility Skill to automatically invoke the new update intent while retaining support for your existing legacy configurations during the migration period.

Do I need to manually migrate my legacy PRD configurations to use the new update intent?▼

No, you do not need to manually migrate legacy PRD configurations because the compatibility layer automatically handles the transition by invoking the new bmad-prd update intent while preserving your existing setup.

Why am I seeing a deprecation notice when updating my PRD?▼

You are seeing a deprecation notice because the legacy PRD update workflow is scheduled for removal, and the system is alerting you to transition to the new bmad-prd update intent while compatibility support remains active.

Can I still use legacy PRD configurations without breaking my current workflow?▼

Yes, you can still use legacy PRD configurations without breaking your workflow because the compatibility layer ensures existing setups function correctly while routing updates through the new bmad-prd intent.

Related Skills

Explore More Software Engineering Skills→
marcmontecalvomarcmontecalvo

bmad-create-prd

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

Community
Basic
sfinessfines

bmad-create-prd

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

Community
Basic
mol4mol4
1

bmad-edit-prd

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

Community
Intermediate
mol4mol4
1

bmad-create-prd

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

Community
Intermediate