/ca-adr
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-adr --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
Context preview
The summary Claude sees to decide when to auto-load this skill.
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
SKILL.md
ca-adr.SKILL.mdname: ca-adr description: Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/. argument-hint: "<decision title>"
$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.
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