EveryInc/compound-engineering-plugin: Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more

Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more - EveryInc/compound-engineering-plugin

Summary

The Compound Engineering plugin is a set of 36 slash-style skills for AI coding agents that enforce a six-step loop: brainstorm, plan, work, simplify, review, and compound. It runs on 14 agent hosts, including Claude Code, Cursor, and Codex, and stores plans, review reports, and learnings in the repo so knowledge carries from one iteration to the next. The project is MIT-licensed and written in TypeScript.

What it is useful for

This is for engineers who want AI-assisted sessions to leave behind more than diffs. Each loop writes durable artifacts to disk: /ce-plan produces implementation-ready plans in docs/plans/, /ce-code-review produces a report-only multi-agent review against that plan, and /ce-compound writes learnings into docs/solutions/ that the next /ce-brainstorm or /ce-plan reads as grounding. The README frames that return arrow as "Run one teaches it. Run two remembers."

For teams, Compound Packs (marked experimental) let you declare folders of prescriptive rules — security policies, stack-specific gotchas — that planning grounds in and review enforces, with citations back to the rule source.

For hands-off work, the autonomous pipeline /lfg runs the whole sequence after a brainstorm: it picks a verified work source, works through it, applies fixes, runs browser tests, then commits. With a git remote it pushes, opens a PR, and watches CI with a bounded repair loop; the README notes it will not merge unless you explicitly grant that, and it may stop with leftovers if the repair budget runs out.

Documented limitations: OpenCode, Pi, and oh-my-pi use native package loading, while the Bun CLI is reserved for repository development. Some Devin skills declare Claude-only tool names like Bash; those skills still work but require permission prompts for some actions. Release versions are owned by release automation, not hand-bumped in routine PRs.

How engineers can use it

Install on your host. For Claude Code:

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

Cursor users run /add-plugin compound-engineering in agent chat. For Codex CLI:

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

The README also documents installs for Kimi Code CLI, Cline, Grok Build CLI, Devin CLI, GitHub Copilot, Factory Droid, Qwen Code, OpenCode, Pi, oh-my-pi, and Antigravity CLI.

After installing, run /ce-setup in the project. It reports optional tool capabilities and creates .compound-engineering/config.yaml when missing. Users with older installs must refresh the marketplace before /plugin update; update alone keeps the old layout.

The standard loop runs six commands in order on one idea: /ce-brainstorm, /ce-plan, /ce-work, /ce-simplify-code, /ce-code-review, /ce-compound. For bugs, start with /ce-debug; for early discovery, /ce-ideate. The README notes Codex invokes installed skills as $skill-name rather than /skill-name, so adjust accordingly.