Architecture Decision Records (ADR)
Standardizes the documentation of architectural decisions, capturing context, consequences, and technical trade-offs.
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.
Key Features
01Standardized ADR template generation with context and consequence sections
021 GitHub stars
03Trigger-based prompts for capturing decisions during technical discussions
04Decision lifecycle management (proposed, accepted, deprecated, superseded)
05Guidance for evaluating technical trade-offs and constraints
06Automated sequential numbering and naming conventions
Use Cases
01Recording team conventions that impact long-term system maintainability
02Defining architectural boundaries and communication patterns between microservices
03Documenting the selection of a specific database, framework, or cloud provider