bmad-edit-prd

Edit and improve PRD documents with format detection and auditable change plans.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-edit-prd-amitmishra-byldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/2-plan-workflows/bmad-edit-prd
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-edit-prd-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the difficulty of updating and improving Product Requirement Documents (PRDs) in a consistent, auditable way by enforcing a disciplined, step-file workflow that guides discovery, review, conversion, and edits while preserving state and frontmatter history.

Core Features & Use Cases

  • Discovery & Format Detection: Prompt-driven discovery to locate the PRD, detect BMAD vs legacy formats, and optionally load validation reports to guide edits.
  • Legacy Conversion Assessment: Analyze legacy PRDs against BMAD standards, produce gap analysis and effort estimates, and let users choose conversion or targeted edits.
  • Deep Review & Controlled Edits: Run section-by-section deep reviews, build prioritized change plans, and apply approved edits with frontmatter updates and audit trail.
  • Use Case: A product manager wants to convert a legacy PRD to BMAD, fix vague success criteria, and produce a validated, downstream-ready document for UX and architecture teams.

Quick Start

Provide the path to the PRD.md you want to edit and describe the edit goals (for example: "improve success criteria and convert to BMAD format").

Frequently Asked Questions about bmad-edit-prd

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

FAQPage Schema
How do I edit an existing product requirements document to follow a structured workflow?

To edit a product requirements document, you provide the PRD path and edit goals. The system detects the format, loads validation reports, and enforces a sequential step-file architecture to guide section-by-section edits and produce an auditable change plan.

Can I convert legacy PRDs to the BMAD format automatically?

Legacy PRDs can be converted to the BMAD format. The tool analyzes your legacy document against BMAD standards, produces a gap analysis with effort estimates, and lets you choose between full conversion or targeted section edits.

What is the best way to review and improve vague success criteria in a PRD?

The best way to improve vague success criteria is running a deep review. The workflow performs section-by-section analysis, builds a prioritized change plan, and applies approved edits while updating frontmatter and maintaining an audit trail.

Does editing PRDs with this workflow require validation reports?

Validation reports are optional but recommended for guiding edits. The workflow can optionally load validation reports during the discovery phase to inform the deep review and ensure downstream-ready product planning documents.

How do PRD frontmatter updates work during controlled document edits?

PRD frontmatter updates occur automatically during controlled edits. As approved changes are applied section-by-section, the system preserves state and updates frontmatter history to maintain a complete audit trail of all modifications.

When should I not use a sequential step-file workflow for product planning?

A sequential step-file workflow may not suit rapid, ad-hoc edits. It enforces disciplined discovery, review, and conversion steps designed for comprehensive product planning, making it less ideal for quick, isolated text changes.