cpo-shape
Turns raw input into clear cards on the tracker. Shape classifies each card by its configured type and hierarchy role: standalone, initiative parent, or initiative child. Standalone cards and children use their type’s work profile. Parents use the initiative agreement. The card is the ticket. It carries the problem, acceptance criteria, and proof plan. There is no separate 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”- standalone cards with only the contract their work profile needs
- initiative parents with outcomes, responsibility boundaries, useful horizons, success measures, and child coverage
- initiative children with bounded contributions, owned scenarios, and proof
- a standalone card or child that passes its 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 work profiles, hierarchy roles, and the
readiness checklist. Parents are never dispatched. Ready children and standalone
cards 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