architecture-decision-records

Create and manage Architecture Decision Records using established templates.

32|Updated Feb 3, 2026

Search Tags:#architecture #decision making #documentation #software design #adr #technical decisions

Ready to run

npx skills add https://github.com/t0dorakis/murmur --skill architecture-decision-records-t0dorakis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/t0dorakis/murmur/tree/main/.agents/skills/architecture-decision-records
Command: npx skills add https://github.com/t0dorakis/murmur --skill architecture-decision-records-t0dorakis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured framework and templates for creating, managing, and reviewing Architecture Decision Records (ADRs), ensuring that significant technical choices are well-documented, their rationale is clear, and their lifecycle is tracked.

Core Features & Use Cases

ADR Creation: Generate new ADRs using various templates (Standard, Lightweight, Y-Statement, Deprecation, RFC).
ADR Management: Organize ADRs within a defined directory structure and maintain an index.
Review Process: Facilitate a clear review process with a checklist for ADR submissions.
Automation: Integrate with tools like adr-tools for streamlined ADR lifecycle management.
Use Case: When adopting a new framework, choosing a database, or making a significant API design change, use this Skill to create a formal ADR documenting the context, decision, and consequences.

Quick Start

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

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 project?▼

Document technical decisions by creating Architecture Decision Records (ADRs) that capture the context, rationale, and consequences of significant software design choices throughout their lifecycle.

What is the best way to manage Architecture Decision Records across a project?▼

Manage Architecture Decision Records by organizing them within a defined directory structure, maintaining a central index, and applying structured review checklists to track their lifecycle and ensure documentation consistency.

Can I use different templates for creating ADRs depending on the decision type?▼

Yes, you can create ADRs using multiple templates including Standard, Lightweight, Y-Statement, Deprecation, and RFC formats to suit different types of technical decisions and documentation needs.

Do I need adr-tools to maintain Architecture Decision Records?▼

Using adr-tools is a dependency for this Skill, providing integrated automation to streamline the creation, organization, and lifecycle management of your Architecture Decision Records.

When should I write an Architecture Decision Record instead of standard documentation?▼

Write an Architecture Decision Record when adopting a new framework, choosing a database, or making significant API design changes to formally document the context, decision, and consequences.

Does the ADR review process include a checklist for submissions?▼

Yes, the Architecture Decision Record review process includes a dedicated checklist to facilitate clear evaluations of ADR submissions, ensuring technical decisions meet documentation standards before approval.