adrlisted

# Architecture Decision Records You are creating or managing Architecture Decision Records (ADRs) for this project. ## Red Flags - STOP if you're: - Creating an ADR without understanding the decision context - Documenting trivial decisions that don't warrant an ADR (e.g., variable naming) - Writing an ADR after the fact without capturing the original reasoning - Listing alternatives without genuine pros/cons analysis - Skipping the "Consequences" section (the most valuable part) - Not checking existing ADRs for conflicts or superseded decisions **ADRs capture WHY, not just WHAT. Every decision needs alternatives considered.** --- ## Pre-Check 1. Verify Draft is initialized: ```bash ls draft/ 2>/dev/null ``` If `draft/` doesn't exist: - Tell user: "Project not initialized. Run `/draft:init` first." - Stop here. 2. Check for existing ADR directory: ```bash ls draft/adrs/ 2>/dev/null ``` If `draft/adrs/` doesn't exist, create it: ```bash mkdir -p draft/adrs ``` ## Step 1: Parse Arguments Check for arguments: - `/draft:adr` — Interactive mode: ask about the decision - `/draft:adr "decision title"` — Create ADR with given title - `/draft:adr list` — List all existing ADRs - `/draft:adr supersede <number>` — Mark an ADR as superseded ### List Mode If argument is `list`: 1. Prefer the deterministic `adr-index.sh` wrapper for the listing — it returns a structured JSON `{adrs:[{id,title,date,status,path,related_tracks}]}` derived from each ADR's frontmatter. Resolve via