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 consequences it has for the project's future.

What templates are included in this skill?

The skill includes the MADR format, lightweight status-based templates, Y-Statements for concise records, and RFC-style templates for collaborative proposals.

Can it help manage the lifecycle of a decision?

Yes, it provides a clear workflow for moving decisions from 'Proposed' to 'Accepted', and eventually to 'Deprecated' or 'Superseded' as the project evolves.

When should I use the Architecture Decision Records skill?

Use this skill whenever you are making a non-trivial technical choice, such as adopting a new library, changing your database schema, or defining cross-cutting security patterns.

How does this help with team onboarding?

It provides new team members with a searchable history of 'why' things were built a certain way, reducing the time spent explaining past architectural choices.

Architecture Decision Records

Name: Architecture Decision Records
Author: GaitanS

byGaitanS

Aprendizaje y Documentación

Document and manage significant technical decisions using standardized Architecture Decision Record (ADR) patterns and templates.

Acerca de

This skill empowers developers to capture the context, rationale, and consequences of architectural choices systematically within their codebase. It provides comprehensive templates—ranging from lightweight records for fast-moving teams to detailed RFC-style proposals for complex systems—ensuring that design trade-offs and historical context are preserved for team alignment. By establishing a transparent and searchable history of technical evolution, it helps teams avoid 're-deciding' past issues and streamlines the onboarding process for new engineers.

Características Principales

Support for decision linking and superseding historical records
0 GitHub stars
Full decision lifecycle management (Proposed, Accepted, Deprecated, Superseded)
Multiple standardized ADR templates (MADR, Lightweight, Y-Statement, RFC)
Structured capture of context, decision drivers, and consequences
Directory organization and indexing guidelines for documentation parity

Casos de Uso

Establishing a 'Source of Truth' for technical debt and deprecation plans
Recording the rationale behind API design patterns and security architecture
Documenting the selection of new frameworks, databases, or infrastructure

Acerca de

Características Principales

Support for decision linking and superseding historical records
0 GitHub stars
Full decision lifecycle management (Proposed, Accepted, Deprecated, Superseded)
Multiple standardized ADR templates (MADR, Lightweight, Y-Statement, RFC)
Structured capture of context, decision drivers, and consequences
Directory organization and indexing guidelines for documentation parity

Casos de Uso

Establishing a 'Source of Truth' for technical debt and deprecation plans
Recording the rationale behind API design patterns and security architecture
Documenting the selection of new frameworks, databases, or infrastructure