How does this skill improve team collaboration?

It provides a centralized source of truth for technical decisions, allowing new team members to understand the history and reasoning behind the current codebase without hunting through old tickets.

Does this skill support existing ADR formats?

Yes, it follows standard ADR structures including Context, Decision, Alternatives, and Consequences, and can adapt to your repository's specific documentation layout.

When should I use the architecture-adr skill?

You should use it whenever a new technology choice is made, a design pattern is implemented, or when an existing architectural direction is changed or refined.

What is an Architecture Decision Record (ADR)?

An ADR is a short text file that captures an important architectural decision, including the context in which it was made and the consequences it has for the project's future.

Architecture Decision Record (ADR) Manager

Name: Architecture Decision Record (ADR) Manager
Author: gw-ai-security

bygw-ai-security

학습 및 문서화

Documents architectural decisions and technology stack updates to maintain a transparent, traceable history of project evolution.

소개

The architecture-adr skill enables Claude to systematically record and manage technical decisions using the Architecture Decision Record (ADR) pattern. It streamlines the process of capturing the context, rationale, considered alternatives, and long-term consequences of design choices. By integrating directly with your repository's documentation structure, it ensures that the critical 'why' behind your architecture remains accessible and organized, preventing institutional knowledge from being lost in informal chats or ephemeral code comments.

주요 기능

Consistency checks against existing architectural documentation
Organized file management within dedicated architecture directories
Automated linking between decisions, requirements, and project modules
Standardized ADR creation including context, decisions, and consequences
Support for updating and revising historical technical decisions
0 GitHub stars

사용 사례

Documenting the rationale for choosing a specific tech stack or framework
Recording design patterns used to solve complex integration problems
Tracking revisions to architectural decisions as project requirements evolve

소개

주요 기능

Consistency checks against existing architectural documentation
Organized file management within dedicated architecture directories
Automated linking between decisions, requirements, and project modules
Standardized ADR creation including context, decisions, and consequences
Support for updating and revising historical technical decisions
0 GitHub stars

사용 사례

Documenting the rationale for choosing a specific tech stack or framework
Recording design patterns used to solve complex integration problems
Tracking revisions to architectural decisions as project requirements evolve