Does this skill help with existing ADRs?

Yes, it can manage the full lifecycle of a decision, including marking old ADRs as superseded and linking them to new records when architectural requirements change.

How does this improve team collaboration?

It provides a clear, searchable history of why certain paths were taken, preventing repeated arguments over the same technical topics and ensuring everyone is aligned on the current architecture.

When should I use the ADR skill?

Use this skill when making hard-to-reverse decisions, such as choosing a database, adopting a new framework, or defining a significant system-wide pattern that future engineers need to understand.

What is an ADR in software development?

An Architecture Decision Record (ADR) is a document that captures a significant architectural decision, the context in which it was made, and the consequences it has for the project's future.

ADR (Architecture Decision Record) Architect

Name: ADR (Architecture Decision Record) Architect
Author: chavangorakh1999

bychavangorakh1999

0•

콘텐츠 관리

Generates and manages structured Architecture Decision Records to document technical choices, trade-offs, and long-term project rationale.

The ADR skill enables Claude to act as a technical architect by facilitating the creation and maintenance of Architecture Decision Records (ADRs). It provides a standardized framework for capturing the 'why' behind critical technical decisions, including context, consequences, and alternatives considered. By maintaining a living history of a project's evolution, this skill helps engineering teams avoid 'decision rot,' streamlines onboarding for new developers, and ensures that high-impact choices regarding frameworks, databases, and infrastructure are documented with professional rigor.

주요 기능

01Automatic ADR Index generation for easy documentation navigation

02Standardized ADR templates including Context, Decision, and Consequences

03Context-aware triggers for when to document vs. when to skip ADRs

04Comparison logic for documenting and rejecting alternative approaches

050 GitHub stars

06Automated status lifecycle tracking (Proposed, Accepted, Superseded)

사용 사례

01Recording team-wide conventions for authentication, security, or API design

02Selecting a core technology stack or migrating to a new database engine

03Documenting architectural patterns like microservices vs. monolith transitions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add chavangorakh1999/sde-skills adr

For use in Claude.ai and ChatGPT