architecture-decision-records

Create and manage Architecture Decision Records using multiple templates.

10|2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/bugrabilge/bilge-development-kit --skill architecture-decision-records-bugrabilge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/bugrabilge/bilge-development-kit/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/bugrabilge/bilge-development-kit --skill architecture-decision-records-bugrabilge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adr-tools, and includes scripts (resource) and references (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

  • ADR Creation: Generate Architecture Decision Records using various templates (Standard, Lightweight, Y-Statement, Deprecation, RFC).
  • ADR Management: Organize ADRs within a project, maintain an index, and manage their lifecycle (Proposed, Accepted, Deprecated, etc.).
  • Use Case: When deciding on a new database technology for a critical system, use this Skill to create an ADR that details the context, considered options, the final decision, and its consequences.

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
How do I document technical decisions using Architecture Decision Records?

You can document technical decisions by generating Architecture Decision Records using templates like Standard, Lightweight, Y-statement, deprecation, or RFC formats to capture context, options, and consequences.

What is the best way to manage the lifecycle of an architectural decision?

Manage the lifecycle of an architectural decision by tracking its status from Proposed to Accepted or Deprecated, maintaining a project index, and integrating with adr-tools for automated organization.

Can I use adr-tools to automate RFC and ADR creation?

Yes, this Skill integrates with adr-tools to automate the creation and management of Architecture Decision Records, supporting multiple templates including MADR, lightweight, Y-statement, and RFC formats.

When do I need an ADR for software architecture decisions?

You need an ADR when making significant technical decisions like adopting a new database technology, ensuring you capture the context, considered options, final decision, and consequences for historical reference.

Does this ADR approach support different documentation templates for various technical decisions?

Yes, the ADR approach supports multiple templates including MADR, lightweight, Y-statement, deprecation, and RFC formats, allowing you to standardize different types of technical decisions effectively.

What is the difference between an RFC and a standard Architecture Decision Record?

An RFC template is tailored for proposing changes and soliciting feedback, while a standard ADR documents the final architectural decision, context, and consequences after evaluation.