cpo-breakdown

Walks the finished prototype and records what the user can do and what the system promises. It compares that behavior with the brief and existing card, then presents additions, contradictions, and dropped promises for owner approval.

When to use it

• a prototype is ready to become an agreed product contract
• an existing card needs to catch up with approved prototype behavior

What it needs

• access to the prototype and its relevant screens and states
• the brief, existing card, and recorded product decisions

What you get

• a behavior inventory and proposed reconciliation with the existing agreement
• unresolved decisions and unverified behavior called out explicitly
• an approved payload for cpo-shape

Breakdown approval does not make a card agent-ready by itself. Shape completes the card’s behavior, proof, and dependency requirements before grading readiness. The selected engineering lead plans implementation later in the Build workspace.

Say this

/cpo-breakdown <prototype and card>