manage-adr

Initialize, create, supersede, link, and report Architecture Decision Records with Mermaid diagrams.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/yu-iskw/dbt-heros --skill manage-adr-yu-iskw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-adr
Source: https://github.com/yu-iskw/dbt-heros/tree/main/.claude/skills/manage-adr
Command: npx skills add https://github.com/yu-iskw/dbt-heros --skill manage-adr-yu-iskw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting significant technical decisions, ensuring that the rationale behind architectural choices is preserved and accessible for future reference.

Core Features & Use Cases

  • Initialize ADRs: Set up the ADR directory structure within your project.
  • Create and Supersede ADRs: Generate new Architecture Decision Records or update existing ones to reflect changes.
  • Link ADRs: Establish relationships between related ADRs to track evolution.
  • Visualize Architecture: Integrate Mermaid diagrams to visually represent complex decisions and system designs.
  • Use Case: When introducing a new microservice, use this Skill to create an ADR detailing the decision, its context, the chosen technology, and potential consequences, including a Mermaid diagram of the service's interaction with others.

Quick Start

Initialize ADRs in your project by running 'adr init docs/adr'.

Frequently Asked Questions about manage-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architectural decisions using Architecture Decision Records?

Architecture Decision Records document technical design choices by creating structured files detailing the context, decision, and consequences of architectural choices, which you can initialize and manage within your project directory.

What is the best way to track the evolution of technical decisions in a project?

Tracking the evolution of technical decisions involves superseding and linking existing records to establish relationships between past and new choices, ensuring the rationale behind architectural changes is preserved and accessible for future reference.

Can I use Mermaid diagrams to visualize architecture within decision records?

Yes, you can integrate Mermaid diagrams within Architecture Decision Records to visually represent complex technical decisions and system designs, optionally generating diagram outputs using Graphviz.

Do I need adr-tools installed to manage decision records?

Yes, installing adr-tools is required to manage Architecture Decision Records, and Graphviz is optionally needed if you want to generate visual diagrams from your technical documentation.

How do I initialize an ADR directory structure for my project?

Initializing an ADR directory structure involves running the initialization command to set up a dedicated folder, such as 'docs/adr', where your architecture decision records and their associated metadata will be stored.

What limitations should I consider when superseding architecture decision records?

When superseding architecture decision records, ensure relationships between old and new records are properly linked to maintain context, as the workflow relies on adr-tools and may require Graphviz for diagram generation.