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.
camunda npx skillmds@latest add camunda/adr 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.
camunda/camunda-security-library/tree/main/.claude/skills/adr commit 11b87ff07a