doccraft-adrlisted

# doccraft — architecture decision records (ADRs) ## When to use - A chat or design exploration reached a **conclusion** worth keeping (yes, no, defer, or "use X instead of Y"). - You need to **supersede** an older ADR without rewriting history. - A **rejected** option should stay visible so the team does not revisit the same dead end. Not every brainstorm needs an ADR — only decisions you want **git history and agents** to reuse. ## YAML frontmatter Use valid YAML between `---` delimiters at the top of the file, or an inline `**Status:**` line immediately after the title. If the project sets `adr.require_frontmatter: true` in `doccraft.yaml`, frontmatter is mandatory — otherwise either form is acceptable, but frontmatter is preferred for machine-readability. | Field | Required | Values / notes | |-------|----------|----------------| | `adr` | yes | Three-digit zero-padded string matching the filename number (e.g. `"007"`). MUST be unique — verify before writing. | | `status` | yes | One of the values in `adr.status` config (default: `Proposed` \| `Accepted` \| `Superseded by NNN-slug` \| `Deprecated`). If the user does not specify, default to `Proposed`. | | `updated` | yes | ISO date `YYYY-MM-DD`. MUST be set on creation and updated on every meaningful edit. | | `supersedes` | optional | YAML list of ADR filenames this record supersedes (e.g. `[005-old-approach.md]`). Omit or `[]` if none. | | `superseded_by` | optional | Filename of the ADR that replaced this one. Se