Does this skill support different ADR formats?

Yes, it supports several industry-standard formats including the Markdown Architecture Decision Record (MADR), lightweight formats, and the concise Y-Statement format.

Can I manage the lifecycle of a decision?

Yes, the skill includes patterns for marking decisions as proposed, accepted, deprecated, or superseded as the project evolves over time.

What is an Architecture Decision Record (ADR)?

An ADR is a short text document that captures a significant architectural decision, including its context, the decision itself, and its consequences.

When should I use the ADR skill?

Use this skill when making significant technical choices like framework adoption, database selection, or security patterns that require long-term rationale for the team.

How does this help with team onboarding?

It provides new team members with a searchable history of why certain technologies were chosen, preventing them from repeating past mistakes or questioning patterns without context.

Architecture Decision Records

Name: Architecture Decision Records
Author: wshobson

bywshobson

•

23,194

Learning & Documentation

Document and maintain significant technical decisions with standardized Architecture Decision Records to capture context and rationale.

About

The Architecture Decision Records (ADR) skill provides a structured framework for documenting, maintaining, and managing significant technical choices within a project. It offers comprehensive templates—including MADR, lightweight, and Y-statement formats—to record the context, trade-offs, and long-term consequences of architectural shifts. By institutionalizing the 'why' behind engineering decisions, this skill ensures that historical knowledge is preserved for future team members, facilitates thorough peer reviews, and streamlines the lifecycle management of architectural evolutions from proposal to deprecation.

Key Features

Automated directory structuring and indexing for architectural documentation
Standardized templates for technology selection, deprecation plans, and design trade-offs
Comprehensive lifecycle management for proposed, accepted, and superseded decisions
23,194 GitHub stars
Support for multiple formats including MADR, Y-Statements, and RFC-style records
Integrated review checklists for security, cost, and technical feasibility assessments

Use Cases

Onboarding new engineers by providing a historical context of the system's architectural evolution
Managing the formal deprecation of legacy systems in favor of modern infrastructure
Capturing the rationale for adopting specific databases or frameworks to prevent future rework

About

Key Features

Automated directory structuring and indexing for architectural documentation
Standardized templates for technology selection, deprecation plans, and design trade-offs
Comprehensive lifecycle management for proposed, accepted, and superseded decisions
23,194 GitHub stars
Support for multiple formats including MADR, Y-Statements, and RFC-style records
Integrated review checklists for security, cost, and technical feasibility assessments

Use Cases

Onboarding new engineers by providing a historical context of the system's architectural evolution
Managing the formal deprecation of legacy systems in favor of modern infrastructure
Capturing the rationale for adopting specific databases or frameworks to prevent future rework