What sections are included in a standard ADR?

A standard record includes Status, Date, Context, the Decision itself, Consequences (positive and negative), Alternatives Considered, and References.

Why should I use this skill with Claude Code?

Using this skill helps Claude understand the specific architectural constraints and patterns of your project, ensuring that any AI-generated code remains compliant with your previous decisions.

Where are the documentation files stored?

The skill recommends storing ADRs in organized directories like 'ai-docs/decisions/' or 'docs/adr/' within your repository for easy discovery by both humans and AI.

An Architecture Decision Record (ADR) is a short text file that captures an important architectural decision made along with its context, rationale, and consequences.

How does it handle outdated decisions?

Instead of deleting records, the skill uses a lifecycle process where outdated decisions are marked as 'Superseded' or 'Deprecated,' referencing the new ADR that replaces them.

ADR Documentation Manager

Name: ADR Documentation Manager
Author: MadAppGang

byMadAppGang

•

Learning & Documentation

Standardize and record architectural decisions with detailed context, trade-offs, and consequences to maintain long-term project clarity.

The ADR Documentation skill enables development teams to implement the Architecture Decision Record (ADR) practice seamlessly within their workflow. It provides a structured framework for capturing significant technical choices, preserving the 'why' behind architectural shifts to ensure institutional knowledge isn't lost over time. By documenting the environment, constraints, and rejected alternatives for each major decision, this skill helps teams avoid revisiting settled debates, streamlines onboarding for new members, and ensures that Claude Code follows established project patterns during code generation.

Key Features

01Contextual tracking of technical trade-offs and rejected alternatives

02Standardized markdown templates for consistent decision logging

03Full lifecycle management including Propose, Accept, Deprecate, and Supersede statuses

04Seamless integration with Claude Code to align AI behavior with project architecture

05Automated sequential numbering and file naming conventions

063 GitHub stars

Use Cases

01Establishing shared architectural patterns like Event-Driven or Microservices styles

02Recording the selection of primary databases, frameworks, or cloud infrastructure

03Documenting the rationale for breaking changes and major API redesigns

Key Features

01Contextual tracking of technical trade-offs and rejected alternatives

02Standardized markdown templates for consistent decision logging

03Full lifecycle management including Propose, Accept, Deprecate, and Supersede statuses

04Seamless integration with Claude Code to align AI behavior with project architecture

05Automated sequential numbering and file naming conventions

063 GitHub stars

Use Cases

01Establishing shared architectural patterns like Event-Driven or Microservices styles

02Recording the selection of primary databases, frameworks, or cloud infrastructure

03Documenting the rationale for breaking changes and major API redesigns