architecture-decision-records

Create and manage Architecture Decision Records using MADR, lightweight, Y-statement, deprecation, and RFC templates.

2|Updated Feb 5, 2026

Search Tags:#architecture #decision making #documentation #adr #rfc #technical decisions

Ready to run

npx skills add https://github.com/yashvinthan/DuskSpendr --skill architecture-decision-records-yashvinthan

💬 Prompt for ChatGPT / Claude Chat▼

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

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 framework for documenting significant technical decisions, ensuring clarity, rationale, and historical context for architectural choices.

Core Features & Use Cases

ADR Creation & Management: Guides users through creating, updating, and managing Architecture Decision Records (ADRs).
Template Variety: Offers multiple templates (Standard, Lightweight, Y-Statement, Deprecation, RFC) to suit different decision types.
Use Case: When deciding on a new database technology, use this Skill to document the context, considered options, the final decision, and its consequences, creating a lasting record for the team.

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 for my software architecture?▼

Document technical decisions by creating Architecture Decision Records (ADRs) that capture context, options, and consequences. This skill facilitates ADR creation and lifecycle management, enforcing best practices for recording significant technical decisions.

What is the difference between an ADR and an RFC format?▼

An ADR (Architecture Decision Record) documents a final technical decision and its rationale, while an RFC (Request for Comments) format is used to propose and discuss decisions. This skill supports creating both, along with standard MADR, lightweight, Y-statement, and deprecation templates.

How do I create a new ADR for adopting a new technology?▼

Create a new ADR by using this skill to guide you through documenting the context, considered options, final decision, and consequences of adopting a new technology. It supports various templates including standard MADR and lightweight formats to suit your needs.

Does this ADR tool work with adr-tools?▼

Yes, this ADR tool depends on adr-tools to facilitate the creation and management of Architecture Decision Records. It integrates with adr-tools while providing additional template varieties and enforcing best practices for technical decision documentation.

Can I manage the lifecycle and review process of architecture decisions?▼

Yes, you can manage the lifecycle and review processes of architecture decisions using this skill. It supports updating existing ADRs and enforces best practices to maintain accurate historical context for your architectural choices over time.

When should I use a lightweight ADR versus a standard MADR template?▼

Use a lightweight ADR for simpler decisions requiring less context, and a standard MADR template for significant technical decisions needing comprehensive documentation. This skill offers both, along with Y-statement and deprecation formats, to suit different decision types.