Why is ADR management important for teams?

ADRs prevent 'architectural drift' by ensuring that every significant choice is documented with its trade-offs, helping future maintainers understand why certain paths were taken or rejected.

An Architecture Decision Record (ADR) is a document that captures an important architectural decision made along with its context and consequences, typically stored as a Markdown file in the project repository.

Can I search through previous architectural decisions?

Yes, the skill includes built-in commands to list ADR titles or grep through their content to find relevant past decisions and their rationales.

How does this skill handle superseded decisions?

When a new decision replaces an old one, the skill updates the status of the original ADR to 'Superseded' and provides a reference to the new record, preserving an immutable history of the architecture's evolution.

Where are the ADR files stored?

The skill follows a standard repository structure, storing records in the /architecture/adr/ directory for easy access and version control.

ADR Management

Name: ADR Management
Author: melodic-software

bymelodic-software

•

학습 및 문서화

Manages Architecture Decision Records (ADRs) to document and track significant technology choices and design decisions over time.

소개

The ADR Management skill provides a structured framework for development teams to record the rationale behind architectural decisions, ensuring long-term maintainability and smoother team onboarding. It automates the creation of standardized ADR files using sequential numbering, manages the decision lifecycle from proposal to supersession, and documents alternatives and trade-offs. By maintaining an immutable history of technical choices within the repository, it helps teams understand the 'why' behind the code and prevents the loss of critical architectural context.

주요 기능

1 GitHub stars
Lifecycle management for tracking Proposed, Accepted, Deprecated, and Superseded statuses
Automated ADR file creation with sequential numbering and kebab-case naming
Seamless integration with architecture principles and trade-off documentation
Standardized templates covering context, decision, consequences, and alternatives
Built-in search functionality to query existing decisions by keyword or title

사용 사례

Recording the reasoning behind major refactoring efforts or pattern changes
Creating a searchable knowledge base for onboarding new engineers to a complex system
Documenting the selection of a specific database or framework for a new project

소개

주요 기능

1 GitHub stars
Lifecycle management for tracking Proposed, Accepted, Deprecated, and Superseded statuses
Automated ADR file creation with sequential numbering and kebab-case naming
Seamless integration with architecture principles and trade-off documentation
Standardized templates covering context, decision, consequences, and alternatives
Built-in search functionality to query existing decisions by keyword or title

사용 사례

Recording the reasoning behind major refactoring efforts or pattern changes
Creating a searchable knowledge base for onboarding new engineers to a complex system
Documenting the selection of a specific database or framework for a new project