architecture-decision-records

Organize Architecture Decision Records with templates, lifecycle tracking, and indexing.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill architecture-decision-records-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/architecture-decision-records
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill architecture-decision-records-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADR documentation reduces ambiguity by capturing context, the chosen decision, and its consequences for major technical choices.

Core Features & Use Cases

  • Templates for Standard ADR (MADR), Lightweight ADR, and Y-Statement to cover common scenarios
  • Lifecycle guidance from Proposed to Superseded with status tracking
  • Indexing and governance for cross-team traceability and auditing

Quick Start

Copy the MADR template to a new ADR file and fill in the Context, Decision, and Consequences.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record captures context, chosen decision, and consequences for major technical choices. You need ADRs for major architectural decisions, technology reviews, and cross-team governance to reduce ambiguity.

How do I write an Architecture Decision Record using standard templates?

To write an Architecture Decision Record, copy the MADR template to a new ADR file and fill in the Context, Decision, and Consections. Available templates include Standard MADR, Lightweight ADR, and Y-Statement formats.

Can I track the lifecycle status of an ADR from proposed to superseded?

Yes, ADR lifecycle management supports status tracking from Proposed to Superseded. This maintains consistent ADR creation and traceability throughout the architectural decision's lifespan.

Does ADR governance support cross-team traceability and indexing?

ADR governance supports cross-team traceability and auditing through indexing and references. This enables consistent ADR creation and allows teams to trace architectural decisions across the organization.

What is the difference between MADR, Lightweight ADR, and Y-Statement templates?

MADR provides a full Standard ADR structure, Lightweight ADR offers a minimal format, and Y-Statement covers alternative scenarios. All three templates capture context, decision, and consequences for different documentation needs.

When should I not use a full ADR template for architectural decisions?

You should avoid full Standard ADR (MADR) templates for minor technical choices. Instead, use the Lightweight ADR template to capture context, decision, and consequences without full governance overhead.