bmad-edit-prd

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preserves legacy PRD editing workflows while forwarding users to the newer bmad-prd workflow, so product documentation updates stay consistent without breaking existing invocations.

Core Features & Use Cases

  • Backward-Compatible PRD Updates: Keeps older bmad-edit-prd entry points working for teams that have not migrated yet.
  • Customization-Aware Workflow: Resolves project-specific configuration so PRD edits follow the right local rules and templates.
  • Clear Migration Path: Emits a deprecation notice and guides users toward bmad-prd for future work.
  • Use Case: A product team asks to update an existing PRD, and the skill routes the request through the newer workflow while preserving legacy overrides and behavior.

Quick Start

Ask this skill to update the target PRD so it applies the current project customization and forwards the work through the modern bmad-prd workflow.

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 product requirements documents without breaking legacy workflows?

To update product requirements documents without breaking legacy workflows, use a backward-compatible skill that parses YAML frontmatter, loads project context, resolves overrides, and forwards update intent to the newer bmad-prd workflow.

What is a backwards-compatible PRD update workflow?

A backwards-compatible PRD update workflow preserves legacy bmad-edit-prd entry points while emitting a deprecation notice and routing requests through the modern bmad-prd workflow to maintain consistent product documentation.

How do I apply project-specific customization rules when editing a PRD?

To apply project-specific customization rules when editing a PRD, the skill resolves local configuration overrides during the update process so PRD edits follow the correct local templates and rules.

Do I need YAML frontmatter parsing to revise product requirements?

Yes, YAML frontmatter parsing is required to revise product requirements using this skill, as it enables loading project context and resolving configuration overrides before forwarding the update intent.

When should I migrate from a legacy PRD editing workflow to bmad-prd?

You should migrate from a legacy PRD editing workflow to bmad-prd when ready for future product planning work, as the current skill emits a deprecation notice while preserving older entry points for teams that have not migrated yet.