Stats
Actions
Tags
From adr-kit
Loads the Architecture Decision Records most relevant to a task before you implement it, so existing decisions are honored without burning context on the whole ADR set. Give it a topic (e.g. "mqtt discovery", "heap allocation", "caching") and it returns the 3-5 most relevant Accepted ADRs as readable context — title, one-line decision, file path, and relevance score. Read-only and safe to call from parallel subagents. Invoke before starting implementation in a project that has ADRs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/adr-kit:context [topic or task description; e.g. "mqtt discovery"][topic or task description; e.g. "mqtt discovery"]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are running `/adr-kit:context`. Purpose: surface the ADRs that constrain the
You are running /adr-kit:context. Purpose: surface the ADRs that constrain the
task at hand before writing code, so you implement within existing decisions
instead of rediscovering or contradicting them. This is read-only — it never
edits ADRs or code, so it is safe to call from parallel subagents.
Take the topic from the argument. If none was given, ask the user for a short topic or task description (one phrase is enough).
Run the bundled deterministic ranker from the project root. Request JSON so you get the relevance signals, and keep the default limit of 5:
python <adr-kit-plugin-path>/bin/adr-context --format json --limit 5 "<topic>"
--adr-dir <path> if the project keeps ADRs somewhere other than
docs/adr/.--min-score <0-1> to tighten or loosen the relevance cutoff
(default 0.1).If the result is an empty list ([]): tell the user plainly —
"No ADRs match ''; all existing ADRs may apply, or none constrain
this work." Do not invent relevance. Stop here.
Otherwise, for each returned ADR, Read the file and present it as
readable context, not just a filename:
ADR-NNN — <title> (relevance: <score>)## Decision (paraphrase the decision, don't dump
the whole section)Order by relevance (highest first), most relevant ADR last in your message so it stays closest to the work that follows.
Briefly state the net constraint: in one or two sentences, what these decisions require or forbid for the task. Then proceed with (or hand back to) the implementation.
--min-score rather than
assuming no ADR exists./adr-kit:judge or
/adr-kit:adr to resolve it.npx claudepluginhub rvdbreemen/adr-kit --plugin adr-kitProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.