agile-v-adr

# Instructions An **Architecture Decision Record (ADR)** captures a significant, long-lived technical decision. It is a distinct artifact from the append-only `DECISION_LOG.md`: an ADR has a fixed field set, is immutable once written, and is changed only by supersession. Agile V reserves the `ADR-XXXX` ID; this skill backs it with an artifact and procedure. Requires **agile-v-core** loaded first. An ADR does not replace a REQ, risk control, specification, or change record. ## When to write an ADR | Use an **ADR** | Use `DECISION_LOG.md` | |---|---| | Architecturally significant, long-lived choice (platform, framework, tool, architecture pattern, infrastructure, data, security posture) | Routine, reversible, day-to-day implementation decisions | | A choice future maintainers must not silently reverse | Session/context notes and rationale | | A decision affecting regulated functionality, data integrity, interfaces, validation, or lifecycle risk | — | If in doubt, an ADR is the more durable, auditable choice. ## ADR fields (append-only, immutable once written) | Field | Value / allowed values | |---|---| | ID | `ADR-XXXX` — unique, never reused | | Type | Platform \| Framework \| Tool \| Architecture \| Infrastructure \| Data \| Security | | Date | Date of decision | | Status | proposed \| approved \| active \| deprecated \| superseded | | Supersedes | Reference to the ADR this one replaces (if any) | | Review Date | Scheduled re-evaluation date | | Context | Forces / pro...