architecture-decision-record

Write, update, and query Architecture Decision Records using Markdown templates.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/a53ali/ai-dev --skill architecture-decision-record-a53ali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-record
Source: https://github.com/a53ali/ai-dev/tree/main/skills/engineer/architecture-decision-record
Command: npx skills add https://github.com/a53ali/ai-dev --skill architecture-decision-record-a53ali

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps engineers document, update, and reference Architecture Decision Records (ADRs) to keep a clear, actionable record of significant architectural decisions.

Core Features & Use Cases

  • ADRs Creation and Management: Generate new ADRs following a structured template, with version control and status tracking.
  • Decision Context and Consequences: Capture the reasoning, trade-offs, and risks associated with each architectural decision.
  • Query Existing Records: Retrieve historical records to understand why specific design choices were made.

Quick Start

Write a new Architecture Decision Record for choosing microservices over monoliths.

Frequently Asked Questions about architecture-decision-record

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

FAQPage Schema
How do I document software architecture decisions to track context and consequences?

You document software architecture decisions using Architecture Decision Records (ADRs) to capture context, rationale, consequences, and alternatives. This Skill generates Markdown-based technical documentation with automated numbering, version control, and status tracking.

What is an Architecture Decision Record and when should I use one for technical documentation?

An Architecture Decision Record (ADR) is a technical documentation file capturing significant architectural decisions, including reasoning, trade-offs, and risks. Use ADRs when structural design choices impact project management and require a clear, actionable historical record.

Can I update and query existing ADRs to understand why specific design choices were made?

Yes, you can query existing Architecture Decision Records to retrieve historical context and understand why specific design choices were made. The Skill supports updating ADRs with version control and status tracking for ongoing maintenance.

Does this ADR tool support version control and status tracking for architecture decisions?

Yes, this ADR tool supports version control and status tracking for architecture decisions. It maintains and references technical documentation records by capturing decision context, alternatives, and consequences while tracking the lifecycle status of each ADR.

What is the best way to write a new Architecture Decision Record for choosing microservices over monoliths?

The best way to write a new Architecture Decision Record for choosing microservices over monoliths is using a structured Markdown template. This Skill automates ADR numbering and helps document context, rationale, alternatives, and consequences of the architectural decision.