skills.rest
sfines
sfinesCOMMUNITY
Explore all skills by this author →
GitHub

bmad-edit-prd

Forward legacy bmad-edit-prd PRD updates to the bmad-prd intent.

1|Updated May 31, 2026
Search Tags:#workflow automation#update management#deprecation notice#product requirement document#forwarding intent
One-click install
npx skills add https://github.com/sfines/slf-llm-wiki-py --skill bmad-edit-prd-sfines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/sfines/slf-llm-wiki-py/tree/main/.agents/skills/bmad-edit-prd
Command: npx skills add https://github.com/sfines/slf-llm-wiki-py --skill bmad-edit-prd-sfines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the update process for Product Requirement Documents (PRDs), providing compatibility for legacy systems while forwarding to the updated bmad-prd intent.

Core Features & Use Cases

  • Legacy Compatibility: Handles legacy bmad-edit-prd invocations, allowing for continued use in existing workflows.
  • Deprecation Notice: Issues a deprecation notice to users informing them of the removal of bmad-edit-prd in favor of bmad-prd.
  • Update Intent Forwarding: Directs updates to the bmad-prd intent for new customization and functionality.

Quick Start

Invoke the skill to update a PRD, legacy systems will continue to function as before while new updates are directed to bmad-prd.

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 Product Requirement Document with legacy compatibility?▼

To update a Product Requirement Document, this skill processes legacy invocations, issues a deprecation notice, and forwards the update intent to the bmad-prd intent for new functionality.

What is deprecation notice forwarding for product requirement documents?▼

Deprecation notice forwarding is the mechanism of informing users that the legacy bmad-edit-prd invocation is removed, while automatically routing update requests to the bmad-prd intent.

Do I need configuration files from the original setup to update a PRD?▼

Yes, updating a PRD requires configuration files and context from the original bmad-edit-prd setup to ensure legacy compatibility and proper forwarding to the bmad-prd intent.

Why does my workflow automation still function with the legacy bmad-edit-prd invocation?▼

Your workflow automation continues to function because the skill maintains backward compatibility for legacy bmad-edit-prd invocations while directing new updates to the bmad-prd intent.

When should I transition from the legacy edit-prd workflow to the new bmad-prd intent?▼

You should transition immediately since the skill issues a deprecation notice indicating the removal of bmad-edit-prd, forwarding all new customization and update functionality to the bmad-prd intent.

Related Skills

Explore More Product & Management Skills→
peshaypeshay
1

bmad-edit-prd

Update PRDs with legacy configuration compatibility and deprecation notices.

Community
Intermediate
diegosanchespereira1diegosanchespereira1

bmad-edit-prd

Update PRD documents while forwarding legacy invocations to bmad-prd.

Community
Intermediate
mol4mol4
1

bmad-create-prd

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

Community
Intermediate
JaronTamJaronTam

bmad-edit-prd

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

Community
Basic