Architecture Decision Records (ADRs)
Standardizes the process of documenting and managing significant architectural decisions and technical rationale within your codebase.
This skill provides a comprehensive framework for capturing the 'why' behind technical choices through Architecture Decision Records (ADRs). It offers multiple industry-standard templates—including MADR and Y-statements—to help teams record context, constraints, and trade-offs during the design phase. By managing the entire decision lifecycle from proposal to supersession, this skill ensures that architectural knowledge is preserved, reducing tribal knowledge and streamlining the onboarding of new engineers by providing a clear audit trail of the project's evolution.
Key Features
01Comprehensive lifecycle management for tracking proposed, accepted, and superseded decisions
02RFC-style patterns for evaluating complex architectural changes and gathering feedback
03Guidelines for linking related decisions to maintain a consistent architectural narrative
04Standardized templates for MADR, Lightweight ADRs, and Y-Statement formats
05Automated directory structure and index management for improved documentation discoverability
0637,717 GitHub stars
Use Cases
01Providing historical context of technical trade-offs to new team members during onboarding
02Managing the formal deprecation and migration path when replacing legacy architecture
03Documenting the rationale behind critical technology choices like databases or frameworks