Product requirements

What each reader-facing feature must do, for whom, and how we know it works.

What a reader-facing feature must do, for whom, and how we know it works.

Living snapshots. Edit in place so each file describes the system as it is right now. No revision tables, no "previously X, now Y" — delete what is no longer true (ADR-0002).

Conventions

  • File name: <feature-slug>.mdx.
  • User stories with acceptance criteria in Given / when / then form.
  • Rules and edge cases carry the content details: versions, ecosystems, public versus private, what happens to existing pages and their URLs.
  • Open questions are asked (ADR-0004), not left in the file.

Template: ../_templates/prd.mdx

Documents

On this page

2 min read