mcpbeat

Ca Adr Status

arbiterforge/codearbiter-ca-adr-status

Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.

309 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-status

The instruction itself

4 sections, as written by the author

/ca-adr-status — ADR health scan

Survey the health of recorded ADRs. Read-only — no file is modified. With --adr N the scan focuses

on a single ADR; with no argument it scans every ADR under

<project-root>/.codearbiter/decisions/.

Routes to

The decision-lifecycle skill (<plugin-root>/routines/decision-lifecycle/SKILL.md) in its

health-scan mode. For each ADR it flags: aged decisions, proposed ADRs never challenged,

supersession candidates (a newer ADR or code pattern contradicts the decision), and unresolved

[CONFIRM-NN] placeholders. Findings aggregate into a structured report; nothing is changed.

When NOT to use

  • Author a new ADR → /ca-adr.
  • Challenge or reconcile a specific ADR in depth → /ca-reconcile.
  • Ask what a specific ADR says → /ca-btw.

Hard gate

Read-only — MUST NOT modify any file. MUST NOT resolve a [CONFIRM-NN] found during the scan —

surface it and stop. A supersession candidate that contradicts an accepted ADR is flagged for

/ca-conflict.

How to use it

Copy the folder

Take arbiterforge/codearbiter-ca-adr-status 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.