> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tiny-brain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PRDs

> The top-level plan document: one initiative, its features, and its release bar

A PRD (Product Requirements Document) is the root of a plan. Created with:

```bash theme={null}
tiny-brain work add prd my-initiative "My Initiative"
```

which writes `docs/prd/my-initiative/prd.md` (plus an empty `features/`
directory) with the frontmatter filled in:

```yaml theme={null}
---
id: my-initiative
uuid: 019f56ad-afc3-7b99-8c39-098e60b8617f   # generated — never hand-write
title: My Initiative
status: not_started
version: 1.0.0
created: 2026-07-12T14:14:11.139Z
updated: 2026-07-12T14:14:11.139Z
author: Your Name
---
```

## Body sections

The CLI scaffolds a minimal body — `## Purpose and Goals` and `## Features` —
and the rest is prose you add. A strong PRD typically carries:

* **Purpose and Goals** — the problem and the outcomes that mark it done.
* **Key Decisions** — choices made up front, with the reasoning (so a future
  session doesn't re-litigate them).
* **User Stories** — who benefits and how, in as-a/I-want form.
* **Release Criteria** — the testable bar for calling the PRD shipped.
* **Testing Strategy** — how the work will be verified, including which
  parts have no test surface (and therefore run with RED skipped).
* **Features** — a linked list of the feature files.
* **Out of Scope** — deliberate exclusions, named so they read as decisions.

## Status lifecycle

`status:` moves `not_started` → `in_progress` (first feature underway) →
`completed` (every feature completed). The PRD's status is yours to update in
the frontmatter as features land; re-sync afterwards:

```bash theme={null}
tiny-brain task sync docs/prd/my-initiative/prd.md
```

Each feature lives in its own file under `features/` —
[their shape is next](/markdown-format/features).