subagent-driven-development
The implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.
npx skills add arbiterForge/codeArbiter --skill subagent-driven-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# subagent-driven-development One task, one fresh subagent, two reviews, proof on a fresh run. Routed to by `/sprint` (full plan, autonomous) and by `executing-plans` (one batch at a time, with human checkpoints between batches). The loop processes tasks in dependency order and never trusts a self-report. ## Pre-flight Read these, or STOP and surface the gap — never guess scope, command, or obligation: - `{{PROJECT_DIR}}/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `{{PROJECT_DIR}}/.codearbiter/plans/<slug>.md` — the approved plan. Each task carries an exact path set and a verification command. This is the task source. - `{{PROJECT_DIR}}/.codearbiter/specs/<slug>.md` — the approved spec. Each task's obligation traces to it. The spec-compliance review measures against it. - `{{PROJECT_DIR}}/.codearbiter/tech-stack.md` — build, test, and verification invocations; file layout; the scope-to-author mapping. - `{{PROJECT_DIR}}/.codearbiter/security-controls.md` — only when a task touches a security boundary (auth, crypto, secrets, a trust boundary). **Optional `scope` parameter:** when invoked by `executing-plans`, a list of task IDs is
- Pre-flight
- Phase 1 — Task selection · gate: BLOCK
- Phase 2 — Implementation dispatch · gate: BLOCK
- Phase 3 — Spec-compliance review · gate: BLOCK
- Phase 4 — Quality review (once per scope) · gate: BLOCK
- Phase 5 — Verification · gate: BLOCK
- Phase 6 — Accept and advance · gate: BLOCK
- Hard rules
What does the subagent-driven-development skill do?
The implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill subagent-driven-development --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.