adrlisted

# adr ## Purpose Create, list, update, and supersede Architecture Decision Records (ADRs) following the Markdown Architectural Decision Records (MADR) format. Maintains an ADR directory (see Directory Convention below). Works standalone or as a companion to `/architecture-design`. --- ## Directory Convention Before creating anything, detect where this project keeps ADRs. Use Glob to check, in order: `docs/decisions/ADR-*.md`, `docs/adr/*.md`, `adr/*.md`, `docs/architecture/decisions/*.md`. Use the first directory that already contains ADRs. Only if none exists, default to `docs/decisions/`. All paths below refer to this detected directory. --- ## ADR Format (MADR) Every ADR uses this structure: ```markdown # ADR-NNN: <Title> **Date:** YYYY-MM-DD **Status:** Proposed | Accepted | Deprecated | Superseded by ADR-NNN **Deciders:** <names or roles> **Tags:** <architecture | security | database | api | infrastructure | ...> ## Context and Problem Statement [1-3 paragraphs: what situation led to this decision? What is the problem being solved? What forces are at play?] ## Decision Drivers - [driver 1: most important constraint or goal] - [driver 2] ## Considered Options 1. **[Option A — Recommended]** — one-sentence description 2. **[Option B]** — one-sentence description 3. **[Option C]** — one-sentence description ## Decision Outcome **Chosen option:** [Option A], because [one paragraph justification tied to decision drivers]. ### Positive Consequences - [what b