cpo-retro
Runs a retro over a window of product work: what shipped, what was tried and abandoned, where the process ground. It distills the window into proposed fixes for memory, skills, or cards — so the factory improves itself.
When to use it
Section titled “When to use it”- the end of a week or a batch
- you want to know what the team actually learned, not what it planned
What it needs
Section titled “What it needs”- a configured repo
- history to read: agent session logs, board changes, and merged work over the window
What you get
Section titled “What you get”- a short report of the window: shipped, abandoned, and stuck
- proposed fixes, each aimed at a home — a skill edit, a memory entry, or a new card
Where it sits
Section titled “Where it sits”Read-only, looking backward. It delegates history reading to the session
tooling and the tracker rather than keeping its own records. Fixes it
proposes flow back in through cpo-shape.
Say this
Section titled “Say this”cpo-retrowhat did we learn this weekhow did the week actually go