architecture-decision-records

Document architecture decisions with standardized ADR templates and lifecycle statuses.

1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/Dhumitech/DHUMI-AI-RESOURCE --skill architecture-decision-records-dhumitech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Dhumitech/DHUMI-AI-RESOURCE/tree/main/AI-Engineer-planner-Skills/00-plan/architecture-decision-records
Command: npx skills add https://github.com/Dhumitech/DHUMI-AI-RESOURCE --skill architecture-decision-records-dhumitech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams document and communicate architectural decisions by creating Architecture Decision Records (ADRs) that capture context, options, decisions, and consequences.

Core Features & Use Cases

  • Standard ADR templates and guidance to document context, options, decisions, and consequences.
  • Lifecycle management (Proposed, Accepted, Deprecated, Superseded) with a discoverable index and cross-linking of related ADRs.
  • Templates for multiple formats (MADR, Lightweight ADR, Y-Statement, RFC) to fit different scopes and governance needs.
  • Real-world use case: ADR-0001 documenting a database technology choice and its trade-offs.

Quick Start

Create a new ADR from the template, fill in the Context, Decision, and Consequences, and link related ADRs.

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 architecture decisions and their rationale effectively?

You can document architecture decisions using Architecture Decision Records (ADRs) that capture context, options, decisions, and consequences. This skill provides standardized templates to record technology choices and trade-offs across software projects.

What ADR template formats are available for software architecture governance?

Available ADR template formats include MADR, Lightweight ADR, Y-Statement, and RFC. These templates fit different scopes and governance needs for documenting architectural decisions and their lifecycle states.

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

Architecture Decision Records support lifecycle management with statuses like Proposed, Accepted, Deprecated, and Superseded. A discoverable index and cross-linking of related ADRs maintain governance across the lifecycle.

When do I need to use Architecture Decision Records for my software project?

You need Architecture Decision Records when software architecture teams must document technology choices, trade-offs, and lifecycle states. ADRs capture the context, decision, and consequences for future reference.

What is the best way to link related architecture decisions across different projects?

The best way to link related architecture decisions is through cross-linking related ADRs within a discoverable index. This maintains context across projects as decisions evolve from Proposed to Superseded.

Does this ADR documentation approach work for lightweight architectural choices?

Yes, this approach works for lightweight architectural choices by offering Lightweight ADR and Y-Statement templates. These formats fit smaller scopes while still capturing the core context, decision, and consequences.