Skip to content

Install

Three steps: install the stack, configure your repo, hire the team.

Terminal window
npx skills add <cpo-stack repo>

This installs the CPO skills — the layer that runs the loop. It does not install the team; that comes in step 3.

Run cpo-setup in your repo. It asks you the real decisions — tracker (Linear or GitHub Issues), board states, owner, verify commands — and writes:

  • .cpo-stack/config.yaml — your board facts
  • docs/agents/issue-tracker.md — your tracker’s verbs

Every skill reads these before acting. No skill hardcodes a board fact.

Each seat is a separate install. Take the ones you need:

SeatLibraryInstall
Engmattpocock/skillsnpx skills add mattpocock/skills
Engcompound engineering (Every)/plugin marketplace add EveryInc/every-marketplace then /plugin install compound-engineering
ResearchA Smart Bear (planned for 1.1)download from skills.asmartbear.com
Researchlast30days/plugin marketplace add mvanhorn/last30days-skill then /plugin install last30days@last30days-skill
ResearchAnthropic PM pluginclaude plugin marketplace add anthropics/knowledge-work-plugins then claude plugin install product-management@knowledge-work-plugins
DesignImpeccable (candidate)npx impeccable install
DesignClaude Design (candidate)built into Claude Code — /design

The stack works without a full roster — each skill says what it delegates, and degrades honestly when a seat is empty.

Run cpo-standup. If it reads your board and reports it back, the stack is wired. If it tells you to run cpo-setup, a config value is missing.