Install
Three steps: install the stack, configure your repo, hire the team.
1. Install the stack
Section titled “1. Install the stack”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.
2. Configure your repo
Section titled “2. Configure your repo”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 factsdocs/agents/issue-tracker.md— your tracker’s verbs
Every skill reads these before acting. No skill hardcodes a board fact.
3. Hire the team
Section titled “3. Hire the team”Each seat is a separate install. Take the ones you need:
| Seat | Library | Install |
|---|---|---|
| Eng | mattpocock/skills | npx skills add mattpocock/skills |
| Eng | compound engineering (Every) | /plugin marketplace add EveryInc/every-marketplace then /plugin install compound-engineering |
| Research | A Smart Bear (planned for 1.1) | download from skills.asmartbear.com |
| Research | last30days | /plugin marketplace add mvanhorn/last30days-skill then /plugin install last30days@last30days-skill |
| Research | Anthropic PM plugin | claude plugin marketplace add anthropics/knowledge-work-plugins then claude plugin install product-management@knowledge-work-plugins |
| Design | Impeccable (candidate) | npx impeccable install |
| Design | Claude 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.
Check the install
Section titled “Check the install”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.