/ca-sprint
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-sprint --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ca-sprint
Context preview
The summary Claude sees to decide when to auto-load this skill.
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
SKILL.md
ca-sprint.SKILL.mdname: ca-sprint
description: Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
argument-hint: "[goal] [--farm]"
$ca-sprint — autonomous sprint
The autonomy mode. Brainstorm a sprint spec with the user — the one interactive gate — then execute the approved plan end-to-end without per-batch checkpoints, deciding "as the user" via SMARTS on every non-hard-gate point. Every auto-decision lands in `.codearbiter/sprint-log.md` (append-only) with a confidence flag; the `low`-confidence entries are exactly what the user reviews afterward. Nothing is hidden behind autonomy.
Flow
Load and follow `${CLAUDE_PLUGIN_ROOT}/SPRINT.md` — it is the procedure. In brief:
1. **Sprint spec (STOP)** — `brainstorming` scoped to a sprint, then `writing-plans`. Explicit user approval of spec AND plan before autonomy begins. 2. **Autonomous execution (BLOCK)** — `subagent-driven-development` runs the plan; test-first via `tdd`, two-pass reviewed, fresh-run verified. SMARTS decides non-hard-gate points; everything logs. 3. **Land & summarize (BLOCK)** — `commit-gate`, then `finishing-a-development-branch`, which auto-selects open-PR. `$ca-sprint` never merges and never discards; the merge decision is the user's.
Hard gates — `security-controls`, crypto/secrets/auth, irreversible ops, `/override`, an unresolvable `[CONFIRM-NN]`, merge-to-default — are NEVER auto-decided. They halt and surface.
Arguments
- **`"goal"`** — seed for the sprint-spec brainstorm.
- **`--farm`** — cost-arbitrage backend: cheap workers implement under the same gates; Claude still
authors spec, failing tests, plan, and reviews everything. Pre-flights `FARM_API_KEY`.
Routes to
`${CLAUDE_PLUGIN_ROOT}/SPRINT.md` (mode body), which routes through `brainstorming`, `writing-plans`, `subagent-driven-development`, `commit-gate`, `finishing-a-development-branch`.
When NOT to use
- A single feature with human checkpoints → `$ca-feature`.
- Work whose spec cannot be made concrete up front — the one interactive gate is load-bearing;
a thin spec makes hard-gate stops frequent instead of rare.
Read more
name: ca-sprint description: Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops. argument-hint: "[goal] [--farm]"
$ca-sprint — autonomous sprint
The autonomy mode. Brainstorm a sprint spec with the user — the one interactive gate — then execute the approved plan end-to-end without per-batch checkpoints, deciding "as the user" via SMARTS on every non-hard-gate point. Every auto-decision lands in `.codearbiter/sprint-log.md` (append-only) with a confidence flag; the `low`-confidence entries are exactly what the user reviews afterward. Nothing is hidden behind autonomy.
Flow
Load and follow `${CLAUDE_PLUGIN_ROOT}/SPRINT.md` — it is the procedure. In brief:
1. **Sprint spec (STOP)** — `brainstorming` scoped to a sprint, then `writing-plans`. Explicit user approval of spec AND plan before autonomy begins. 2. **Autonomous execution (BLOCK)** — `subagent-driven-development` runs the plan; test-first via `tdd`, two-pass reviewed, fresh-run verified. SMARTS decides non-hard-gate points; everything logs. 3. **Land & summarize (BLOCK)** — `commit-gate`, then `finishing-a-development-branch`, which auto-selects open-PR. `$ca-sprint` never merges and never discards; the merge decision is the user's.
Hard gates — `security-controls`, crypto/secrets/auth, irreversible ops, `/override`, an unresolvable `[CONFIRM-NN]`, merge-to-default — are NEVER auto-decided. They halt and surface.
Arguments
- **`"goal"`** — seed for the sprint-spec brainstorm.
- **`--farm`** — cost-arbitrage backend: cheap workers implement under the same gates; Claude still
authors spec, failing tests, plan, and reviews everything. Pre-flights `FARM_API_KEY`.
Routes to
`${CLAUDE_PLUGIN_ROOT}/SPRINT.md` (mode body), which routes through `brainstorming`, `writing-plans`, `subagent-driven-development`, `commit-gate`, `finishing-a-development-branch`.
When NOT to use
- A single feature with human checkpoints → `$ca-feature`.
- Work whose spec cannot be made concrete up front — the one interactive gate is load-bearing;
a thin spec makes hard-gate stops frequent instead of rare.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
Other skills on codearbiter.
- /brainstorming
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No
Open skill - /commit-gate
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message,
Open skill - /context-check
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Open skill - /context-creation
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase
Open skill - /crypto-compliance
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive
Open skill - /debug
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a known bug). Five gated phases: capture, hypothesize, gather, decide, hand off. Investigation only, no code changes; exits to /fix, /adr, or a no-action close.
Open skill