What is an Architecture Decision Record (ADR)?

An ADR is a short document that captures a significant technical decision, the context in which it was made, and the resulting consequences for the project.

Should I delete old ADRs when a decision changes?

No, ADRs are a permanent record. Instead of deleting them, you should mark the old record as 'Superseded' and link it to the new ADR that replaces it.

When should I use the ADR skill?

Use this skill whenever you make a decision that is hard to change later, affects system structure, or impacts non-functional requirements like security or performance.

How do ADRs help engineering teams?

They provide a 'paper trail' for technical choices, helping new developers understand the project's evolution and preventing the team from revisiting the same arguments without new context.

Architecture Decision Records

Name: Architecture Decision Records
Author: ai-enhanced-engineer

byai-enhanced-engineer

0•

Aprendizaje y Documentación

Standardizes the documentation of significant technical decisions to maintain architectural clarity and historical context within a codebase.

The Architecture Decision Records (ADR) skill enables Claude to implement a structured framework for capturing the 'why' behind technical choices. It guides the creation of lightweight documentation that tracks the context, rationale, and long-term consequences of significant architectural shifts, such as technology selection or system structure changes. By enforcing a standardized format and status lifecycle—from proposed to superseded—this skill ensures that critical engineering knowledge is preserved, making it invaluable for team alignment, onboarding, and future-proofing software evolution.

Características Principales

01Traceability through internal referencing and research links

020 GitHub stars

03Sequential numbering and historical tracking of technical choices

04Decision lifecycle management (Proposed, Accepted, Deprecated, Superseded)

05Identification criteria for architecturally significant decisions

06Standardized templates including Context, Decision, and Consequences

Casos de Uso

01Documenting the selection of a specific database or framework over valid alternatives

02Capturing team consensus on complex technical trade-offs to prevent future regression

03Recording shifts in system architecture like moving from REST to GraphQL

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ai-enhanced-engineer/aiee-team arch-decision-records

For use in Claude.ai and ChatGPT

Download Skill