EveryInc/compound-engineering-pluginPublic

Compound Engineering

AI skills that make each unit of engineering work easier than the last.

Compound Engineering is a plugin of 36 skills for AI coding agents. It structures the work around a loop — brainstorm, plan, build, review, then capture what you learned — so the knowledge from each change is written down where the next change can read it.

It runs on 14 agent hosts, including Claude Code, Cursor, and Codex.

Maintained by Kieran Klaassen and Trevin Chow, with contributions from the open-source community.

For understanding before a change, ask ce-explain how the relevant behavior works and why it exists. For a recommendation, use ce-pov; “oracle this” adds independent model opinions. Both can contribute to another workflow without a separate human interaction.

/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering

In Cursor Agent chat, install from the plugin marketplace:

/add-plugin compound-engineering

Or search for "compound engineering" in the plugin marketplace.

Grok Bot is its own app, but it uses your Cursor account and plugin library. There is no separate Grok Bot login. Install Compound Engineering once on that account and Grok Bot agents can load it.

In Cursor Agent chat:

/add-plugin compound-engineering

Or search for "compound engineering" in the Cursor plugin marketplace. Do not run /add-plugin in the Grok Bot chat, and do not clone this repository onto the Grok Bot computer.

Compound Engineering is not listed in Codex's built-in plugin marketplace yet. Add it as a custom marketplace:

1. In the Codex app, open Plugins from the sidebar.

2. Click the arrow next to Create, then select Add marketplace.

3. Enter:

   Field	Value
   Source	EveryInc/compound-engineering-plugin
   Git ref	main
   Sparse paths	leave blank

4. Click Add marketplace.

5. Search for Compound Engineering, install compound-engineering-plugin, then restart Codex.

The Codex app install is self-contained for Compound Engineering. Specialist reviewer and research behavior lives inside the skills as local prompt assets; no separate custom-agent install step is required.

Register the marketplace, then install the plugin.

1. Register the marketplace with Codex:

   codex plugin marketplace add EveryInc/compound-engineering-plugin

2. Install the plugin:

   codex plugin add compound-engineering@compound-engineering-plugin

   You can also launch codex, run /plugins, find the Compound Engineering marketplace, select the compound-engineering plugin, and choose Install. Restart Codex after install completes.

The native Codex plugin install is self-contained for Compound Engineering. Specialist reviewer and research behavior lives inside the skills as local prompt assets; no separate custom-agent install step is required.

For a non-default Codex profile, run every Codex-related step against the same CODEX_HOME. This example installs CE into a work profile:

CODEX_HOME="$HOME/.codex/profiles/work" codex plugin marketplace add EveryInc/compound-engineering-plugin
CODEX_HOME="$HOME/.codex/profiles/work" codex plugin add compound-engineering@compound-engineering-plugin

The marketplace step only makes the plugin available; the plugin install is what activates the native CE skills for that profile.

Another editor or CLI? Kimi Code CLI, Cline, Grok Build CLI, Devin CLI, GitHub Copilot, Factory Droid, Qwen Code, OpenCode, Pi, oh-my-pi (omp), and Antigravity CLI are all supported — see More install options.

Each unit of engineering work should make subsequent units easier -- not harder.

Invocation syntax: this README uses /skill-name examples for slash-skill hosts. In Codex, invoke installed skills with $skill-name (for example, $ce-plan and $lfg). In oh-my-pi (omp), these prompts can model-route to visible skills; use the native deterministic /skill:<name> form for manual-only or hidden skills (for example, /skill:ce-polish). /goal remains a Codex built-in command.

Traditional development accumulates technical debt. Every feature adds complexity. Every bug fix leaves behind a little more local knowledge that someone has to rediscover later. The codebase gets larger, the context gets harder to hold, and the next change becomes slower.

Compound engineering inverts this. 80% is in planning and review, 20% is in execution:

• Plan thoroughly before writing code with /ce-brainstorm and /ce-plan using one plan artifact that grows from requirements into implementation planning
• Review to catch issues and calibrate judgment with /ce-code-review and /ce-doc-review
• Codify knowledge so it is reusable with /ce-compound
• Keep quality high so future changes are easy

The point is leverage, not ceremony. A good brainstorm makes the plan sharper. A good plan makes execution smaller. A good review catches the pattern, not just the bug. A good compound note means the next agent does not have to learn the same lesson from scratch.

The core loop is six steps: brainstorm the requirements, plan the implementation, work through the plan, simplify what you wrote, review the result, then compound the learning -- and repeat with better context.

Each cycle compounds. /ce-compound writes learnings that the next /ce-brainstorm and /ce-plan read as grounding. Brainstorms sharpen plans, plans inform future plans, reviews catch more issues, patterns get documented. That return arrow is the whole point.

Run one teaches it. Run two remembers.

