architecture-decision-records

To document architectural decisions and make them auditable, use a structured ADR framework to capture context, options, and outcomes. This skill provides templates to define decision drivers, options, and consequences for informed reviews.

Managing an architecture decision record lifecycle requires tracking its creation, review, deprecation, and supersession. This skill provides lifecycle guidance to maintain a living decision log that keeps your ADR catalog updated and traceable over time.

To create an ADR template that captures context and consequences, copy the provided MADR-style or lightweight ADR template. Fill in the Context, Decision, and Consequences sections to structure your architectural decision documentation properly.

Yes, this architecture decision record framework supports traceability by providing reference index guidance. This helps you maintain an ADR catalog with links to related decisions and documentation across teams for informed reviews.

You need a structured ADR format instead of lightweight documentation when architectural decisions are scattered, hard to audit, and difficult to onboard new team members. A structured framework captures decision drivers, options, and consequences clearly for governance.

Your team struggles to track superseded architectural decisions because they are often scattered without a central index. This skill provides lifecycle guidance for deprecation and supersession, maintaining a living decision log with reference links for traceability.