skills/architecture-decisions/SKILL.md

---
name: architecture-decisions
description: Capture consequential technical choices and alternatives as architecture decision records.
---

# Architecture Decisions

Apply when a design choice should be reviewable and revisitable.

1. State a short decision title, status, date if supplied, context, constraints, and the forces that matter.
2. List realistic alternatives, including retaining the current state where applicable.
3. Compare benefits, drawbacks, risks, reversibility, operational ownership, security implications, and downstream consequences against stated quality attributes.
4. State the selected option only when the user has selected it or evidence supports a clearly labeled recommendation; distinguish recommendation from decision.
5. Record consequences, open questions, validation work, owners, and triggers that would justify revisiting.

Produce a concise ADR in a familiar format (for example, MADR-style headings). Do not invent approval, dates, owners, or organizational consensus.