PRDs — Product Requirements Documents¶
PRDs argue for user-value. Each PRD names a surface or experience and makes the case for why it earns being built — what's broken, what changes for the photographer, why now, what would make the assumption wrong.
PRDs are not implementation specs, not feature lists, not user stories. They're arguments.
Reference¶
PA.md— audiences, promises, principles. Every PRD anchors here.PRD_TEMPLATE.md— the format every PRD follows.
Index¶
| PRD | Title | Status |
|---|---|---|
| PRD-001 | Mode A — the editing session | Draft v0.1 |
| PRD-002 | Mode B — autonomous fine-tuning | Draft v0.1 |
| PRD-003 | Vocabulary as voice | Draft v0.1 |
| PRD-004 | Local adjustments through AI masking | Draft v0.1 |
| PRD-005 | A command-line interface for Chemigram | Draft v0.1 |
Conventions¶
- Numbered sequentially (
PRD-NNN-slug.md) - Slug uses lowercase-hyphenated words
- Every PRD has a "Why this is a PRD" sentence in the header
- Every PRD anchors to PA via
PA/audiences/...,PA/promises/...,PA/principles/... - Drafts don't promise dates or sequencing — those are planning concerns, not PRD content