architecture-decisions

You document architecture decisions using a standardized Architecture Decision Record (ADR) format to capture context, decision, consequences, alternatives, and references for technology choices and design patterns.

An Architecture Decision Record (ADR) is a standardized document capturing the context, rationale, and consequences of a significant technology choice. You need one when making structural design decisions to ensure historical context and consistency.

You track architectural evolution and technical debt by systematically generating ADRs that document the rationale, alternatives, and consequences of your design patterns and technology choices throughout the project lifecycle.

Yes, you can use the ADR template for database selection, API design, and authentication decisions. The Skill includes practical examples for these specific use cases to guide your documentation process.

The best way to capture context and alternatives for a design pattern is using the comprehensive ADR template, which systematically records the decision context, rationale, alternatives considered, and potential risks.

An ADR document should include the decision context, the chosen technology or design pattern, alternatives considered, consequences, and references. This structure enables systematic tracking of architectural rationale and evolution.