Files
msd-core/docs/prd
Tom Boucher f52a7a5f77 feat(#1245): add capability ecosystem ADR, PRD, and developer documentation (#1248)
Phase 0 of the Capability Ecosystem epic (#1244): the design record and the
third-party-author documentation set, with no runtime or code changes.

- docs/adr/1244-capability-ecosystem.md — architecture decision record
  (amends/extends ADR-857 Decisions 7 & 8)
- docs/prd/1244-capability-ecosystem.md — product requirements
- Diataxis docs: tutorial, how-to (publish/import/version/remove),
  reference (manifest schema, /gsd:capability command, capability matrix),
  explanation (trust model); cross-links added to develop-a-capability.md

Refs #1244

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 17:51:43 -04:00
..

Product Requirements Documents

This directory contains Product Requirements Documents (PRDs) for GSD.

A PRD captures the what and why of a feature before implementation begins. ADRs (in docs/adr/) capture the how of architectural decisions. The two complement each other: a PRD makes the case for a feature and defines acceptance criteria; an ADR records the architectural mechanism chosen to deliver it.

Naming Convention

PRDs use the same issue#-prefix slug naming as ADRs:

docs/prd/<issue#>-<kebab-slug>.md

Example: docs/prd/3491-bar-feature.md for a feature tracked in issue #3491.

The GitHub-assigned issue number is the prefix. Do not compute a sequential number locally — see CONTRIBUTING.md — "Proposing an ADR or PRD" for the full process.

Historical note

docs/adr/0011-review-default-reviewers-prd.md predates this directory and is preserved as immutable historical record. It is not a pattern to follow. New PRDs live here.

Index

PRD Title Status
3524-cjs-sdk-hard-seam.md CJS↔SDK hard seam — phased migration (#3524) Superseded by ADR-0174