# Adr

> Create or review Architecture Decision Records with ADR Kit's four verification gates and lifecycle rules.

- Skill: `rvdbreemen/adr-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rvdbreemen/adr-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rvdbreemen/adr-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: rvdbreemen (https://skillmd.com/u/rvdbreemen)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rvdbreemen/adr-2

---


<!-- Generated by scripts/build-client-adapters.py from clients/workflows.json; schema v1; client codex-cli. -->
# ADR authoring

Invoke explicitly with `$adr-kit:adr` when needed.
Resolve `<plugin-root>` from this installed skill. Use only bundled,
local ADR Kit tools and follow this canonical workflow:

1. Query the generated ADR index for relevant Accepted ADRs before writing, open only returned sources, and report conflicts.
2. Run `python <plugin-root>/bin/adr profiles --format json`; use only a returned profile with `available: true`.
3. Use `madr` as the default; support `nygard` and `canonical` only when returned as available, and never invent a profile or template.
4. Qualify `<subject>` as a consequential, difficult-to-reverse decision before creating a record; do not create an ADR for an ordinary reversible implementation choice.
5. Create a Proposed record, then follow the canonical grill protocol for context, decision, alternatives, consequences, risks, mitigations, evidence, scope, ownership, conflicts, and Open Questions.
6. Show the final acceptance packet and require an explicit `yes` in this active session before invoking `adr accept ... --confirm`; require Completeness, Evidence, Clarity, and Consistency and supersede rather than rewriting Accepted decisions.

Do not contact another model or mutate user-owned instructions.