bmad-edit-prd

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/JaronTam/SDONE --skill bmad-edit-prd-jarontam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/JaronTam/SDONE/tree/main/.agents/skills/bmad-edit-prd
Command: npx skills add https://github.com/JaronTam/SDONE --skill bmad-edit-prd-jarontam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill is designed to streamline the process of updating and maintaining Product Requirement Documents (PRDs) by consolidating a deprecated intent, thereby simplifying the update workflow.

Core Features & Use Cases

  • Consolidation of Deprecated Intent: This skill has been deprecated and consolidated into bmad-prd, simplifying the update process by removing the need for the separate bmad-edit-prd intent.
  • Legacy Customization: Retained for compatibility, allows existing users to maintain their customization files.
  • Deprecation Notice: Notifies users of the impending removal and directs them to use bmad-prd for future updates.
  • Intent Forwarding: Automatically forwards the update intent to bmad-prd without further manual steps.

Quick Start

Invoke the bmad-edit-prd skill to update your PRD files. The system will automatically forward your request to the new bmad-prd skill with the appropriate context.

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 an existing Product Requirement Document using bmad-edit-prd?

To update a Product Requirement Document, invoke bmad-edit-prd and it will automatically forward your request to the new bmad-prd skill with the appropriate context. This streamlines the process by handling the update intent without further manual steps.

What does the deprecation and consolidation of the PRD update intent mean for my workflow?

The deprecation and consolidation of the PRD update intent means the separate bmad-edit-prd intent is removed to simplify your workflow. Future updates are directed to bmad-prd, while legacy customization is maintained for backwards compatibility.

Do I need to manually forward my PRD update requests to the new bmad-prd skill?

No, you do not need to manually forward PRD update requests to bmad-prd. The system automatically forwards the update intent to bmad-prd for intent handling when you invoke the legacy bmad-edit-prd skill.

Can I still use my legacy customization files for backwards compatibility?

Yes, you can still use legacy customization files for backwards compatibility. The bmad-edit-prd skill is retained to allow existing users to maintain their customization files during the transition to bmad-prd.

Why should I use the bmad-prd skill instead of bmad-edit-prd for future updates?

You should use bmad-prd for future updates because bmad-edit-prd is deprecated and scheduled for impending removal. Using bmad-prd provides a streamlined update process by consolidating the intent handling into a single skill.