Architecture Decision Records
Captures, maintains, and manages the context and rationale behind significant technical decisions using standardized ADR formats.
This skill provides comprehensive patterns for creating and managing Architecture Decision Records (ADRs) to document the history and reasoning behind technical choices. It helps engineering teams capture the context, considered options, trade-offs, and resulting consequences of architectural decisions, ensuring that the 'why' is preserved alongside the code. By offering multiple templates—including MADR, Y-Statements, and lightweight formats—it facilitates better team onboarding, simplifies historical reviews, and establishes a clear, searchable decision-making process within a repository.
Características Principales
0123,139 GitHub stars
02Review checklists to ensure consistency, security, and stakeholder alignment
03Lifecycle management for tracking proposed, accepted, deprecated, and superseded decisions
04Detailed trade-off analysis guidance for documenting pros, cons, and risks
05Automation workflows for indexing and linking related architectural decisions
06Standardized ADR templates including MADR, Lightweight, and Y-Statement formats
Casos de Uso
01Managing the deprecation and supersession of legacy architectural choices
02Capturing complex design trade-offs and rationale for future team onboarding
03Documenting the selection of new frameworks, databases, or infrastructure components