bmad-edit-prd

Edit and improve existing PRDs through a structured multi-step workflow.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-edit-prd-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-edit-prd
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-edit-prd-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing Product Requirements Documents often suffer from vague requirements, missing sections, implementation leakage, or non-standard structure, making them unreliable inputs for downstream UX, architecture, and development work. ## Core Features & Use Cases - Guided PRD Editing: Walks through discovery, deep review, and section-by-section editing of an existing PRD with user approval at each stage. - Format Detection & Conversion: Detects whether a PRD follows the BMAD standard structure and offers legacy-to-BMAD conversion with gap analysis and effort estimates. - Validation Report Integration: Auto-detects prior validation reports in the PRD folder and uses their findings to prioritize edits. - Use Case: A product manager has a legacy PRD with unmeasurable requirements. The skill analyzes it against BMAD standards, proposes a prioritized change plan, applies approved edits, and optionally hands off to the validation workflow. ## Quick Start Ask the assistant to edit your PRD by saying "edit this PRD" and providing the path to your PRD file.

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 PRD with this workflow?▼

Provide the path to your PRD file when prompted. The workflow discovers your edit goals, reviews the document section by section, presents a prioritized change plan for approval, then applies the approved edits.

What is the BMAD PRD format and how is it detected?▼

The BMAD format requires six core sections: Executive Summary, Success Criteria, Product Scope, User Journeys, Functional Requirements, and Non-Functional Requirements. The workflow counts present sections to classify the PRD as BMAD Standard, Variant, or Legacy.

Can I convert a legacy PRD to BMAD format?▼

Yes. When a legacy PRD is detected, the workflow runs a conversion assessment with per-section gap analysis and effort estimates, then lets you choose full restructuring, targeted improvements, or both.

Does the edit workflow use validation reports?▼

Yes. It auto-detects validation report files in the PRD folder and can also load a manually provided report, using the findings to prioritize edits by severity before making changes.

What makes a good functional requirement in a BMAD PRD?▼

Functional requirements must be SMART: specific, measurable, attainable, relevant, and traceable. They describe capabilities rather than implementation details and avoid subjective adjectives like "fast" or "user-friendly" in favor of testable metrics.