Skip to content
CPO Stack

cpo-verify

Verifies a change by driving the running product against the card’s acceptance criteria — through the repo’s harness when it has one, else by browser automation — and attaches the evidence to the ticket.

When to use it

Section titled “When to use it”
  • a card’s build is done and needs proof before human review
  • you want to see a change working, not just passing tests

What it needs

Section titled “What it needs”
  • a configured repo; the verify commands come from config
  • a card with acceptance criteria to verify against
  • a runnable product, or a browser to drive it in

What you get

Section titled “What you get”
  • a pass or fail against each acceptance criterion
  • evidence — screenshots or recordings — attached to the card, best-effort

Where it sits

Section titled “Where it sits”

The gatekeeper before human review. No card moves to the human-review state without it. cpo-build calls it for UI units as they land; cpo-pr expects its evidence when opening the PR.

Say this

Section titled “Say this”
verify this
check it works
show me it working