executing-plans
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint before the next batch. The checkpointed counterpart to /sprint's autonomous run.
npx skills add arbiterForge/codeArbiter --skill executing-plans --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.
# executing-plans Coordinate the plan in small, user-acknowledged batches. Routed to by `/feature` after `writing-plans` has produced a plan. Each batch is executed by `subagent-driven-development` — fresh author agent per task, spec-compliance review, quality review, fresh verification — and the user checkpoints between batches. The orchestrator never implements; it schedules and checkpoints. ## Pre-flight Read these, or STOP and surface the gap — never guess a path, a command, or a task boundary: - `{{PROJECT_DIR}}/.codearbiter/plans/<slug>.md` — the approved plan. The ordered task list and each task's verification command are the contract. No plan, no execution. - `{{PROJECT_DIR}}/.codearbiter/specs/<slug>.md` — the spec the plan implements. - `{{PROJECT_DIR}}/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `{{PROJECT_DIR}}/.codearbiter/tech-stack.md` — the exact verification, test, and build invocations. ## Phase 1 — Batch plan · gate: BLOCK Group the plan's tasks into small batches. Keep batches tight — three to five tasks is a ceiling, not a target. Respect the plan's ordering and dependencies: a task never lands before the task
- Pre-flight
- Phase 1 — Batch plan · gate: BLOCK
- Phase 2 — Execute batch · gate: BLOCK
- Phase 3 — Checkpoint · gate: STOP
- Hard rules
What does the executing-plans skill do?
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint before the next batch. The checkpointed counterpart to /sprint's autonomous run.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill executing-plans --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.