An Architectural Decision Record (ADR) is a document that captures a significant technical decision, including the context in which it was made and the consequences it has for the project.

How do I create the record once the skill suggests it?

You can use the command /adr:create within your Claude Code environment to quickly generate a new architectural decision record.

When will this skill suggest an ADR?

It suggests an ADR when it detects high-impact changes like adding new frameworks, changing security protocols, migrating technologies, or restructuring core modules.

Does it suggest an ADR for every code change?

No, it specifically avoids suggesting ADRs for bug fixes, minor refactors, routine dependency updates, or style changes to keep prompts relevant.

Architectural Decision Records (ADR)

Name: Architectural Decision Records (ADR)
Author: dariuszparys

bydariuszparys

学習とドキュメンテーション

Suggests documenting significant architectural changes as ADRs to capture technical context and long-term reasoning.

概要

The ADR Skill helps maintain a healthy codebase history by identifying moments where long-term architectural choices are made and prompting for their documentation. It monitors for significant changes such as new framework integrations, infrastructure shifts, or core refactoring, then provides a non-intrusive nudge to use the /adr:create command. By capturing the rationale behind technical decisions as they happen, this skill ensures that future developers understand the context, trade-offs, and intentions behind the system's architecture.

主な機能

0 GitHub stars
Streamlined integration with the /adr:create command
Clear differentiation between routine tasks and ADR-worthy decisions
Intelligent detection of architectural shifts and pattern changes
Context-aware suggestions for documenting technical trade-offs
Non-intrusive prompts delivered only after significant work is completed

ユースケース

Capturing the rationale behind a breaking API change or major refactoring
Documenting the introduction of a new database or caching layer
Recording trade-offs when choosing between two competing frameworks or libraries

概要

主な機能

0 GitHub stars
Streamlined integration with the /adr:create command
Clear differentiation between routine tasks and ADR-worthy decisions
Intelligent detection of architectural shifts and pattern changes
Context-aware suggestions for documenting technical trade-offs
Non-intrusive prompts delivered only after significant work is completed

ユースケース

Capturing the rationale behind a breaking API change or major refactoring
Documenting the introduction of a new database or caching layer
Recording trade-offs when choosing between two competing frameworks or libraries