Which AI coding tools does this plugin support?

Claude Code, Cursor, Codex App, and Codex CLI have direct install paths. Kimi Code CLI, Cline, Grok Build CLI, Devin CLI, GitHub Copilot, Factory Droid, Qwen Code, OpenCode, Pi, and Antigravity CLI are supported through additional install options.

How many skills does the plugin ship with?

32 skills, covering the core plan-work-review-compound loop plus ideation, strategy, debugging, PR feedback, browser and Xcode testing, and session handoff.

How do I invoke a skill in Codex versus Claude Code?

Claude Code and other slash-skill hosts use `/skill-name` (for example `/ce-plan`), while Codex uses `$skill-name` (for example `$ce-plan`); `/goal` remains a Codex built-in command regardless.

What does `/lfg` do differently from the standard loop?

It runs the full brainstorm-to-ship loop hands-off: planning, execution, simplification, code review with fixes applied, browser testing, commit, push, PR creation, and CI monitoring until the build is green.

Where does the plugin store plans and learnings?

By default in `docs/plans/` and `docs/solutions/` in the repo; these locations can be moved under a single repo-relative root via the `docs_root` configuration setting.

Compound Engineering Plugin: A skill pack

Compound Engineering is a plugin of AI skills for coding agents like Claude Code, Cursor, and Codex. It's aimed at developers and teams using AI assistants for real feature work who want a repeatable process instead of ad-hoc prompting, and who want each engineering task to leave the codebase easier to work in, not harder.

The plugin is built around a philosophy: put most of the effort into planning and review (roughly 80%) and less into raw execution (20%). Instead of treating each coding session as isolated, it structures work into a loop, brainstorm, plan, work, simplify, review, compound, so that lessons learned in one cycle inform the next. A /ce-compound step writes learnings to a docs/solutions/ folder that future brainstorms and plans read as grounding.

Key features

Structured workflow loop: six core skills (/ce-brainstorm, /ce-plan, /ce-work, /ce-simplify-code, /ce-code-review, /ce-compound) cover requirements gathering through knowledge capture.
Multi-host support: installable in Claude Code, Cursor, Codex App, Codex CLI, and via custom marketplace setup for other editors and CLIs (Kimi Code CLI, Cline, Grok Build CLI, Devin CLI, GitHub Copilot, Factory Droid, Qwen Code, OpenCode, and more).
Autonomous pipeline mode: /lfg runs the full loop hands-off, including planning, coding, review, browser tests, commit, push, PR creation, and CI monitoring until green.
Ideation and strategy skills: /ce-ideate generates and ranks grounded feature ideas; /ce-strategy maintains a STRATEGY.md that other skills read for context.
Dedicated bug workflow: /ce-debug reproduces failures, traces root cause, and prepares fixes for PR as an alternative to the feature-planning loop.
Report-only code review: /ce-code-review runs multi-agent review against the plan before merge, with local apply left explicit rather than automatic.
Knowledge compounding: /ce-compound and /ce-compound-refresh document solved problems and keep that documentation from going stale.
Configurable artifact roots: default docs/plans/ and docs/solutions/ folders can be relocated under a single repo-relative root via a docs_root setting.
32 shipped skills total, including PR feedback resolution, git worktree isolation, browser and Xcode test running, and session handoff between agents.

Ideal use cases

This fits teams already using Claude Code, Cursor, or Codex for day-to-day feature work who want a consistent plan-review-ship cycle instead of freeform prompting. It's a good match for codebases where technical debt from ad-hoc AI-assisted changes has become a problem, since the loop is explicitly designed to leave things easier for the next change. It also suits teams that want a paper trail: requirements docs, implementation plans, and solution write-ups that persist across sessions and across different engineers or agents picking up the work.

It's less useful for one-off scripts, throwaway prototypes, or solo tinkering where the overhead of brainstorming and planning artifacts outweighs the benefit. Teams not using one of the supported hosts (Claude Code, Cursor, Codex, or the other listed CLIs/editors) won't be able to install it directly. If your workflow doesn't tolerate a docs/ folder full of plans and solution notes, or you can't adopt the docs_root convention, the artifact-heavy approach may feel like friction rather than help.

Installation

Installation depends on the host tool.

Claude Code:

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

Cursor (in Cursor Agent chat):

/add-plugin compound-engineering

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

Codex App: open Plugins in the sidebar, click the arrow next to Create, select "Add marketplace," and enter source EveryInc/compound-engineering-plugin with git ref main. Then search for and install "Compound Engineering," and restart Codex.

Codex CLI:

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

You can also run codex, use /plugins, and install from there. Restart Codex after install.

For a non-default Codex profile, run the same commands with CODEX_HOME set to that profile's path.

After installing on any host, run /ce-setup in a project to check repo-local config and gitignore machine-local CE settings. Other editors and CLIs (Cline, GitHub Copilot, OpenCode, and others) are supported through a similar custom-marketplace setup described in the project's docs.