ca-feature
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
npx skills add arbiterForge/codeArbiter --skill ca-feature --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-feature — spec-driven feature The single permitted entry to implementation work. No feature code is written before a spec is approved and `tdd` Phase 1 clears. A one-line idea is not a spec — `brainstorming` makes it one. **Orientation:** if `.codearbiter/code-map.md` is present, read it first — a coarse concern→path→role map that orients task authoring. Absent is fine; it is read-on-demand, populated by context-creation or commit-gate heal. ## Resume — an interrupted pipeline is re-entered, never restarted Before triage, scan `<project-root>/.codearbiter/specs/` and `plans/` for an existing slug matching `$ARGUMENTS` (invoked bare, list every resumable pipeline and ask which). A crash, compaction, or closed session mid-pipeline loses nothing — the spec, the plan, and each task's `status` cell are on disk. On a match, confirm the resume with the user in one line ("resume `<slug>` at <point>?") and re-enter at the furthest checkpoint reached: 1. **Plan exists with non-`ACCEPTED` tasks** → `executing-plans` (its Phase 1 batches only the remaining tasks). 2. **Plan exists, every task `ACCEPTED`** → `commit-gate` (the work is done and verified; it was the commit that never happen
- Resume — an interrupted pipeline is re-entered, never restarted
- Step 0 — change-class triage (logged)
- Flow — full lane
- Scope routing
- When NOT to use
- Hard gate
What does the ca-feature skill do?
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-feature --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.