Document and maintain Architecture Decision Records (ADRs) to track technical choices and long-term design tradeoffs.
This skill empowers Claude to automatically identify and document significant architectural decisions within your project. It monitors for major dependency changes, API modifications, and new pattern adoptions, ensuring that the logic behind your technical choices is preserved in a standardized format. By maintaining an organized history of decisions, alternatives considered, and consequences, this skill helps development teams avoid regressions, understand historical context, and facilitate smoother onboarding for future maintainers.
Key Features
011 GitHub stars
02Status lifecycle management including Proposed, Accepted, and Superseded
03Comprehensive documentation of alternatives and consequences
04Integration with project-specific documentation directories
05Standardized ADR creation using predefined templates
06Automated sequential numbering and indexing
Use Cases
01Redesigning public API surfaces or changing module boundaries
02Introducing or replacing core system dependencies like databases or frameworks
03Adopting new architectural patterns or state management approaches
