cpo-dispatch
Assigns agent-ready cards under the project’s workspace and capacity policy. It creates or reuses a workspace, hands one card at a time to its lead, confirms the brief landed, and ends the launch turn. Results and human-input requests return through the named session channel.
When to use it
Section titled “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
Section titled “What it needs”- a configured repo — run
cpo-setupfirst - 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
Section titled “What you get”- project-approved workspaces, each with one active writer and a confirmed brief
- a separate branch and PR per card; the lead moves its card when work starts
Where it sits
Section titled “Where it sits”Between shaping and building. The workspace lead runs cpo-build and owns the
card from there. For pstack, the brief names /poteto-mode and its resolved
installation. Build invokes that command after readiness checks and supplies
the CPO return boundary. Dispatch launches the assignment and confirms startup.
The workspace carrier and engineering lead are separate choices. Carrier instructions load only for the configured launcher. Each receiving lead owns its environment setup; workspace creation alone does not prove setup completed.
Say this
Section titled “Say this”cpo-dispatchopen worktrees for these ticketsdispatch the batch