cpo-shape
Turns raw input into one clear card on the tracker, written to the template for its card type. The card is the ticket — it carries the problem, the acceptance criteria, and the proof plan. There is no spec file.
When to use it
Section titled “When to use it”- an idea, bug report, mockup, or research question needs to become work
- a pile of loose inputs needs triage into cards
- an existing card needs review before it can reach the agent-ready state
What it needs
Section titled “What it needs”- a configured repo — run
cpo-setupfirst - you, for real product decisions only; everything else it decides from the templates and the readiness checklist
What you get
Section titled “What you get”- one card per piece of work, written in user terms in the
cpo-writeregister, with acceptance criteria and a proof plan - a card that passes its type’s readiness checklist moves to the agent-ready state — the first gate
Where it sits
Section titled “Where it sits”The front of the lifecycle. It owns the card-type templates and the
readiness checklist. Cards it marks agent-ready are what cpo-dispatch
picks up.
Say this
Section titled “Say this”cpo-shape: users want to export their data as CSVshape this bugtriage the pile