adr

Create an Architecture Decision Record when making architecturally significant decisions that affect system structure, quality attributes, or dependencies—such as choosing between competing frameworks, establishing project-wide patterns, resolving technical uncertainty, or making changes expensive to reverse. ADRs document the rationale, alternatives, and consequences of these choices.

Use template-driven creation to generate properly formatted ADRs following project standards, with automatic numbering and file naming. ADRs include standardized sections: Context, Decision, Consequences, and References, plus alternatives and trade-offs. The Skill automatically updates your table of contents when new records are added.

Document the context explaining why a decision was needed, the decision itself and chosen approach, consequences of that choice, and references to supporting materials. Include alternatives considered and their trade-offs so future readers understand why this path was selected over competing technical approaches.

Yes. The Skill automates ADR creation with template automation and automatic numbering, ensuring consistent documentation across your project without manual formatting overhead. This standardization helps your team maintain uniform decision records and reduces documentation burden.

Document decisions involving framework selection, API design choices, technology stack changes, deployment patterns, and other choices affecting multiple system components or that are difficult to reverse. ADRs work best for decisions where trade-offs between alternatives significantly impact system quality or maintenance.