skills.rest
angga30
angga30COMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decision-records

Capture and standardize architectural decisions using MADR, Lightweight ADR, and RFC templates.

Updated Feb 19, 2026
Search Tags:#architecture#documentation#adr#lifecycle#rfc#madr#decision-records
One-click install
npx skills add https://github.com/angga30/antigravity-skill-tech-lead --skill architecture-decision-records-angga30
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/angga30/antigravity-skill-tech-lead/tree/main/ADR
Command: npx skills add https://github.com/angga30/antigravity-skill-tech-lead --skill architecture-decision-records-angga30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are frequently made and discarded without a persistent, accessible record. This skill standardizes the process for capturing context, alternatives, rationale, and consequences to ensure traceability and governance over time.

Core Features & Use Cases

  • Supports multiple ADR formats (MADR, Lightweight ADR, Y-Statement, RFC) to fit team preferences.
  • Enforces a lifecycle (Proposed → Accepted → Deprecated → Superseded) and cross-references related ADRs.
  • Provides templates, guidance, and review practices to improve decision quality and onboarding.
  • Enables onboarding, audits, and knowledge transfer by preserving decision context and rationale.

Quick Start

Copy the standard ADR template, fill in Context, Decision, Consequences, and commit to the ADR directory.

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 to preserve context and rationale?▼

To document architectural decisions, you capture context, alternatives, and consequences using standardized templates like MADR or Lightweight ADR, then commit them to an ADR directory for persistent governance and traceability.

What is an Architecture Decision Record and when should I use one?▼

An Architecture Decision Record (ADR) is a standardized document capturing the rationale behind significant technology choices and system redesigns. You should use an ADR when making significant architectural choices that require governance and traceability over time.

Can I use MADR and RFC templates for architecture decision records?▼

Yes, you can use MADR, Lightweight ADR, Y-Statement, and RFC templates to fit your team's preferences for documenting architecture decisions. These formats help standardize the capture of context, decision, and consequences.

How do I manage the lifecycle status of an architecture decision record?▼

You manage the lifecycle of an architecture decision record by enforcing statuses from Proposed to Accepted, then to Deprecated or Superseded. This lifecycle management includes cross-referencing related ADRs to maintain history.

Does this approach support linking between architectural decisions?▼

Yes, this approach supports linking between architectural decisions by cross-referencing related ADRs. This ensures traceability when a previous decision is deprecated or superseded by a new architectural choice.

Related Skills

Explore More Software Engineering Skills→
oiagorodriguesoiagorodrigues

create-adr

Generate a MADR-style Architecture Decision Record template with decision, context, drivers, options, and consequences.

Community
Intermediate
heimanbaheimanba
2

documentation-and-adrs

Record architectural decisions with status, context, and consequences in ADR templates.

Community
Advanced
CodeAlexxCodeAlexx
1

coder:discuss-phase

Capture phase implementation decisions and generate a CONTEXT.md file.

Community
Intermediate
hgflimahgflima
1

documentation-and-adrs

Create and manage architectural decision records using markdown templates.

Community
Advanced