An Architecture Decision Record (ADR) is a document that captures a significant architectural decision, including the context in which it was made and the rationale for the chosen approach.

How does this skill improve AI-assisted development?

It provides Claude with a specific, rigorous framework to follow, ensuring that AI-generated architectural advice is documented according to industry best practices.

When should I create an ADR using this skill?

You should create an ADR when choosing between multiple valid approaches, adopting new patterns, or making decisions that are difficult to reverse.

Does this skill help with evaluating alternatives?

Yes, the ADR authoring process requires listing at least two alternatives with their respective pros and cons to ensure a balanced and fair evaluation.

ADR Authoring

Name: ADR Authoring
Author: rand

byrand

•

学習とドキュメンテーション

Standardizes the creation and management of Architecture Decision Records (ADRs) to document technical rationale and trade-offs.

概要

The adr-authoring skill streamlines the process of capturing critical technical decisions within your development workflow by providing a structured framework for drafting, reviewing, and organizing ADRs. It ensures that the rationale behind architectural choices is preserved alongside context, alternatives, and consequences, preventing knowledge rot and facilitating better team alignment. This skill is essential for teams practicing rigorous AI-assisted development who need to maintain a clear, searchable history of their project's evolution.

主な機能

Lifecycle management tracking for Proposed, Accepted, and Superseded states
2 GitHub stars
Impact analysis including positive, negative, and neutral consequences
Standardized ADR template generation with sequential numbering
Structured capture of context, alternatives, and decision rationale
Automated organization within a dedicated documentation directory

ユースケース

Recording the rationale behind significant refactors or architectural shifts
Documenting the selection of a new technology stack or framework
Managing a historical index of technical trade-offs for team onboarding

概要

主な機能

Lifecycle management tracking for Proposed, Accepted, and Superseded states
2 GitHub stars
Impact analysis including positive, negative, and neutral consequences
Standardized ADR template generation with sequential numbering
Structured capture of context, alternatives, and decision rationale
Automated organization within a dedicated documentation directory

ユースケース

Recording the rationale behind significant refactors or architectural shifts
Documenting the selection of a new technology stack or framework
Managing a historical index of technical trade-offs for team onboarding