architecture-decision-records

Name: architecture-decision-records
Availability: InStock
Author: LLLLimbo

Documents and maintains Architecture Decision Records with templates and lifecycle guidance.

Updated Jan 5, 2026

Search Tags:#architecture #templates #documentation #adr #governance #decision-record

Ready to run

npx skills add https://github.com/LLLLimbo/Skills --skill architecture-decision-records-llllimbo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/LLLLimbo/Skills/tree/main/documentation-generation/architecture-decision-records
Command: npx skills add https://github.com/LLLLimbo/Skills --skill architecture-decision-records-llllimbo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) are often created inconsistently or become hard to maintain, leading to decisions diverging from implementation details and legacy choices.

Core Features & Use Cases

Standard ADR templates and guidance to capture Context, Decision, and Consequences in a consistent format.
Lifecycle guidance for creation, review, updates, deprecation, and supersession to keep the decision graph coherent.
Reference and linkage to related ADRs to build a navigable decision history across projects.

Quick Start

Create a new ADR using the standard template and populate the Context, Decision, and Consequences sections. Update the ADR index after acceptance.

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 (ADR) captures context, decisions, and consequences for major architectural choices. You need an ADR when establishing governance processes or documenting significant structural changes to maintain a coherent decision history across projects.

How do I create a standard Architecture Decision Record?▼

To create an Architecture Decision Record, use a standard template and populate the Context, Decision, and Consequences sections. After acceptance, update the ADR index to maintain a navigable decision graph across your project history.

How do I manage the lifecycle of an Architecture Decision Record?▼

Manage the Architecture Decision Record lifecycle using guidance for creation, review, updates, deprecation, and supersession. This lifecycle process keeps your decision graph coherent and prevents historical choices from diverging from implementation details.

Can I link related Architecture Decision Records together?▼

Yes, you can link related Architecture Decision Records through reference and linkage features. This builds a navigable decision history across projects, connecting related ADRs to maintain context and track supersession over time.

What's the best way to maintain legacy architecture decisions?▼

The best way to maintain legacy architecture decisions is applying ADR lifecycle guidance for updates and supersession. This prevents legacy choices from diverging from implementation details by keeping the decision graph coherent and documented.

Architecture Decision Records are becoming hard to maintain, what are the limitations?▼

Architecture Decision Records become hard to maintain when created inconsistently, causing decisions to diverge from implementation details. Limitations arise without standard templates and lifecycle governance for deprecation and supersession to keep records coherent.