ADR — Architecture Decision Records

What I do

• Guide creation of lightweight, version-controlled Architecture Decision Records
• Provide a structured template covering context, options, rationale, consequences
• Enforce naming conventions and review checklist for consistency
• Help teams document why decisions were made — not just what was decided

When to use me

Activate this skill when:

• Making architectural choices that affect multiple components or teams
• Choosing between technologies, frameworks, or libraries
• Changing core design patterns, data models, or system boundaries
• Making decisions with long-term impact or high reversal cost
• Documenting why an approach was explicitly rejected (negative decisions)

Key Rules