Ca Adr Agent Skill
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/arbiterForge/codeArbiter --skill ca-adrThe 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 (<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.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take arbiterforge/codearbiter-ca-adr from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.