Compound Engineering
Official Compound Engineering 3 from Every, installed through the upstream Pi target.
What LazyPi installs
LazyPi uses the upstream @every-env/compound-plugin Bun CLI directly. When you install compound, LazyPi runs the upstream cleanup step first and then installs the official Pi target output into your Pi directory.
LazyPi also auto-installs the two runtime dependencies Compound Engineering expects: pi-subagents and pi-ask-user. That means npx @robzolkos/lazypi --only compound is enough to get a working CE 3 setup.
Bun requirement
The official installer is Bun-based. If bun is missing, LazyPi warns and skips Compound Engineering while continuing with the rest of the catalog.
Installed layout
CE 3 is treated as upstream output, not a LazyPi-managed compatibility fork. After install, the canonical files live under your Pi root:
.pi/skills/— Compound Engineering skills.pi/agents/— Compound Engineering agents.pi/compound-engineering/install-manifest.json— upstream install manifest
LazyPi uses that upstream manifest as the source of truth for detection, updates, health checks, and removal.
Updates and migration
npx @robzolkos/lazypi update refreshes Compound Engineering by running upstream cleanup and upstream install again. If LazyPi detects an older pre-CE-3 install, it migrates in place and removes the old LazyPi state file after the CE 3 manifest is present.
Removal
npx @robzolkos/lazypi remove compound removes the files listed in the upstream manifest, clears legacy LazyPi state, and deletes the upstream backup directory under .pi/compound-engineering/legacy-backup/.
What shows up in Pi
The install brings in the official Compound Engineering workflow skills plus the supporting specialists those workflows rely on.
| Skill | What it does |
|---|---|
/skill:ce-brainstorm | Explore requirements and options before committing to a build |
/skill:ce-plan | Create structured implementation plans |
/skill:ce-work | Execute implementation work against a plan |
/skill:ce-review | Run multi-agent review before shipping |
/skill:ce-debug | Investigate bugs and root causes systematically |
/skill:ce-compound | Capture reusable learnings from solved problems |
/skill:ce-compound-refresh | Refresh stale learnings under docs/solutions/ |
The exact inventory can evolve with upstream Compound Engineering releases, but LazyPi no longer renames skills, rewrites generated files, or ships a compatibility layer on top of the upstream Pi output.