architecture-decision-records

Create and manage Architecture Decision Records using standardized templates.

1|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Dbillionaer/wholesaile --skill architecture-decision-records-dbillionaer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Dbillionaer/wholesaile/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/Dbillionaer/wholesaile --skill architecture-decision-records-dbillionaer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adr-tools, and includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides a structured and standardized way to document significant technical decisions, ensuring clarity, rationale, and historical context for architectural choices.

Core Features & Use Cases

  • Standardized ADR Templates: Offers multiple formats (MADR, Lightweight, Y-Statement, Deprecation, RFC) for various decision-making scenarios.
  • ADR Management Guidance: Includes best practices for directory structure, indexing, and review processes.
  • Automation Tools: Demonstrates the use of adr-tools for efficient ADR creation and management.
  • Use Case: When deciding on a new database technology, use this Skill to create an ADR that captures the context, considered options, the final decision, and its consequences, ensuring all stakeholders understand the rationale.

Quick Start

Use the architecture-decision-records skill to create a new ADR for adopting TypeScript.

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 should I document technical decisions?

An Architecture Decision Record (ADR) is a standardized document capturing significant technical decisions, their context, alternatives considered, and consequences. You should create an ADR whenever making a major architectural choice, such as adopting a new technology or framework, to ensure historical rationale is clear to all stakeholders.

How do I create and manage Architecture Decision Records using adr-tools?

You can create and manage Architecture Decision Records by utilizing the `adr-tools` automation tool, which facilitates efficient ADR generation. This Skill provides guidance on using `adr-tools` to structure your ADR directory, index records, and apply templates for documenting technical decisions throughout their lifecycle.

What ADR templates are available for different decision-making scenarios?

Available ADR templates include MADR, Lightweight, Y-Statement, Deprecation, and RFC formats. These templates support various decision-making scenarios, allowing you to document everything from lightweight technical choices to formal architectural requests for comments and deprecations.

Does this approach work for documenting technical debt and deprecating past architecture decisions?

Yes, this approach works for documenting technical debt and deprecating past architecture decisions by utilizing the specific Deprecation ADR template. It ensures that when an architectural choice is reversed or superseded, the context and consequences of that technical debt are formally recorded and reviewed.

What is the best way to structure Architecture Decision Records in a software repository?

The best way to structure Architecture Decision Records is by following standardized directory and indexing best practices. This Skill provides guidance on organizing your ADR directory, ensuring that technical documentation remains easily navigable and reviewable across the development process.