arbiterforge/ca-status
Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-status
A read-only summary of .codearbiter/ state. No skill is routed to; no file is modified.
The orchestrator reads and presents:
stage: maturity value from <project-root>/.codearbiter/CONTEXT.md frontmatter.<project-root>/.codearbiter/specs/ and plans/, with howfar each got: spec awaiting approval, spec approved / no plan, plan in progress (ACCEPTED count
vs. total from the plan's status column), or complete. An interrupted pipeline is resumable via
$ca-feature — say so on its line.
<project-root>/.codearbiter/open-tasks.md(top-level - bullets excluding done - [x]; the same _taskboardlib count the
SessionStart hook uses).
[CONFIRM-NN] placeholders in<project-root>/.codearbiter/open-questions.md.
<project-root>/.codearbiter/overrides.lognewer than the marker in <project-root>/.codearbiter/last-checkpoint.
## Project status — YYYY-MM-DD
Stage: N
Branch: <current branch>
Pipelines:
<slug> plan 3/7 ACCEPTED — resume with $ca-feature "<slug>"
<slug> spec approved, no plan
Open tasks: N
Open questions: N ([CONFIRM-NN] unresolved)
Overrides since last checkpoint: N
No specs and no plans → Pipelines: none.
If [CONFIRM-NN] placeholders are open, surface them — do not resolve them here.
$ca-checkpoint.$ca-btw.Read-only. MUST NOT modify any file. MUST NOT resolve a [CONFIRM-NN] it surfaces. No skill is routed
to by this command.
Take arbiterforge/ca-status 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.