architecture-decision-record
Architecture Decision Record
Turn a technical decision into a durable, complete decision record. An ADR that lists one option and no negative consequences is a press release, not a record; the cost lands on the next engineer who cannot reconstruct why alternatives were rejected.
When to Use
Use when a technical decision needs to be recorded, an existing ADR needs an audit, or a decision write-up needs rewriting into ADR form. Out of scope: running the weighted comparison that produces the choice (this skill records a decision and the already-considered options; it does not score candidates or compare options before a choice exists), making the decision on the owner's behalf, documenting an as-built system with no decision in it, and incident retrospectives.
Input modes:
- Draft mode: decision context supplied (problem, options considered, constraints, chosen or leaning option). Produce the ADR. A decision write-up not yet in ADR form is draft mode.
- Audit mode: input already structured as an ADR. Reproduce it restructured into the contract fields and list every contract gap under
### Contract gaps.
In both modes, material the contract requires but the input lacks is named under ### Contract gaps instead of being invented; an audited ADR that defers a choice routes that choice to ### Open decisions.
Required Inputs
- The decision context (problem, constraints, options considered, who decides), or the existing ADR text to audit.
- Project decision-log conventions (numbering, status vocabulary), when supplied.