using-adr-plugin

Search and traverse Architecture Decision Records in Obsidian vaults.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill using-adr-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-adr-plugin
Source: https://github.com/RafayelGardishyan/rafayels-marketplace/tree/main/plugins/rafayels-engineering/.opencode/skills/using-adr-plugin
Command: npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill using-adr-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADR plugin helps teams design and document architecture decisions by linking design work to existing Architecture Decision Records stored in the Obsidian vault. It enforces consulting ADRs before making decisions and provides a workflow for creating, updating, and relating ADRs to maintain a coherent decision history.

Core Features & Use Cases

  • Semantic search across ADRs to surface relevant decisions before starting work.
  • Read full ADR content to capture context, constraints, and rationale.
  • Traverse ADR relationships to understand dependencies and impacts.
  • Create or update ADRs and link them with depends_on, relates_to, or supersedes.
  • Integrate with an Obsidian vault for centralized decision-history tracking.

Quick Start

Search for ADRs related to your topic, read the relevant ADRs, explore connected decisions, synthesize findings, and create or update ADRs as appropriate.

Frequently Asked Questions about using-adr-plugin

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

FAQPage Schema
How do I find existing architecture decision records before implementing a new feature?

Semantic search across existing architecture decision records (ADRs) surfaces relevant decisions, constraints, and rationale before you start designing or implementing features. It traverses connected ADRs to reveal dependencies and impacts.

How do I link architecture decision records to maintain a coherent decision history?

You maintain a coherent decision history by creating or updating ADRs and linking them using depends_on, relates_to, or supersedes relationships to connect related architecture decisions.

Does the ADR plugin work with an Obsidian vault for decision tracking?

Yes, the ADR plugin integrates with an Obsidian vault to provide centralized decision-history tracking, allowing you to read full ADR content and traverse ADR relationships directly within your vault.

What is the best way to trace dependencies between Architecture Decision Records?

Graph traversal of ADR relationships traces dependencies and impacts across related architecture decisions. By reading full ADR content and following links, you synthesize constraints and alternatives distributed across records.

Why should I consult ADRs before making software architecture decisions?

Consulting ADRs before making architecture decisions enforces reviewing prior context, constraints, and rationale. This prevents conflicting choices and ensures new designs respect existing dependencies and historical alternatives.

Can I update an existing ADR to supersede an older architecture decision?

Yes, you can update existing ADRs and link them to older records using the supersedes relationship, ensuring the decision history accurately reflects the evolution of architectural choices.