A plugin that tries to make codebases cheaper over time

What it does

Compound Engineering is a plugin for Claude Code, Cursor, Codex, Copilot, and several other AI coding tools. It replaces the typical “prompt and pray” loop with a structured workflow: brainstorm requirements, plan implementation, execute, review, and document learnings so the next cycle starts with better context. The plugin ships 37 skills and 51 agents, accessed via slash commands like /ce-brainstorm, /ce-plan, /ce-work, and /ce-compound.

The interesting bit

The core bet is that most engineering value comes from upfront work, not typing speed. The plugin enforces an 80/20 split — 80% planning and review, 20% execution — and persists strategy, requirements, and post-mortems as durable artifacts (STRATEGY.md, docs/pulse-reports/, compounded notes). The theory: a codebase should get cheaper to change as it grows, not more expensive. Whether that theory survives contact with real deadlines is the open question.

Key highlights

• /ce-strategy anchors all downstream work to a durable product brief that ideation, brainstorming, and planning all read automatically
• /ce-product-pulse generates time-windowed reports on usage, errors, and performance, creating a browsable timeline of user outcomes
• Multi-agent code review (/ce-code-review) runs before merge, not as an afterthought
• Supports Claude Code, Cursor, Codex, GitHub Copilot, Qwen Code, Factory Droid, OpenCode, Pi, Gemini CLI, and Kiro CLI — though installation complexity varies sharply by platform
• Codex currently requires a three-step install including a Bun-based agent workaround; the README notes this should simplify once Codex’s plugin spec matures

Caveats

• Installation is genuinely uneven: some editors need one command, others need three steps with environment-variable juggling for non-default profiles
• Pi requires a separate third-party subagent plugin (nicobailon/pi-subagents) to function at all
• The “37 skills and 51 agents” claim is stated but not enumerated in the README; the full inventory lives in a separate component reference file

Verdict

Worth evaluating if your team already uses AI coding tools and you’re watching context decay erode velocity. Probably overkill if you’re not willing to trade immediate output for documentation discipline — the plugin assumes you’ll actually read and maintain STRATEGY.md between sprints.