Compound Engineering: Orchestrate Claude Code, Codex
Compound Engineering (20K stars) is a multi-agent plugin for Claude Code, Codex, and Cursor. 9 commands for brainstorm, plan, review, debug, and compound learnings. 80% planning, 20% execution workflow.
- ⭐ 22777
- Updated 2026-06-13
Compound Engineering (20,000+ stars) is a multi-agent orchestration plugin that coordinates AI coding agents (Claude Code, Codex, Cursor) through a structured planning-review-compound loop. Its philosophy is simple: plan thoroughly before writing code, review meticulously, and document learnings so future work gets easier.
What Is Compound Engineering? #
Compound Engineering is a collection of 9 specialized commands that turn your AI coding agent from a simple code generator into a disciplined engineering partner. Each command targets a specific phase of the development lifecycle:
Traditional Development:
Idea → Code → Fix Bugs → Repeat (tech debt accumulates)
Compound Engineering:
Strategy → Ideate → Brainstorm → Plan → Work → Review → Compound → Repeat (tech debt decreases)
The core insight is that 80% of engineering value comes from planning and review, not execution. Traditional AI coding tools skip straight to writing code, which produces quick results that accumulate technical debt. Compound Engineering forces the agent to think before it types.
The plugin works across multiple AI coding tools:
- Claude Code: Installs via the marketplace (
/plugin marketplace add EveryInc/compound-engineering-plugin) - Cursor: Installs via the plugin marketplace (
/add-plugin compound-engineering) - Codex: Three-step setup with marketplace registration, agent installation, and plugin enablement
Each agent shares the same command set and knowledge base, so switching between tools doesn’t lose context. For scalable multi-agent deployment, HTStack provides infrastructure supporting multiple agent instances.
Each command targets a specific phase of the development lifecycle:
The project is built on a single principle: each unit of engineering work should make subsequent units easier, not harder.
Traditional development accumulates technical debt — every feature adds complexity, every bug fix leaves behind local knowledge that future developers must rediscover. The codebase gets larger, the context gets harder to hold, and the next change becomes slower.
Compound Engineering inverts this:
| Phase | Command | Purpose | |
| Phase | Command | Purpose |
|---|---|---|
| Strategy | /strategy | High-level approach alignment |
| Ideation | /ideate | Generate multiple solution angles |
| Brainstorm | /brainstorm | Deep exploration of the chosen angle |
| Planning | /plan | Step-by-step implementation plan |
| Work | /work | Execute the plan with the agent |
| Review | /review | Critical self-review of the work |
| Debug | /debug | Systematic root-cause debugging |
| Compound | /compound | Document learnings into the knowledge base |
| Archive | /archive | Store decisions and rationale |
The Compound Loop #
The key differentiator is the compound phase. After each task, the plugin writes what was learned — architecture decisions, pitfalls, patterns — into a persistent knowledge base. The next task starts with that context, so the agent gets smarter over time instead of starting from zero each session.
Best Practices #
- Plan before coding: the
/plancommand is not optional — skip it and you’re back to traditional mode - Review everything:
/reviewcatches what the agent’s first pass missed - Compound every session: even a one-line learning compounds across dozens of sessions
- Use one command set: the same 9 commands across Claude Code, Codex, and Cursor keeps context portable
Conclusion #
Compound Engineering turns AI coding from an execution tool into a disciplined engineering process. The planning-review-compound loop is a genuine answer to the “AI writes code fast but the codebase gets worse” problem. For teams that want their AI agents to leave the codebase better than they found it, this plugin is the most complete implementation available in 2026.
💬 Discussion