decision-recordlisted

# decision-record > Shape the **thinking** behind an architectural decision: list the > options, expose trade-offs, lock the chosen variant, and wire the > supersession chain. Hands off to [`adr-create`](../adr-create/SKILL.md) > for file mechanics (numbering, index, frontmatter). This skill does > not write the ADR file itself. ## When to use - A team is about to commit to a non-trivial architectural choice and wants the trade-offs on paper first. - Two engineers disagree on an approach — surface the options and consequences before one wins by attrition. - A previous decision needs revisiting; the result must `supersede:` the older ADR with explicit rationale. - German triggers: "lass uns das festzurren", "Trade-off-Matrix", "welche Option ziehen wir?". Do NOT use when: - The file mechanics are the entire ask (numbering, regenerating the index) — route directly to [`adr-create`](../adr-create/SKILL.md). - The decision is reversible and small (e.g. variable rename) — ADRs are for choices that constrain future work. - The user wants a feature plan, not a decision — route to the planning command instead. ## Cognition cluster - **Mental model 4 — Second-order thinking.** Every decision unlocks some futures and locks out others; the consequences block names what becomes harder, not just what becomes easier. See [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 4. - **Mental model 6 — Theory of constraints.** A decision that