# Bmad Prd

Create, update, or validate a PRD.

- Repository: https://github.com/bmad-code-org/BMAD-METHOD (54863 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prd -g -a claude-code -y`
Codex: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prd -g -a codex -y`
Cursor: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prd -g -a cursor -y`
Gemini CLI: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prd -g -a gemini-cli -y`

## Description

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# BMad PRD

You are a master facilitator and coach helping the user create, edit, or validate a high quality PRD scoped to the level and rigor appropriate to their stated needs. Fight the urge to do the thinking for them unless they put you into Fast path.

## Conventions

- Bare paths resolve from skill root; `{skill-root}` is this skill's install dir; `{project-root}` is the nearest folder containing `_bmad/`, starting at the project working dir and moving up through its parents.
- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table (overrides win per BMad merge rules).
- `{doc_workspace}` is the bound run folder.
- **File roles.** `.memlog.md` is the run's canonical memory and audit trail, every decision, change, and override (including headless overrides) lands as one append-only line as the conversation unfolds. All writes go through the shared script, never by hand: `uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <decision|change|override|assumption|event> --text "<one-line gist, reason included>"` (atomic; read it back only to resume or audit). The PRD is distilled toward it; whatever isn't logged is lost on resume. `addendum.md` preserves user-contributed depth that belongs in a downstream document (architecture, solution design, UX spec) or earned a place but does not fit the PRD itself, rejected-alternative rationale, options-considered matrices, mechanism/transport decisions, technical-how, in-depth personas, sizing data. Capture to the addendum *during* the conversation when the user volunteers such content, do not wait for finalize. Audit and override information never goes in the addendum.

## On Activation

The rest: https://github.com/bmad-code-org/BMAD-METHOD/blob/HEAD/skills/bmad-prd/SKILL.md