When should I use the ADR skill in Claude Code?

Use this skill whenever you are choosing between technologies, defining system patterns, or making any high-impact technical decision that would be difficult to reverse later.

Does this skill help with naming and organization?

Yes, it enforces a sequential numbering convention (e.g., 001-use-postgresql.md) to ensure your architecture repository remains organized and easy to navigate.

What is an Architecture Decision Record (ADR)?

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

How does the ADR skill handle decision updates?

It manages a status lifecycle, allowing you to mark decisions as proposed, accepted, deprecated, or superseded by newer records to maintain an accurate history.

What is the benefit of using ADRs for a development team?

ADRs reduce technical debt and knowledge silos by ensuring that every team member understands the reasoning and trade-offs behind the current system architecture.

Architecture Decision Records (ADR)

Name: Architecture Decision Records (ADR)
Author: SmidigStorm

bySmidigStorm

•

Herramientas de Colaboración

Standardizes the documentation of architectural decisions, capturing context, consequences, and technical trade-offs.

Acerca de

The ADR skill enables teams to maintain a transparent and permanent record of significant technical choices. By providing a structured framework for documenting the 'why' behind technology stacks, system boundaries, and integration patterns, it ensures that the rationale for critical decisions isn't lost over time. This skill automatically triggers during technical discussions, helping developers move from debate to documented consensus by managing the full lifecycle of a decision from proposal to deprecation.

Características Principales

Standardized ADR template generation with context and consequence sections
1 GitHub stars
Trigger-based prompts for capturing decisions during technical discussions
Decision lifecycle management (proposed, accepted, deprecated, superseded)
Guidance for evaluating technical trade-offs and constraints
Automated sequential numbering and naming conventions

Casos de Uso

Recording team conventions that impact long-term system maintainability
Defining architectural boundaries and communication patterns between microservices
Documenting the selection of a specific database, framework, or cloud provider

Acerca de

Características Principales

Standardized ADR template generation with context and consequence sections
1 GitHub stars
Trigger-based prompts for capturing decisions during technical discussions
Decision lifecycle management (proposed, accepted, deprecated, superseded)
Guidance for evaluating technical trade-offs and constraints
Automated sequential numbering and naming conventions

Casos de Uso

Recording team conventions that impact long-term system maintainability
Defining architectural boundaries and communication patterns between microservices
Documenting the selection of a specific database, framework, or cloud provider