3 · Plan
Walk the prototype back into behavior the owner can review and approve. Shape that agreement into an agent-ready card with acceptance criteria and named proof. Technical planning belongs to the selected engineering lead inside the Build workspace.
This is the return trip. Spec-driven development only runs one way: human intent down into code. Products get good on the trip back up, where humans can actually react.
The CPO skills
Section titled “The CPO skills”- cpo-breakdown — walks the prototype and shows you a diff: what it promises versus what the card asked for — added, changed, dropped. Nothing the prototype invented gets adopted silently.
- cpo-shape makes the approved behavior, dependencies, scope, and proof complete enough to grade the card agent-ready.
The checkpoint
Section titled “The checkpoint”Definition of ready. The owner approves the behavior and Shape checks the complete card contract. Dispatch separately checks prerequisites and capacity before assigning work.
Deliverables
Section titled “Deliverables”An approved product agreement and agent-ready cards with named proof.
Who participates
Section titled “Who participates”Product runs the walk and shapes the cards; the owner settles product decisions. Engineering plans and implements the approved work in Build.