How does this improve team collaboration?

By documenting the 'why' behind technical choices, it reduces repetitive debates, provides a history for new team members, and makes architectural trade-offs explicit.

When should I use the ADR skill?

Use this skill whenever you make a non-trivial technical choice, such as adopting a new framework, changing API patterns, or choosing between database technologies.

What is an Architecture Decision Record (ADR)?

An ADR is a document that captures a significant architectural decision, the context in which it was made, and the consequences of that choice for the project.

Does it support different documentation formats?

Yes, it includes templates for standard MADR, lightweight records, Y-statements, and formal Request for Comments (RFC) styles.

Can I use it to update or replace old decisions?

Absolutely. The skill includes specific patterns for superseding and deprecating previous ADRs as your system and requirements evolve.

Architecture Decision Records (ADR)

Name: Architecture Decision Records (ADR)
Author: Tahir-yamin

byTahir-yamin

•

콘텐츠 관리

Generates and manages Architecture Decision Records (ADRs) to document significant technical choices and their underlying rationale.

This skill empowers developers and architects to document high-impact technical decisions using standardized ADR formats, ensuring transparency and long-term maintainability. It provides structured templates for various scenarios—including lightweight updates, formal RFCs, and deprecation notices—allowing teams to capture context, decision drivers, and consequences while building a historical record of architectural evolution. By formalizing the decision-making process, it helps teams avoid 'architecture by accident' and provides essential context for future maintainers and new hires.

주요 기능

01Provides multiple standardized templates including MADR, Lightweight, and Y-Statement formats.

023 GitHub stars

03Automates the documentation of technology deprecation and superseding cycles.

04Includes RFC-style templates for proposing and discussing major architectural shifts.

05Establishes best practices for ADR directory structures and historical indexing.

06Guides users in identifying and documenting decision drivers, trade-offs, and consequences.

사용 사례

01Onboarding new engineers by providing a clear history of past architectural choices.

02Recording the rationale and trade-offs of a major microservices migration.

03Documenting the selection of a new primary database or frontend framework.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tahir-yamin/dev-engineering-playbook architecture-decision-records

For use in Claude.ai and ChatGPT

Download Skill