mcpbeat

Ca Status

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.

520 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
138
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-status

The instruction itself

5 sections, as written by the author

$ca-status — state snapshot

A read-only summary of .codearbiter/ state. No skill is routed to; no file is modified.

Flow

The orchestrator reads and presents:

  • Stage — the stage: maturity value from <project-root>/.codearbiter/CONTEXT.md frontmatter.
  • Pipelines — every slug in <project-root>/.codearbiter/specs/ and plans/, with how

far 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.

  • Open tasks — the in-flight count from <project-root>/.codearbiter/open-tasks.md

(top-level - bullets excluding done - [x]; the same _taskboardlib count the

SessionStart hook uses).

  • Open questions — the count of unresolved [CONFIRM-NN] placeholders in

<project-root>/.codearbiter/open-questions.md.

  • Overrides since last checkpoint — entries in <project-root>/.codearbiter/overrides.log

newer than the marker in <project-root>/.codearbiter/last-checkpoint.

  • Current branch — from git.

Output

## 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.

When NOT to use

  • A full cross-cutting review → $ca-checkpoint.
  • A specific question → $ca-btw.

Hard gate

Read-only. MUST NOT modify any file. MUST NOT resolve a [CONFIRM-NN] it surfaces. No skill is routed

to by this command.

How to use it

Copy the folder

Take arbiterforge/ca-status from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.