π PRDs
| Title | Author | Status | Date βΌ |
|---|---|---|---|
| PRD: Spotlight (βK command palette) for the Organization Dashboard | relbns | ready-for-rd | 2026-06-26 |
| User Notifications System | product-team | shipped | 2025-01-15 |
What lives here: Product Requirements Documents β the WHAT and WHY of a shipping feature. Owned by Product.
Use vs. siblings: a proposal is lighter and pre-PRD; an RFC is broader and multi-team; a Design Doc is R&D's translation of the PRD into HOW.
Template: PRD Β· filename:
docs/prds/<slug>-<cu-id>.mdHow handoff works: see Product β R&D Handoff for the full pipeline, statuses, and Path A / Path B design reference options.
This section contains all active PRDs. Every PRD has a paired ClickUp parent task (clickup_parent in frontmatter) and, once ready-for-rd, a paired Design Doc under docs/designs/.
Lifecycle at a glanceβ
| Status | What it means | Next step |
|---|---|---|
draft | PRD is being written | Author iterates until Definition of Ready is satisfied |
ready-for-rd | Gatekeeper approved; PRD passes DoR | R&D opens the Design Doc and runs /plan-feature |
in-progress | R&D building | Implementation across affected repos |
shipped | DoD checked, feature live | Pattern stays as reference |
deprecated | Removed or replaced | Linked to its successor |
Active PRDsβ
Browse the sidebar for current PRDs.
Use the PRD template and open a PR. The template's Definition of Ready section is the gate that prevents "we started and got blocked." Don't move past draft until every DoR item passes.
PRDs drafted with Claude include ai_assisted: true in frontmatter and must be reviewed by a human before reaching ready-for-rd.