An Architecture Decision Record (ADR) is a document that captures an important architectural decision made along with its context and consequences for future reference.

Does it require a specific template?

Yes, it follows a structured format including YAML frontmatter, context, decision, alternatives considered, and consequences to ensure consistency.

When should I use the ADR Writing skill?

You should use it whenever you make hard-to-reverse choices, such as adding major dependencies, changing public APIs, or altering data models with migration implications.

Where does this skill store the records?

The skill typically stores ADRs in the docs/adrs/ directory of your project, maintaining a README.md index for easy navigation.

How does it handle conflicting or old decisions?

The skill includes a status model that allows it to mark old ADRs as 'Superseded' or 'Deprecated' rather than deleting them, preserving the project's historical narrative.

ADR Writing

Name: ADR Writing
Author: echohello-dev

byechohello-dev

•

学习与文档

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.

主要功能

1 GitHub stars
Status lifecycle management including Proposed, Accepted, and Superseded
Comprehensive documentation of alternatives and consequences
Integration with project-specific documentation directories
Standardized ADR creation using predefined templates
Automated sequential numbering and indexing

使用场景

Redesigning public API surfaces or changing module boundaries
Introducing or replacing core system dependencies like databases or frameworks
Adopting new architectural patterns or state management approaches

关于

主要功能

1 GitHub stars
Status lifecycle management including Proposed, Accepted, and Superseded
Comprehensive documentation of alternatives and consequences
Integration with project-specific documentation directories
Standardized ADR creation using predefined templates
Automated sequential numbering and indexing

使用场景

Redesigning public API surfaces or changing module boundaries
Introducing or replacing core system dependencies like databases or frameworks
Adopting new architectural patterns or state management approaches