# Adr

> Use when the user asks to write an ADR, says "create an ADR for X", "document this decision", "we need an ADR", or whenever you're about to make a significant design choice — introducing a port/adapter/SPI, picking between viable approaches, altering data flow, adding a dependency, or establishing a project-wide convention. Default to invoking this skill for any architectural change.

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

---


# Write an Architecture Decision Record

Follow the workflow in `docs/workflows/adr.md` to create a new ADR in `docs/adr/`.

Read that file and follow it exactly. It covers when an ADR is required, how to number it, the body structure (including the `Deciders` field), and how to link the ADR from the work it accompanies.

