/ca-adr-status
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-adr-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ca-adr-status
Context preview
The summary Claude sees to decide when to auto-load this skill.
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
SKILL.md
ca-adr-status.SKILL.mdname: ca-adr-status description: Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only. argument-hint: "(none) | --adr N"
$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 (`${CLAUDE_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`.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
Other skills on codearbiter.
- /brainstorming
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No
Open skill - /commit-gate
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message,
Open skill - /context-check
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Open skill - /context-creation
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase
Open skill - /crypto-compliance
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive
Open skill - /debug
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a known bug). Five gated phases: capture, hypothesize, gather, decide, hand off. Investigation only, no code changes; exits to /fix, /adr, or a no-action close.
Open skill