adr-recordlisted

# Architecture Decision Record (ADR) Record an important architecture decision with its context, status, alternatives, and consequences. Artifacts are English unless the target repository explicitly requires another documentation language. ## Ownership and handoffs `adr-record` owns full standalone ADR documents and the canonical filename convention. It does not own a project-wide PRD/TASKS workflow or a multi-document specification pack. - Use `prd-taskbreaker` for PRD/PLAN/TASKS. Its ADR-lite block is enough for a small, local decision; hand a costly-to-reverse decision to this skill for a full ADR. - In a `development-spec-suite` pack, Technical Design owns the `ADR-*` index row and traceability link. This skill writes the referenced full ADR without creating a second decision register. - Use `volumx-writer` only to rewrite, translate, or humanize an existing ADR without changing its decision. ## Workflow 1. **Locate the scope.** If `~/Projects/<project>/` already exists, read its project instructions and existing decision records, and use its established ADR directory or `docs/adr/`. If it does not exist yet, use the `~/Documents/work/prd/<project>/` staging directory instead — see Storage. 2. **Allocate the next ID.** Scan `docs/adr/` and `adr/` (or the `~/Documents/work/prd/<project>/` staging directory before the repository exists) for existing canonical `ADR-[0-9]+-*.md` files and legacy `[0-9]+-*.md` files. Parse the numeric prefixes, take the highest ID, add o