/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 --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/sprint
Context preview
What this command does when you run it.
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
Command definition
sprint.mddescription: 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]"
{{CMD: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 `{{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. `{{CMD: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
`{{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 → `{{CMD: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
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]"
{{CMD: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 `{{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. `{{CMD: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
`{{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 → `{{CMD: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 commands on codearbiter.
- /add-dep
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
Open command - /adr-status
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
Open command - /adr
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
Open command - /arbiter
Exit maintainer dev mode — restore orchestration, remove the dev marker, log the exit.
Open command - /audit
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
Open command - /btw
Lightweight Q&A about the project — answer from context and return, no routing, no state change.
Open command