arbiterForge/codeArbiter / plugins/ca-codex/skills/ca-status
ca-status
UnverifiedShow the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
$ca-status — state snapshot
A read-only summary of .codearbiter/ state. No skill is routed to; no file is modified.
Drift mode
With the exact argument drift, load and follow
routines/context-check/SKILL.md. The audit begins read-only; re-scout or re-baseline may
write only after the user's explicit selection. In drift mode the context-check contract governs;
the opening summary and Hard gate below apply only to the no-argument snapshot. With no argument,
continue with the unchanged read-only snapshot below. Reject other arguments rather than treating
them as drift mode.
An initialized refresh is a separate explicit scoped or full selection handled by that existing owner after its read-only report. Neither this argument nor an ordinary status snapshot authorizes a write, a create-context retry or marker reset.
Flow
The orchestrator reads and presents:
- Stage — the
stage:maturity value from<project-root>/.codearbiter/CONTEXT.mdfrontmatter. - Pipelines — every slug in
<project-root>/.codearbiter/specs/andplans/, preserving its existing representation. For HTML, use the installed engine's bounded structured reads (identity,index, symbol-scopedread, ortask-context) through includes/artifacts.md; do not read rendered markup or execute verification to obtain status. For Markdown, read its actual status ledger without creating a counterpart. Report a spec with no plan, implementation in progress, or implementation complete. CountDONEand historicalACCEPTEDtoward implementation completion while retaining their distinct labels. Show verification separately: pending, failed, unknown, or the recorded result and its applicability when available. Completion alone does not establish a passing check, current acceptance, review, or release. Report missing/unreadable state as unknown, not complete. For a selected HTML plan task, includetask-context.check_summarywhen the installed engine suppliestask-context: an unresolved applicable reported failure remains visible after unrelated passes, while stale reports and trimmed history are disclosed separately. When the compatibility path can only use symbol-scoped reads, report the check summary as unknown unless those reads establish it; do not infer a clear summary from missingtask-contextsupport. These caller reports are not verified evidence. A draft spec or plan is not awaiting permission. Show a genuine unresolved product decision, explicit user checkpoint, orBLOCKEDstop with its actual reason; status never clears it. An interrupted pipeline is resumable via$ca-feature— say so on its line. - Open tasks — resolve the installed
hooks/work.pythrough the installed helper card: includes/helper-invocation.md. Whenopen-tasks.mdexists, runwork.py list --limit 1to check for conflicting owners, then use the board's in-flight count if it reportsowner: legacy(top-level-bullets excluding done- [x]; the same_taskboardlibcount the SessionStart hook uses). Otherwise pagework.py list --limit 64with its returnednext_offsetandmembership_sha256, up to 256 entries total. Countqueuedandactive; excludecompleteandarchived. If the first page reports more than 256 entries, or a later page remains after the cap, report the count as unknown with the total and suggestwork.py listfor selected pages. Stop on an unavailable page, changed membership, or an unsafe store and report the count as unknown. This cap avoids repeated full-directory scans for one display count. This selected read is for the explicit status command, not a new native-engine call on every statusline or SessionStart frame. - 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.lognewer 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> implementation 3/7 complete (2 DONE, 1 historical ACCEPTED); verification unknown — resume with $ca-feature "<slug>"
<slug> spec present, 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 → ask it directly; no command needed.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |