cpo-build

Hands one ready card to the selected engineering lead. With pstack selected, Build invokes /poteto-mode with the bounded card assignment. The mode selects its playbook and owns planning, worker dispatch, implementation, and code review. CPO checks readiness, verifies acceptance independently, and owns the PR gates.

When to use it

• a ready card needs implementation or an existing build needs to resume
• an agent in a dispatched worktree picks up its card

What it needs

• a configured repo with an engineering lead and workspace instructions
• a card that says what to build and how to prove it

What you get

• the change, built and independently reviewed in its assigned workspace
• acceptance evidence from cpo-verify before human review

Build order

1. Build with focused checks and targeted runtime feedback.
2. Run independent engineering review and resolve its findings.
3. Pass the configured full validation.
4. Run independent acceptance verification against the card.
5. Apply the PR contract and stop at human review.

Verification defects return to the lead for fixes and review before affected checks run again. Earlier checks can diagnose problems while building; the full acceptance pass follows engineering review.

Where it sits

Between shaping and human review. The engineering lead supervises workers; CPO resolves product decisions and checks the returned work against the card. Only the owner authorizes the merge gate.

Pstack returns reviewed implementation before its own PR or shipping steps. Build then completes CPO acceptance and PR preparation. An already active mode continues the assignment without starting another lead or another Build cycle. /setup-pstack configures models during setup, not on every build.

Say this

/cpo-build ABC-###
resume implementation of ABC-###