architecture-decision-records

Capture and govern architectural decisions using MADR-style templates and lifecycle states.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/okatech-org/gabon-diplomatie --skill architecture-decision-records-okatech-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/okatech-org/gabon-diplomatie/tree/main/.agent/skills/architecture-decision-records
Command: npx skills add https://github.com/okatech-org/gabon-diplomatie --skill architecture-decision-records-okatech-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) provide a lightweight, standardized way to document the context, options, decisions, and consequences of technical choices, ensuring traceability and onboarding clarity.

Core Features & Use Cases

  • Standard ADR templates (MADR-style) for consistent decision documentation across teams.
  • ADR lifecycle guidance (Proposed, Accepted, Superseded, and Deprecated states) to track evolution.
  • References, linkable decisions, and an auditable trail to improve onboarding and maintainability.
  • Integration guidance with tooling workflows (version control, review processes) to embed ADRs into your development lifecycle.

Quick Start

Create your first ADR using the MADR template and initialize the ADR directory with adr-tools.

Frequently Asked Questions about architecture-decision-records

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architectural decisions consistently across engineering teams?

Architecture decision records provide a standardized MADR-style template to capture context, options, decisions, and consequences, ensuring consistent documentation and traceability across software projects. This approach maintains an auditable trail for major technology choices and design trade-offs.

What is the MADR template and how does it work for ADRs?

The MADR template is a lightweight, structured format for architecture decision records that standardizes how teams document context, options, decisions, and consequences. It works by providing consistent fields for each record, improving onboarding clarity and maintainability across software projects.

How do I manage the architecture decision record lifecycle from proposed to deprecated?

Architecture decision record lifecycle management tracks the evolution of technical choices through Proposed, Accepted, Superseded, and Deprecated states. This governance process maintains an auditable trail with references linking, ensuring onboarding clarity and traceability for engineering teams.

Can I integrate architecture decision records into version control and CI workflows?

Architecture decision records integrate into version control and CI workflows to embed governance into your development lifecycle. Tooling guidance supports initializing an ADR directory with adr-tools, linking references, and incorporating decision reviews into standard development processes.

When do I need architecture decision records for my software project?

Architecture decision records are needed when engineering teams make major technology choices, design trade-offs, or governance decisions that require traceability. They provide a standardized way to document context and consequences, ensuring onboarding clarity and maintainability across software projects.

What is the best way to track design trade-offs and technology choices in software engineering?

Architecture decision records are the best way to track design trade-offs and technology choices because they provide a lightweight, standardized format for documenting context, options, decisions, and consequences. Linkable references and lifecycle states create an auditable trail for engineering teams.