_{Replayed from a real pair of sessions 18 days apart, with names and paths anonymized and the six-minute run compressed to about 30 seconds. Nothing shown is behavior the skills don't have — see assets/demo for the source and the substitutions.}

Artifact folders like docs/solutions/ and docs/plans/ are the defaults. A project whose docs/ is tracked content can relocate every CE artifact folder under one repo-relative root via the docs_root setting -- see configuration.

Want the same knowledge compounding across every repo in your org -- team conventions, security policies, a stack's hard-won rules -- instead of being relearned in each one? Declare it as Compound Packs: folders of prescriptive rules (local, or ref-pinned git repos) that planning grounds in and review enforces, every use cited back to the rule file (experimental) -- see Compound Packs.

After installing, run /ce-setup in any project. It reports optional tool capabilities, creates repo .compound-engineering/config.yaml when missing, refreshes the committed example, and gitignores an existing local override.

The standard loop -- turn a rough idea into shipped, reviewed code:

/ce-brainstorm make background job retries safer
/ce-plan
/ce-work
/ce-simplify-code
/ce-code-review
/ce-compound

Autonomous -- hand off a feature and let the agent run the whole pipeline:

/ce-brainstorm describe the feature
/lfg

/lfg runs the loop hands-off: it picks the route to a verified work source (a plan, or a ce-debug fix for a bug report), works through it, simplifies, runs code review and applies the fixes, captures any durable learning, runs browser tests, then commits. When a git remote exists it pushes, opens a PR, and watches CI with a bounded repair loop (it does not merge unless you grant that, and it can finish with leftovers if the repair budget is hit). With no remote it stops at local commits. Start it after /ce-brainstorm so it plans against real requirements rather than a one-line prompt.

Starting from a bug instead of a feature? Use /ce-debug. Not sure what to build yet? Start with /ce-ideate.

36 skills, grouped by what they are for. The full catalog, with a page per skill and how each one chains into the others, is in docs/guides.

Learn more

• Skill documentation catalog
• Compound engineering: how Every codes with agents
• The story behind compounding engineering

Claude Code, Cursor, and Codex are at the top. Everything here is equally supported.

Kimi Code CLI can install Compound Engineering directly from this repository because the repo ships a native .kimi-plugin/plugin.json manifest:

/plugins install https://github.com/EveryInc/compound-engineering-plugin

You can also browse it through Kimi's custom marketplace flow:

/plugins marketplace https://raw.githubusercontent.com/EveryInc/compound-engineering-plugin/main/.kimi-plugin/marketplace.json

After installing or updating, run /reload or start a new Kimi session so the plugin skills are loaded.

Cline loads CE skills from on-demand SKILL.md directories. Enable Settings -> Features -> Enable Skills in the Cline extension, then link this repository's skills globally or per project:

git clone https://github.com/EveryInc/compound-engineering-plugin
./compound-engineering-plugin/.cline/scripts/install-skills.sh --global

Per-project install from a checkout:

./compound-engineering-plugin/.cline/scripts/install-skills.sh --project

Start a new Cline task after installing or updating skills. See .cline/INSTALL.md for pinning, local development, and uninstall steps.

xAI's Grok Build CLI (grok) installs Compound Engineering directly from this repository. The repo root is a valid Grok plugin: grok reads the existing Claude-compatible manifests, and the repo also ships a native .grok-plugin/plugin.json.

grok plugin install EveryInc/compound-engineering-plugin

This tracks the repository; run grok plugin update to pull the latest. To browse it as a marketplace source instead, the repo ships a native .grok-plugin/marketplace.json:

grok plugin marketplace add EveryInc/compound-engineering-plugin
grok plugin install compound-engineering

Both paths track the repository directly (no commit pin). Add --trust to skip the install confirmation. grok stores config under ~/.grok; start a new session after installing so the skills load.

Compound Engineering is also being submitted to the official xAI plugin marketplace; see docs/grok-marketplace-submission.md for the maintainer runbook.

Devin CLI can install Compound Engineering directly from GitHub because the repo ships a native .devin-plugin/plugin.json manifest:

devin plugins install EveryInc/compound-engineering-plugin

Verify the install and inspect the skills:

devin plugins list
devin plugins info compound-engineering

Update to the latest version with devin plugins update compound-engineering. Plugins load at session start, so start a new Devin session after installing or updating for the skills to appear (as /compound-engineering:<skill> slash commands).

A few skills declare Claude-style allowed-tools names that Devin does not map (for example Bash); those skills still work, but some of their actions ask for permission instead of running auto-approved. See docs/specs/devin.md for details.

For VS Code Copilot Agent Plugins:

1. Run Chat: Install Plugin from Source from the VS Code command palette
2. Use EveryInc/compound-engineering-plugin for the repo
3. Select compound-engineering when VS Code shows the plugins in this repository

For Copilot CLI, use:

Inside Copilot CLI:

/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering@compound-engineering-plugin

From a shell with the copilot binary:

copilot plugin marketplace add EveryInc/compound-engineering-plugin
copilot plugin install compound-engineering@compound-engineering-plugin

Copilot CLI reads the existing Claude-compatible plugin manifests directly.

From a shell with the droid binary:

droid plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin
droid plugin install compound-engineering@compound-engineering-plugin

Droid uses plugin@marketplace plugin IDs; here compound-engineering is the plugin and compound-engineering-plugin is the marketplace name. Droid installs the existing Claude Code-compatible plugin and translates the format automatically.

qwen extensions install EveryInc/compound-engineering-plugin:compound-engineering

Qwen Code installs Claude Code-compatible plugins directly from GitHub and converts the plugin format during install.

Add Compound Engineering to the plugins array in your global or project opencode.json:

{
  "plugins": ["compound-engineering@git+https://github.com/EveryInc/compound-engineering-plugin.git"]
}

On OpenCode 1.x, the config key is plugin (singular). Restart OpenCode after changing the config. The plugin registers the Compound Engineering skills and /commands directly; no Bun installer or generated skill copy is required. See .opencode/INSTALL.md for pinning examples.

Install Compound Engineering as a Pi package from this repository:

pi install git:github.com/EveryInc/compound-engineering-plugin

Required companion for CE workflows that dispatch reviewer, research, or implementation subagents:

pi install npm:pi-subagents

Recommended companion for richer blocking questions:

pi install npm:pi-ask-user

oh-my-pi (omp) installs Compound Engineering through its marketplace flow. The repo ships a native .omp-plugin/marketplace.json catalog whose plugin entry carries a release-managed version, so omp's update checker can see each new CE release:

omp plugin marketplace add EveryInc/compound-engineering-plugin
omp plugin install compound-engineering@compound-engineering-plugin

To stay current automatically, enable auto-update:

omp config set marketplace.autoUpdate auto

The default notify mode only writes update availability to the debug log — it does not prompt — so without auto you will not hear about new releases. To upgrade by hand instead, run omp plugin upgrade compound-engineering@compound-engineering-plugin.

omp plugin link "$PWD"

Run /reload-plugins or start a new omp session after installing so the skills load. omp's native deterministic command is /skill:<name> (for example, /skill:ce-plan); ordinary /skill-name prompts can also model-route to visible skills, but manual-only or hidden skills require the native form. See docs/specs/omp.md for details.

Google has replaced the consumer Gemini CLI with Antigravity CLI (agy), which still runs on Gemini models. Install Compound Engineering directly from GitHub — no clone step required:

agy plugin install https://github.com/EveryInc/compound-engineering-plugin

Verify with agy plugin list. The repository root is the plugin package (plugin.json plus skills/).

For a local checkout or pinned release:

git clone https://github.com/EveryInc/compound-engineering-plugin
agy plugin install ./compound-engineering-plugin

The bundled .agy/ directory remains a compatibility entry point (agy plugin install ./compound-engineering-plugin/.agy). agy also loads GEMINI.md workspace context from the checkout.

See .agy/INSTALL.md for pinning, local development, uninstall, and legacy Gemini import.

Compound Engineering moved to a root-native, skills-only layout. If you installed before that move, refresh the cached marketplace before updating the plugin — order matters, and /plugin update alone keeps you on the old version.

See docs/install/upgrading.md for the per-host refresh commands, and for removing the obsolete Codex tool-map block left behind by pre-native Bun installs.

OpenCode, Pi, and oh-my-pi (omp) use native package/plugin loading from this repository. The Bun CLI remains for repository development and converter maintenance, not normal installation.

Release versions are owned by release automation. Routine feature PRs should not hand-bump plugin or marketplace manifest versions.

No. Bun is only needed for repo development tasks and converter maintenance.

The grouped overview is above; the full catalog with a page per skill is docs/guides/README.md. Each skill's authoritative runtime spec lives in skills/<skill>/SKILL.md.

GitHub Releases are the canonical release-notes surface. The root CHANGELOG.md points to that history.

See CONTRIBUTING.md for setup, and docs/development.md for loading a local checkout into each harness.

Contributions are welcome. Issues, bug reports, and pull requests all help make this better, and we genuinely appreciate them — bug reports especially. Start with CONTRIBUTING.md, which covers setup and what to do before opening a PR.

A note on what to expect: Compound Engineering is opinionated by design. It's maintained by @kieranklaassen and @tmchow, and its direction reflects a specific point of view about how AI-assisted engineering should work. So while we welcome help, we can't promise to accept every change — some proposals won't fit that vision even when they're good ideas on their own.

Open an issue or send a PR, and we'll fold in what moves the plugin in the right direction. We just want to be upfront that not everything will land.

MIT