architecture-decision-records

Name: architecture-decision-records
Availability: InStock
Author: drluggels

Create and manage ADRs with templates like MADR, lightweight, RFC, and Y-Statement.

3|Updated Jan 8, 2026

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

Ready to run

npx skills add https://github.com/DrLuggels/my_dhbw --skill architecture-decision-records-drluggels

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/DrLuggels/my_dhbw/tree/main/.claude/plugins/documentation-generation/skills/architecture-decision-records
Command: npx skills add https://github.com/DrLuggels/my_dhbw --skill architecture-decision-records-drluggels

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

Core Features & Use Cases

ADR Creation: Generate new Architecture Decision Records using various templates (Standard, Lightweight, Y-Statement, Deprecation, RFC).
ADR Management: Maintain an organized index of ADRs, track their status (Proposed, Accepted, Deprecated, Superseded, Rejected), and manage their lifecycle.
Use Case: When deciding on a new primary database for a project, use this Skill to create an ADR that details the context, considered options (e.g., PostgreSQL vs. MySQL vs. MongoDB), the final decision, and its consequences.

Quick Start

Use the architecture-decision-records skill to create a new ADR titled "Adopt 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 to track architectural rationale and context?▼

You create Architecture Decision Records using templates like MADR, lightweight, or Y-Statement formats to capture context, options, decisions, and consequences. This Skill facilitates ADR generation to ensure architectural rationale and historical context are maintained.

What is the best way to manage the lifecycle of an Architecture Decision Record?▼

Manage the ADR lifecycle by tracking status transitions like Proposed, Accepted, Deprecated, Superseded, or Rejected. This Skill maintains an organized index of ADRs and provides guidance on review processes to handle architectural status changes effectively.

Does this ADR workflow integrate with adr-tools for automated documentation?▼

Yes, this ADR workflow integrates with adr-tools for automation. It combines structured templates like MADR and RFC with the tool's capabilities to streamline the creation and maintenance of your technical decision documentation.

Can I use different templates like RFC or deprecation formats for software design decisions?▼

Yes, you can use various templates including Standard, Lightweight, Y-Statement, Deprecation, and RFC formats for software design decisions. This Skill supports multiple formats to accommodate different architectural choices and technical documentation needs.

When should I create an Architecture Decision Record to manage technical debt?▼

Create an Architecture Decision Record when making significant technical choices like selecting a primary database or adopting a framework to manage technical debt. Documenting context and consequences early prevents future ambiguity and tracks architectural shifts over time.