skills.rest
FatBy
FatByCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Create and manage Architecture Decision Records with lifecycle templates.

2|Updated Feb 13, 2026
Search Tags:#architecture#decision making#documentation#software design#adr#technical governance
One-click install
npx skills add https://github.com/FatBy/DD-OS --skill architecture-decision-records-fatby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/FatBy/DD-OS/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/FatBy/DD-OS --skill architecture-decision-records-fatby

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams systematically document significant technical decisions, ensuring clarity, context, and a traceable history of architectural choices.

Core Features & Use Cases

  • ADR Creation: Generate Architecture Decision Records using various templates (Standard, Lightweight, Comprehensive).
  • Lifecycle Management: Understand and apply the ADR lifecycle (Proposed, Accepted, Rejected, Deprecated, Superseded).
  • Best Practices: Follow established guidelines for writing and managing ADRs.
  • Use Case: When deciding on a new database technology, use this Skill to create an ADR that outlines the context, decision drivers, considered options, the final decision, and its consequences.

Quick Start

Use the architecture-decision-records skill to create a new ADR for adopting PostgreSQL as the primary database.

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 technical decisions for a software engineering project?▼

Use Architecture Decision Records (ADRs) to document significant technical decisions systematically. ADRs outline the context, decision drivers, considered options, final decision, and consequences, ensuring clarity and a traceable history of architectural choices.

What is the lifecycle of an Architecture Decision Record?▼

The ADR lifecycle tracks technical governance through statuses: Proposed, Accepted, Rejected, Deprecated, and Superseded. This lifecycle management provides a traceable history of architectural choices throughout a software engineering project.

What templates can I use for writing an Architecture Decision Record?▼

You can generate Architecture Decision Records using Standard, Lightweight, or Comprehensive templates. These templates support best practices for writing ADRs by structuring context, decision drivers, considered options, and consequences.

When do I need to create an ADR for software design?▼

Create an ADR when making significant technical choices, such as adopting a new database technology like PostgreSQL. ADRs address the need for structured technical decision-making and clear technical governance in software engineering projects.

What is the best way to manage technical governance for architectural choices?▼

The best way to manage technical governance is applying the ADR lifecycle to track architectural choices. By documenting decisions from Proposed to Accepted or Superseded, teams maintain a traceable history of significant technical decisions.

Related Skills

Explore More Software Engineering Skills→
testdoubletestdouble
198

architectural-decision-record

Create, extract, and convert Architectural Decision Records to standard templates.

Official
Advanced
burgebjburgebj

document-release

Parse Git diff outputs to update Markdown documents after releases.

Community
Intermediate
ghalacticghalactic
2

adr-skill

Create, maintain, and review Architecture Decision Records in a repository.

Official
Intermediate
asanexampleasanexample
1

authoring-adrs

Write and manage Architecture Decision Records with structured templates and lifecycle rules.

Official
Advanced