Architecture Decision Records (ADR)

•
215k
•

Standardizes and automates the documentation of architectural choices directly within the code repository.

The Architecture Decision Records skill empowers developers to capture the 'why' behind critical design choices, transforming ephemeral discussions into a structured, searchable log. By automatically detecting decision-making moments or responding to explicit requests, it generates Nygard-style ADR documentation that tracks context, alternatives, and trade-offs, ensuring future maintainers understand the evolution of the codebase without searching through old PRs or chat threads.

Key Features

01Standardized Michael Nygard-style ADR template generation
02Structured capture of alternatives, pros, and cons
03Contextual retrieval of existing architectural history
04214,597 GitHub stars
05Automatic indexing and directory structure management
06Automated detection of architectural decision signals

Use Cases

01Recording high-stakes infrastructure and database schema decisions
02Onboarding new developers by providing a history of design choices
03Evaluating and documenting transitions between frameworks or libraries