Head of Product
Skills from
Runs discovery and delivery as connected parts of the same product process.
Produces
- product bets and discovery briefs
- PRDs and product specs
- delivery briefs and release outcomes
CPO Stack
agent skill pack · 12 skills
The product management layer for agentic engineering.
Agents can build all day. But someone still has to do the product work: decide what is worth building, write it so both humans and agents understand it, check what was built against what was asked, and keep the record straight. CPO Stack does that job.
$
see the skillsnpx skills add jazic/cpo-stackplugs into
Claude CodeCodexGitHub IssuesLinearGitHub PRs
CPO-214 · search feels slow
>cpo-shape “search feels slow”
card CPO-214 · improvement · shaped
agent-ready ++
>cpo-dispatch CPO-214
worktree up · 4 units planned
4 units built · 4 diffs reviewed
>cpo-verify CPO-214
criteria 3/3 · 3 screenshots attached
waiting: human review
One card, start to gate. You have not typed a prompt since the first line.
Agents made building cheap. That is the part everyone noticed. The part I kept running into is that nothing else got cheaper: deciding what is worth building, writing it down so an agent can act on it, checking that what came back is what you asked for, and telling people what changed.
I was doing all of it by hand, on every project, in a chat window. Re-explaining the same context. Reading diffs to work out whether the thing actually worked. Writing release notes at midnight because nobody else was going to.
So I packaged the role instead of the tasks. cpo stack is the product manager I kept having to be. It shapes work into cards, hands each card to whichever pack is best at the craft, holds the gates, and keeps the record straight. It does not write your code. It decides what your code is for.
It is early. The front half of product — customers, strategy — is still ahead of me. If you run it on a real repo, tell me where it got in your way. That is the fastest way this gets better.
Meet the modern product org.
You keep the product decisions. Five accountable heads turn discovery, delivery, and operations into work the next team can pick up.
you, the chief product officer.
You still own strategy, priorities, and the final product call. You define the factory, set its rules, and orchestrate the agents doing the work.
cpo-strategydefine the strategycpo-setupset the factory rulescpo-dispatchorchestrate agents
Head of Research
Skills from
Turns continuous customer feedback and current market signals into reusable product evidence.
Produces
- an ideal customer profile and research plan
- a customer feedback synthesis
- a continuous learning brief
Head of Design
Skills from
Turns product specs into clear interface decisions and keeps the product visually consistent.
Produces
- a clickable prototype
- a brand and style guide
- a feature design review
Head of Engineering
Skills from
Turns approved specs into working software and keeps the codebase healthy.
Produces
- a technical plan and architecture decisions
- a tested and reviewed implementation
- a bug, refactor, and performance report
Head of Operations
Works with
Keeps the factory moving from approved work through implementation, review, and release.
Produces
- an agent-ready worktree and brief
- current status and evidence in Linear
- a GitHub pull request and release handoff
Scroll to see every head
Five phases, one loop.
Every piece of work is a card. The stack moves it around the loop; you approve at three checkpoints. Open a phase to see inside.
discover > prototype > plan > build > ship ⟲ ship feeds discover
01discover — find what is worth building; end with a brief
learncpo-retroce-sessionsmetrics-review
customer researchFind Your ICPCustomer InterviewsNeeds Stacksynthesize-research
market researchGood Market?Positioningcompetitive-brieflast30days
ideateproduct-brainstormingce-brainstorm
triagecpo-intake
strategycpo-strategyRude Q&A
briefcpo-shapecpo-brief
02prototype — the brief becomes something clickable
generateClaude DesignImpeccableprototype
review vs briefcpo-brief — the demonstration list is the rubric
03plan — the prototype becomes approved stories, then a plan
definition of ready — you approve the story diff
storiescpo-stories
technical planto-specto-ticketsce-plan
04build — reviewed units, verified before review
human review — nothing reaches you without evidence
dispatch & runcpo-dispatchcpo-build
implementtddimplementdiagnosing-bugsce-work
reviewcode-reviewce-code-review
verifycpo-verify
05ship — merge, release, tell the story
your approval merges — only your word sets the last gate
prcpo-pr
merge & releasecpo-shiporca lineargh
announce & documentcpo-announcecpo-wiki
Twelve skills, and the pages behind them.
Every skill has a reference page: what it reads, what it writes, which gate it touches, and the prompt to run it.