cpo-build

Executes a build plan through the configured runtime. The planner frames units, the worker implements each one, and every diff is reviewed against the spec before the next unit starts. UI units are browser-verified as they land.

When to use it

• a planned feature is ready to build
• an agent in a dispatched worktree picks up its card

What it needs

• a configured repo — the runtime (planner, worker, carrier) comes from config, not from the skill
• a card or plan that says what to build and how to prove it

What you get

• the change, built in reviewed units on the card’s branch
• UI work verified in the browser through cpo-verify as it lands

Where it sits

The middle of the lifecycle. It delegates implementation craft to the engineering skills (test-driven development, code review) rather than owning it. In solo mode the session itself is the worker. When the build is done, cpo-verify and cpo-pr take the card to human review.

Say this

cpo-build
build this plan
run the plan