Architecture Decision Records (ADR) FAQs

Question 1

What templates are included in this skill?

Accepted Answer

The skill provides several formats including Y-Statements for simple selections, Lightweight ADRs for medium decisions, Standard MADR for significant changes, and RFC-style templates for major proposals.

Question 2

What is an ADR?

Accepted Answer

An Architecture Decision Record (ADR) is a short text file that captures an important architectural decision, including the context in which it was made and the consequences it has for the project's future.

Question 3

Can I edit an ADR once it has been accepted?

Accepted Answer

No, the 'Iron Law' of ADRs is that you never edit an accepted record. Instead, you create a new ADR that explicitly references and supersedes the old one to preserve the historical decision trail.

Question 4

How does the review process work for these records?

Accepted Answer

Typically, an ADR is submitted as a Pull Request and requires review from at least two senior engineers to ensure the decision is technically sound and the trade-offs are understood.

Question 5

When should I use the ADR skill in Claude Code?

Accepted Answer

You should use this skill whenever you face a significant or irreversible technical choice, such as framework selection, API design patterns, database technology choices, or security architecture.

Architecture Decision Records (ADR)

Architecture Decision Records (ADR)

主要功能

使用场景

主要功能

使用场景