a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
Product Requirements Documents
This directory contains Product Requirements Documents (PRDs) for MSD.
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 |