cpo-dispatch

Turns a set of agent-ready cards into worktrees that build themselves — one worktree per card, each with its own agent that owns the card end to end. It checks readiness and capacity, creates the worktree, launches the agent, confirms the brief landed, and stops.

When to use it

• one or more cards sit in the agent-ready state and you want them moving
• you name several cards and want them started at once

What it needs

• a configured repo — run cpo-setup first
• cards that have passed the readiness checklist; it re-checks and skips cards that have not
• free capacity under the configured worktree limit

What you get

• one worktree per card, each with a launched agent and a confirmed brief
• cards moved to the in-progress state

Where it sits

Between shaping and building. It never builds, reviews, or reaches into a worktree it created — the agent in the worktree runs cpo-build and owns the card from there.

Say this

cpo-dispatch
open worktrees for these tickets
dispatch the batch