recording-architecture-decisions

1# Recording Architecture Decisions
2 
3## Purpose
4 
5Record durable architecture decisions without losing the current-state baseline
6closure. An ADR records why a decision was made; a baseline records what the
7architecture is after that decision.
8 
9This skill is a lazy, task-specific workflow. It does not replace
10`verification-before-completion`, does not grant completion authority, and does
11not make authoritative `GateDecision` or `PolicySnapshot` outputs.
12 
13## Required Read Set
14 
15Before deciding or writing, read the smallest relevant excerpts from:
16 
17- `docs/adr/ADR-CREATION-GATE.md`
18- `docs/current/AEGIS_ADR_AUTO_BACKFILL.md`
19- the target project's current ADR, baseline, or authority docs that own the
20  affected architecture surface
21 
22For Aegis repository changes, use this repository's `docs/adr/` and
23`docs/current/` authority order. For target projects with their own ADR system,
24respect that project owner instead of duplicating the same decision into
25`docs/aegis/adr/`.
26 
27## When To Use
28 
29Use this skill when the user asks to:
30 
31- create, write, update, amend, supersede, or evaluate an ADR
32- decide whether an architecture decision record is needed
33- record a durable architecture decision or decision log entry
34- close baseline sync after an ADR-relevant architecture change
35- verify that an ADR action did not leave the architecture baseline stale
36 
37Do not use it for simple wording edits, ordinary README cleanup, tests-only
38…