ADR (Architecture Decision Record)

To document architecture decisions in Markdown, use a standardized ADR template to record the context, alternatives considered, the final decision, and its consequences. This ensures a consistent and traceable history of significant architectural choices.

An Architecture Decision Record should include the context of the decision, the alternatives evaluated, the final choice made, and the resulting consequences. Documenting these elements ensures technical decisions are traceable and governance is maintained.

To maintain and version ADRs within a project directory, use a Skill that supports linking related records and managing standardized Markdown files. This facilitates tracking architectural choices over time.

You should create an Architecture Decision Record when making significant technical decisions, such as choosing a new database technology. It documents the evaluation of alternatives, the final choice, and the reasoning behind it.

Yes, you can link related technical decisions across different ADR files. The Skill supports versioning and linking of related Architecture Decision Records within specified project directories to maintain a cohesive governance history.

The best way to track architectural governance is by creating Architecture Decision Records in Markdown. This approach standardizes documentation of technical decisions, including context and consequences, ensuring a traceable project history.