ADR Authoring Skill

Purpose

Create Architectural Decision Records that preserve durable technical reasoning for humans and implementation agents.

An ADR records a decision that future work must remember. It captures the problem pressure, evaluated options, chosen direction, accepted consequences, constraints that must not be violated, implementation freedom that remains open, and conditions that require revision.

The ADR should constrain future work enough to prevent architectural drift. It must not freeze implementation details that are likely to change during coding unless the decision is explicitly about those details.

Generated ADRs should contain only information needed by future reviewers and implementation agents.

Output Contract

Output one ADR per durable decision. When multiple durable decisions are present, output an ADR set with an index and separate ADRs.

An ADR MUST define exactly one primary decision. Split the ADR when separate decisions have different drivers, consequences, owners, risks, validation signals, or revision triggers.

An ADR MUST NOT contain implementation code.