When should I write an ADR using this skill?

You should write an ADR when choosing a technology or framework, making decisions that are hard to reverse, or implementing an approach that might confuse future engineers if not explained.

Does this skill maintain a history of superseded decisions?

Yes, it includes a status for 'Superseded' and encourages referencing new ADRs in old ones to ensure the documentation remains a cohesive timeline of the project's evolution.

How does this skill help with team collaboration?

It provides a clear status lifecycle (Proposed, Accepted, etc.) and a standardized format that makes it easy for team members to review, comment on, and understand architectural changes.

What is an Architecture Decision Record (ADR)?

An ADR is a document that captures an important architectural decision, its context, and its consequences. It serves as a historical record for why certain technical paths were chosen.

Architecture Decision Record (ADR)

Name: Architecture Decision Record (ADR)
Author: chavangorakh1999

bychavangorakh1999

0•

Collaboration Tools

Standardizes the capture and management of critical architectural decisions to ensure team alignment and long-term project maintainability.

This skill empowers developers to document significant architectural choices using the ADR framework, capturing context, rationale, and consequences in a standardized format. By providing a structured template and status lifecycle (Proposed, Accepted, Superseded), it prevents 'architectural rot' and allows future engineers to understand the historical constraints and trade-offs behind the current codebase. It is essential for teams looking to maintain a clear, searchable history of their technical evolution.

Key Features

01Standardized ADR markdown template with context and rationale sections

02Comprehensive impact analysis including positive, negative, and risk assessments

03Comparison of alternative solutions and rejection reasoning

04Structured status lifecycle tracking (Proposed, Accepted, Deprecated, Superseded)

05Centralized ADR index management for easy project-wide discovery

060 GitHub stars

Use Cases

01Recording trade-offs for high-impact decisions like authentication strategies or API designs

02Selecting a primary technology stack, database, or framework for a new project

03Documenting complex migrations or shifts in architectural patterns

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chavangorakh1999/sde-skills adr

For use in Claude.ai and ChatGPT