// Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path.
| name | adr-writer |
| description | Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path. |
| version | 0.1.0 |
| status | experimental |
| risk | low |
| tags | ["design","writes-files"] |
runbooks/)| Name | Type | Required | Notes |
|---|---|---|---|
context | string | yes | The problem being solved, in 2–4 sentences |
options | list | yes | Alternatives considered |
decision | string | yes | Chosen path |
number | int | no | If omitted, finds next ADR number from memory/decisions/ |
A file at memory/decisions/ADR-NNNN-<slug>.md matching the ADR template.
number input)accepted (default), proposed, superseded by ADR-XXXXmemory/decisions/ADR-NNNN-<slug>.mdMEMORY.md#decisionsADR-\d{4}-[a-z0-9-]+\.mdUse when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas) before any analysis.
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.
