artifact-prd

Artifact: PRD (Product Requirements Document)

A Product Requirements Document that captures intent and scope as a durable spec before any issues or stories are cut from it — the upstream design investment against “ball of mud” drift. Two frameworks produce one:

• BMAD — bmad-prd: prd.md (+ addendum.md), authored by the PM persona (bmad-pm) on a Fast or Coaching path, with a .memlog.md decision/audit trail; length “scales with stakes” (pattern-scale-adaptive-planning).
• Builder Methods — bm-prd-creator: a structured interview for non-technical builders producing a visual single-file HTML PRD (or markdown, or both) plus milestone prompt files; strict what-not-how boundary.

Matt Pocock no longer produces a PRD (2026-07-09). MP’s former /to-prd was renamed to mp-to-spec and now produces a spec (artifact-spec-md) — “spec” is the single through-line term in v1.1 (the skill still says “you may know this as a PRD”); the two documents remain close counterparts.

Produced by (backlinks)

• bmad-prd — the PM’s create/update/validate PRD workflow.
• bm-prd-creator — non-technical-builder interview → visual HTML PRD + milestone prompts.

See Also

• artifact-spec-md — the leaner spec-document counterpart (Addy/SpecKit/BMAD/MP); MP’s mp-to-spec now produces this instead of a PRD.
• artifact-issue, artifact-story — the slices/stories decomposed from a PRD.
• artifact-product-brief — the pre-PRD scoping document (BMAD) that feeds it.
• pattern-spec-driven-development — the method this serves.