An Architecture Decision Record (ADR) is a short text file that captures an important architectural decision, including the context in which it was made, the decision itself, and the resulting consequences.

Can I track the status of decisions over time?

Absolutely. The skill follows a lifecycle management pattern where decisions move through states like Proposed, Accepted, Deprecated, and Superseded.

Does this skill support different ADR formats?

Yes, it includes templates for multiple formats including MADR (Markdown Architecture Decision Records), lightweight versions for small teams, and formal Y-Statements.

When should I use the ADR skill?

Use this skill whenever you face a significant technical choice that will be difficult to change later, such as choosing a database, adopting a new framework, or defining API design patterns.

How does this help with team onboarding?

ADRs act as a 'paper trail' for your architecture. New team members can read through past ADRs to understand why the system is built the way it is without needing extensive manual explanation.

Architecture Decision Records (ADRs)

Name: Architecture Decision Records (ADRs)
Author: ccf

byccf

0•

Learning & Documentation

Standardizes the creation and management of technical documentation to capture the context and rationale behind significant architectural choices.

This skill empowers developers to implement a formal decision-making process within their codebase by providing structured templates and best practices for Architecture Decision Records (ADRs). It facilitates long-term project maintainability by documenting the rationale behind technology choices, design trade-offs, and implementation patterns, ensuring that future team members understand the constraints and motivations that shaped the current architecture. By integrating these patterns directly into the development workflow, teams can maintain a living history of their system's evolution.

Key Features

010 GitHub stars

02Comprehensive guidance on ADR lifecycle management from Proposed to Superseded

03Best practices for documenting technology deprecation and migration paths

04Standardized templates for MADR, lightweight, and Y-Statement formats

05Standardized directory structures and automated indexing practices

06Support for Request for Comments (RFC) style documentation for early-stage proposals

Use Cases

01Documenting the selection of a primary database, framework, or cloud provider

02Onboarding new developers by providing a historical record of architectural choices

03Establishing a formal review process for significant system design changes

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ccf/claude-code-ccf-marketplace architecture-decision-records

For use in Claude.ai and ChatGPT

Download Skill