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.

Setup discovers existing providers and installs the selections you authorize. Choose one engineering lead in runtime.engineering_lead. Pstack uses /poteto-mode; CE uses its own engineering workflow. Other engineering skills are optional companions.

SeatLibraryInstall
Engineering leadpstackOn Cursor, /add-plugin pstack, then /setup-pstack. Other hosts use a working provider installation or adapter. See the pstack README.
Alternative engineering leadCompound EngineeringUse its documented installer for the active host and approved scope.
Optional companionsmattpocock/skillsnpx skills add mattpocock/skills
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

Pstack commands must resolve from the same selected installation. Setup verifies that the active host loads its model configuration. A Cursor rule does not establish that another host consumes it. Optional seats can remain empty; missing requirements of the selected engineering lead hold engineering readiness.

Run cpo-standup to check tracker connectivity. That does not prove engineering readiness. Setup separately checks provider discovery, required dependencies, model access, and a bounded read-only smoke task. It records the evidence and remaining gaps in FACTORY.md.