ca-adr
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
npx skills add arbiterForge/codeArbiter --skill ca-adr --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $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.
- Routes to
- When NOT to use
- Hard gate
What does the ca-adr skill do?
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-adr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.