Ca Sprint Skill for Claude
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/arbiterForge/codeArbiter --skill ca-sprintThe instruction itself
5 sections, as written by the author/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 <plugin-root>/SPRINT.md — it is the procedure. In brief:
- Sprint spec (STOP) —
brainstormingscoped to a sprint, thenwriting-plans. Explicit user
approval of spec AND plan before autonomy begins.
- Autonomous execution (BLOCK) —
subagent-driven-developmentruns the plan; test-first via
tdd, two-pass reviewed, fresh-run verified. SMARTS decides non-hard-gate points; everything logs.
- Land & summarize (BLOCK) —
commit-gate, thenfinishing-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
<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.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take arbiterforge/codearbiter-ca-sprint from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.