architecture-decision-records

To document architecture decisions, you capture structured ADRs that record context, alternatives considered, and rationale. This ensures design choices are preserved in a centralized log for future developers.

An architecture decision record captures context and rationale for a design choice. You need to create an ADR when making technology choices, selecting architecture patterns, or deciding on deployment trade-offs.

To start capturing a new ADR, request to record one and follow the guided workflow to capture context, alternatives, and rationale. It saves to docs/adr with an incremented number after your confirmation.

Yes, you can apply a standard ADR workflow to track deployment trade-offs across projects. It provides a repeatable process for capturing new records and reading existing ones in a centralized log.

The best way to maintain a centralized log of architectural decisions is saving structured ADRs to a docs/adr directory. This provides a repeatable workflow for reading existing records and adding new ones.

You need a standard ADR template to record alternatives and rationale effectively. The workflow requires capturing context, decision, alternatives considered, and rationale to preserve design choices alongside your code.