Back to Skills

architecture-decision-records

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

26,022stars2,863forksUpdated 1/20/2026

Security Assessment

Safe(100/100)
Security Score100/100

About architecture-decision-records

The architecture-decision-records skill provides a structured approach to documenting significant technical decisions through Architecture Decision Records (ADRs). It addresses the challenge of maintaining clarity and context in architectural choices by offering a framework that captures the rationale behind decisions and their potential impacts. This skill is essential for teams looking to enhance their decision-making processes and ensure that past architectural choices are documented for future reference and learning.

Key features of this skill include templates for creating ADRs, guidance on when to write an ADR versus when it may be unnecessary, and a comprehensive understanding of the ADR lifecycle. The templates, such as the Standard ADR (MADR Format), allow teams to standardize their documentation practices, ensuring consistency across different decisions. The guidance on decision-making processes aids in onboarding new team members and reviewing historical decisions, allowing teams to learn from past experiences and make informed choices moving forward.

This skill is particularly useful for software architects, developers, and technical leads who frequently engage in making architectural decisions. It serves users who are documenting technology choices, recording design trade-offs, or establishing decision processes, thereby facilitating better communication and understanding within teams and across projects. By promoting best practices in technical decision documentation, this skill contributes to a more informed and cohesive development environment.

FAQ

When should I write an ADR?

You should write an ADR when making significant architectural decisions, such as adopting a new framework or selecting a database technology.

What are the core components of an ADR?

An ADR typically includes the context for the decision, the decision made, and the consequences of that decision.

Is there a specific format I should follow for an ADR?

Yes, the Standard ADR (MADR Format) is recommended for maintaining consistency and clarity in your documentation.

Can I use this skill for minor version upgrades?

No, minor version upgrades and bug fixes are typically not documented with ADRs.

Who can benefit from using this skill?

Software architects, developers, and technical leads will benefit most, especially when documenting significant architectural decisions.

Install architecture-decision-records

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

wshobson/agents