1---2name: architecture-decision-records3description: create and maintain high-signal adrs for architecture, package, runtime, workflow, and operational decisions. use when a decision should stay reviewable after the current session or when multiple credible options need a durable rationale.4---56# Architecture Decision Records78## Trigger Signals910- the task changes architecture, package boundaries, runtime behavior, support guarantees, or operating model11- more than one credible option exists and the trade-off should stay reviewable later12- a decision will affect multiple teams, releases, or future migrations1314## Inspect First1516- the affected specs, tasks, plans, and runtime boundaries17- any existing ADRs, design docs, or release notes that already capture related decisions18- operational constraints such as support window, migration cost, reliability, security, or compliance1920## Workflow21221. frame the actual decision, not the implementation diary around it232. capture the strongest drivers, constraints, and alternatives that were seriously considered243. choose a concise ADR shape and write context, decision, status, and consequences in plain language254. note follow-up actions, migration implications, and what would invalidate the decision later265. update or supersede older ADRs explicitly when the decision changes an earlier one2728## Output Contract2930- ADR title, status, and date-ready decision summary31- short context section with the forces that matter32- options considered and why the chosen path won33- consequences, follow-up actions, and superseded links when relevant3435## Failure Modes3637- the real decision has not been framed clearly yet38- the work is still exploratory enough that no stable rationale exists39- the note drifts into a long implementation log instead of a decision record4041## Escalation4243- escalate when the decision changes public contracts, support commitments, or cross-team ownership44- escalate when alternatives have materially different operational or migration risk45- escalate when the ADR appears to conflict with an existing record and the supersession path is unclear4647## References4849- `skills/architecture-decision-records/references/adr-template.md`50- `skills/architecture-decision-records/references/decision-rubric.md`51- `skills/architecture-decision-records/references/madr-style-guide.md`52- `skills/architecture-decision-records/references/adr-anti-patterns.md`53- `skills/architecture-decision-records/references/examples.md`
ldilov