mcpbeat

Ca Adr

arbiterforge/ca-adr

Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.

339 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
138
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-adr

The instruction itself

4 sections, as written by the author

$ca-adr — author an ADR

Record an architectural decision as a numbered, dated ADR. Title the decision clearly — name what was

decided, not what was considered ("Use PostgreSQL as the primary database", not

"Database selection"). This is the only sanctioned path to author an ADR.

Routes to

The decision-lifecycle skill (${CLAUDE_PLUGIN_ROOT}/routines/decision-lifecycle/SKILL.md). The skill

owns numbering, the file template, the proposed → accepted → superseded | rejected status lifecycle,

and writes the file to <project-root>/.codearbiter/decisions/. Status transitions require

explicit user instruction; the orchestrator never advances an ADR on its own.

When NOT to use

  • Check the health of existing ADRs → $ca-adr-status.
  • Reconcile or challenge a suspect ADR → $ca-reconcile.
  • Ask about a decision without recording it → $ca-btw.

Hard gate

An ADR is authored ONLY via $ca-adr with explicit user attribution. MUST NOT author an ADR as the

disposition of a routine finding — decision-worthy findings surface to the user or to

open-questions.md as a [CONFIRM-NN]. MUST NOT resolve a [CONFIRM-NN] in the ADR by guessing.

How to use it

Copy the folder

Take arbiterforge/ca-adr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.