🔥 EveryInc/compound-engineering-plugin：面向 Claude Code、Codex、Cursor 等的官方 Compound Engineering 插件
英文标题：🔥 EveryInc/compound-engineering-plugin
EveryInc 发布了适用于 Claude Code、Codex、Cursor 及多种 AI 编程工具的官方 Compound Engineering 插件，旨在通过规划、执行、审查与知识沉淀，让后续工程工作越来越高效。该插件目前提供 32 项技能、0 个独立 Agent，审查、研究和工作流能力均以内嵌的技能本地提示资产形式提供。其核心流程包括需求头脑风暴、实施规划、编码、代码简化、审查和知识复用，并支持由 `/lfg` 自动完成从规划到创建 PR、跟踪 CI 修复的端到端流程。对于开发者而言，该项目将工程经验沉淀为可复用文档和工作流，减少重复探索与技术债务积累。
2.2 KB
65.6 KB
中文
让每一项工程工作都比上一项更轻松的 AI 技能。
/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering
已经安装 Compound Engineering？ Compound Engineering 已迁移至根目录原生布局。你必须在更新前刷新 marketplace——请参见 Existing Installs。仅运行
/plugin update会让你继续停留在旧版本。
在 Cursor Agent 聊天中，请从插件 marketplace 安装：
/add-plugin compound-engineering
或者在插件 marketplace 中搜索“compound engineering”。
Compound Engineering 尚未列入 Codex 的内置插件 marketplace。请将其添加为自定义 marketplace：
-
在 Codex 应用中，从侧边栏打开 Plugins。
-
点击 Create 旁的箭头，然后选择 Add marketplace。
-
输入：
| 字段 | 值 |
|---|---|
| 来源 | EveryInc/compound-engineering-plugin |
| Git ref | main |
| Sparse paths | 留空 |
-
点击 Add marketplace。
-
搜索 Compound Engineering，安装 compound-engineering-plugin，然后重启 Codex。
Codex 应用中的安装对 Compound Engineering 而言是自包含的。专业审查员和研究行为作为本地提示资产保存在各项技能中；无需额外执行自定义 Agent 安装步骤。
注册 marketplace，然后安装插件。
-
向 Codex 注册 marketplace：
codex plugin marketplace add EveryInc/compound-engineering-plugin -
安装插件：
codex plugin add compound-engineering@compound-engineering-plugin
你也可以启动 codex，运行 /plugins，找到 Compound Engineering marketplace，选择 compound-engineering 插件，然后选择 Install。安装完成后重启 Codex。
原生 Codex 插件安装对 Compound Engineering 而言是自包含的。专业审查员和研究行为作为本地提示资产保存在各项技能中；无需额外执行自定义 Agent 安装步骤。
对于非默认的 Codex 配置文件，请针对同一个 CODEX_HOME 执行每一步与 Codex 有关的操作。以下示例会将 CE 安装到 work 配置文件中：
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
marketplace 步骤仅使该插件可用；插件安装步骤才会为该配置文件激活原生 CE 技能。
移除旧版 Codex 工具映射（原生安装之前的安装方式）
如果你此前通过 Bun convert / install --to codex CLI 安装 Compound Engineering（即原生 Codex 插件支持之前），该路径可能在你的全局 Codex 指令文件中插入了一个受管理区块：
<!-- BEGIN COMPOUND CODEX TOOL MAP --> … <!-- END COMPOUND CODEX TOOL MAP -->
位于 $CODEX_HOME/AGENTS.md（默认路径为 ~/.codex/AGENTS.md）。该 Claude 兼容工具映射已过时——CE 技能会内联指定 Codex 工具——其中有一行还错误地要求 Codex 将子 Agent 调度收缩到主线程。原生插件安装不会添加这个区块。
将以下内容粘贴到 Codex（或任何可访问你主目录的 Agent）中以移除它：
Remove the obsolete Compound Engineering Codex tool-map block from my Codex home AGENTS.md.
1. Check `$CODEX_HOME/AGENTS.md` if CODEX_HOME is set, otherwise `~/.codex/AGENTS.md`. If I use Codex profiles, also check `~/.codex/profiles/*/AGENTS.md`.
2. Look for the exact sentinels `<!-- BEGIN COMPOUND CODEX TOOL MAP -->` and `<!-- END COMPOUND CODEX TOOL MAP -->`.
3. If both are present, delete only the span from the BEGIN line through the END line (inclusive), leaving any other user content untouched. Do not edit project/repo AGENTS.md unless those exact sentinels are present there.
4. If the file is empty after the removal, delete the file.
5. Show a short before/after summary of what you changed (or say the block was already absent). Do not add a replacement tool map.
如果该区块仍存在，重新为 Codex 运行 Bun convert/install CLI 也会将其移除；它已不再插入该区块。
使用其他编辑器或 CLI？ Kimi Code CLI、Cline、Grok Build CLI、Devin CLI、GitHub Copilot、Factory Droid、Qwen Code、OpenCode、Pi 和 Antigravity CLI 均受支持——请参见 More install options。
每一项工程工作都应当让后续工作更轻松，而不是更困难。
调用语法：本 README 对支持斜杠技能的宿主使用 /skill-name 示例。在 Codex 中，请使用 $skill-name 调用已安装的技能（例如 $ce-plan 和 $lfg）；/goal 仍是 Codex 的内置命令。
传统开发会积累技术债务。每个功能都会增加复杂性。每次 Bug 修复都会留下更多局部知识，之后仍需要有人重新发现。代码库会越来越大，上下文越来越难以掌握，下一次改动也会越来越慢。
Compound Engineering 颠覆了这一模式：80% 在规划和审查，20% 在执行：
- 使用
/ce-brainstorm和/ce-plan，在编写代码前充分规划，并采用一份基于就绪度的计划产物 - 使用
/ce-code-review和/ce-doc-review进行审查，以发现问题并校准判断 - 使用
/ce-compound将知识规范化，使其可复用 - 维持高质量，让未来的改动更容易
关键不在于繁文缛节，而在于杠杆效应。高质量的头脑风暴会让计划更清晰；高质量的计划会缩小执行范围；高质量的审查能发现模式，而不仅是 Bug；高质量的复盘笔记意味着下一个 Agent 无需从头学习相同的教训。
了解更多
核心循环分为六步：对需求进行头脑风暴（brainstorm）、对实施进行规划（plan）、按计划执行（work）、简化（simplify）所写代码、审查（review）结果，再将经验沉淀复用（compound）——随后在更完善的上下文中重复这一循环。
| 技能 | 用途 |
|---|---|
/ce-brainstorm |
通过交互式问答思考功能或问题，并在规划前编写一份仅包含需求的统一计划 |
/ce-plan |
将功能构想或仅包含需求的计划充实为可实施的计划 |
/ce-work |
原生执行可实施计划，或通过合格的跨模型开发者执行，同时保留宿主验证、提交和交付能力 |
/ce-simplify-code |
在审查前优化新写的代码，以提高可读性和复用性 |
/ce-code-review |
合并前针对计划执行仅报告式多 Agent 审查；本地应用修复需明确触发 |
/ce-compound |
将经验沉淀至 docs/solutions/，让下一轮循环拥有更好的起点 |
每一轮循环都会产生复利：/ce-compound 写入的经验会成为下一次 /ce-brainstorm 与 /ce-plan 所读取的基础上下文——头脑风暴会优化计划，计划会启发未来的计划，审查能发现更多问题，模式会得到文档化。这个回流箭头正是核心所在。
docs/solutions/和docs/plans/等产物目录是默认值。如果项目的docs/是受版本控制的内容，可通过docs_root设置将所有 CE 产物目录迁移到一个相对于仓库的根目录下——请参见配置。
以下技能围绕该循环运行，或按需调用——并非每一轮都需要它们。
| 技能 | 适用时机 |
|---|---|
/ce-ideate |
进入循环之前，当你尚不清楚要构建什么时——生成并批判性排序有据可依的想法，再将最强候选导入 /ce-brainstorm |
/ce-strategy |
上游锚点 -- 创建并维护 STRATEGY.md；ideate、brainstorm 和 plan 会将其作为基础上下文读取，使战略选择流入每项功能 |
/ce-product-pulse |
外部循环 -- 围绕特定时间窗口生成用户实际体验的报告（使用情况、性能、错误），保存至 docs/pulse-reports/；其后续事项会反馈至创意构思和头脑风暴 |
/ce-debug |
当输入是 Bug 而非功能时，替代 brainstorm - > plan -> work——复现问题、追踪根本原因、修复，然后在必要时于交接 PR 前进行优化和审查 |
/ce-pov |
按需使用，在提交前 -- 对某项采用决策、文档的整体观点或给定方案形成明确、基于项目的判断；可选地通过具名同行或 oracle 进行交叉验证，采用盲测式首轮评估和有边界的协调 |
/ce-explain |
按需使用，用于说明工作或理解工作 -- 将一个概念、diff、想法或“我这周做了什么？”转化为一份密集、自包含、值得保留的可视化文档；当材料值得留存时，可附带可选的检查环节（针对 diff 的先预测后揭示、经纠正的练习） |
如需完整目录及各项技能如何串联，请参见 docs/skills。完整清单如下。
寻找方向 -- 当你还没有明确的想法时，先进行 ideate，再将最强候选带入循环：
/ce-ideate new drawing tools
/ce-ideate surprise me
/ce-ideate open issues # ground ideas in your tracker's open issues (GitHub, Linear, Jira)
/ce-ideate 会先完成准备工作（代码库、既有经验、网络上的先例，以及可选的议题追踪器），然后交给你一组经过排序、有事实依据的候选方案，供你带入 /ce-brainstorm。
标准功能循环 -- 将粗略想法转化为已交付、经过审查的代码：
/ce-brainstorm make background job retries safer
/ce-plan
/ce-work
/ce-simplify-code
/ce-code-review
/ce-compound
简化代码 -- 在完成新的实施工作后使用，或将其指向持续拖慢改动速度的代码：
/ce-simplify-code
/ce-simplify-code simplify the code in my most-churned file
第一轮会在审查前收紧近期分支中的改动。定向模式则适用于某个文件不断吸收无关修复、后续改动或合并冲突的情况。
调试 Bug -- 当你的起点是异常行为而非新功能时：
/ce-debug the checkout webhook sometimes creates duplicate invoices
/ce-code-review
/ce-compound
自主模式 -- 交接一个功能，让 Agent 运行整条流水线：
/ce-brainstorm describe the feature
/lfg
/lfg 会以无人值守方式运行该循环：它会规划、按计划执行、简化、运行代码审查并应用修复、运行浏览器测试、提交、推送、创建 PR，然后监控 CI 并修复失败项，直到 CI 变绿。请在 /ce-brainstorm 后启动它，使其能够针对真实需求而非一句话提示进行规划。这是标准循环的自动驾驶版本——适合你暂时离开，回来时看到一个已创建且 CI 通过的 PR。当一个符合条件的多领域计划仍有未规划的工作时，lfg 还会推荐并说明下一个需要独立规划的领域；只有在你接受后，它才会为新会话创建一个 /ce-handoff 和单独的计划。
安装后，请在任意项目中运行 /ce-setup。它会检查仓库本地配置、报告可选工具能力，并协助安全地将机器本地的 CE 设置加入 gitignore。
compound-engineering 插件目前提供 32 项技能和 0 个独立 Agent。专业审查、研究和工作流行为均存在于所属技能的技能本地提示资产中。
| 技能 | 用途 |
|---|---|
/ce-strategy |
创建或维护 STRATEGY.md |
/ce-ideate |
生成并批判性评估有据可依的想法 |
/ce-pov |
对采用决策、文档或方案集合形成明确且基于项目的 POV |
/ce-explain |
将概念、diff、想法或自己一段时间内的工作记录为一份值得保留的可视化产物 |
/ce-brainstorm |
探索需求并编写大小适宜的需求文档 |
/ce-plan |
创建结构化实施计划 |
/ce-work |
通过原生或跨模型实施、持久化进度和由宿主负责的事务性集成来执行计划 |
/ce-code-review |
使用技能本地审查员角色审查代码 |
/ce-doc-review |
审查 |
English / 原文
AI skills that make each unit of engineering work easier than the last.
/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering
Already have Compound Engineering installed? Compound Engineering moved to a root-native layout. You must refresh the marketplace before updating — see Existing Installs. Running
/plugin updatealone keeps you on the old version.
In Cursor Agent chat, install from the plugin marketplace:
/add-plugin compound-engineering
Or search for "compound engineering" in the plugin marketplace.
Compound Engineering is not listed in Codex's built-in plugin marketplace yet. Add it as a custom marketplace:
-
In the Codex app, open Plugins from the sidebar.
-
Click the arrow next to Create , then select Add marketplace.
-
Enter:
| Field | Value |
|---|---|
| Source | EveryInc/compound-engineering-plugin |
| Git ref | main |
| Sparse paths | leave blank |
-
Click Add marketplace.
-
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.
-
Register the marketplace with Codex:
codex plugin marketplace add EveryInc/compound-engineering-plugin -
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.
Remove the legacy Codex tool map (pre-native installs)
If you previously installed Compound Engineering with the Bun convert / install --to codex CLI (before native Codex plugin support), that path may have inserted a managed block into your global Codex instructions file:
<!-- BEGIN COMPOUND CODEX TOOL MAP --> … <!-- END COMPOUND CODEX TOOL MAP -->
in $CODEX_HOME/AGENTS.md (default ~/.codex/AGENTS.md). That Claude-compat tool map is obsolete — CE skills name Codex tools inline — and one of its lines incorrectly told Codex to collapse subagent dispatch onto the main thread. Native plugin install does not add this block.
Paste this into Codex (or any agent with access to your home directory) to remove it:
Remove the obsolete Compound Engineering Codex tool-map block from my Codex home AGENTS.md.
1. Check `$CODEX_HOME/AGENTS.md` if CODEX_HOME is set, otherwise `~/.codex/AGENTS.md`. If I use Codex profiles, also check `~/.codex/profiles/*/AGENTS.md`.
2. Look for the exact sentinels `<!-- BEGIN COMPOUND CODEX TOOL MAP -->` and `<!-- END COMPOUND CODEX TOOL MAP -->`.
3. If both are present, delete only the span from the BEGIN line through the END line (inclusive), leaving any other user content untouched. Do not edit project/repo AGENTS.md unless those exact sentinels are present there.
4. If the file is empty after the removal, delete the file.
5. Show a short before/after summary of what you changed (or say the block was already absent). Do not add a replacement tool map.
Re-running the Bun convert/install CLI for Codex also strips the block if it is still present; it no longer inserts it.
Another editor or CLI? Kimi Code CLI, Cline, Grok Build CLI, Devin CLI, GitHub Copilot, Factory Droid, Qwen Code, OpenCode, Pi, 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); /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-brainstormand/ce-planusing one readiness-based plan artifact - Review to catch issues and calibrate judgment with
/ce-code-reviewand/ce-doc-review - Codify knowledge so it is reusable with
/ce-compound - Keep quality high so future changes are easy
The point is not ceremony. The point is leverage. 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.
Learn more
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.
| Skill | Purpose |
|---|---|
/ce-brainstorm |
Interactive Q&A to think through a feature or problem and write a requirements-only unified plan before planning |
/ce-plan |
Enrich feature ideas or requirements-only plans into implementation-ready plans |
/ce-work |
Execute implementation-ready plans natively or through a qualified cross-model author while retaining host verification, commits, and shipping |
/ce-simplify-code |
Refine the freshly written code for clarity and reuse before review |
/ce-code-review |
Report-only multi-agent review against the plan before merging; local apply is explicit |
/ce-compound |
Capture the learning into docs/solutions/ so the next loop starts smarter |
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.
Artifact folders like
docs/solutions/anddocs/plans/are the defaults. A project whosedocs/is tracked content can relocate every CE artifact folder under one repo-relative root via thedocs_rootsetting -- see configuration.
These sit around the loop or get reached for on demand -- not every cycle needs them.
| Skill | When to reach for it |
|---|---|
/ce-ideate |
Before the loop , when you don't yet know what to build -- generates and critically ranks grounded ideas, then routes the strongest one into /ce-brainstorm |
/ce-strategy |
Upstream anchor -- creates and maintains STRATEGY.md, read as grounding by ideate, brainstorm, and plan so strategy choices flow into every feature |
/ce-product-pulse |
Outer loop -- a time-windowed report on what users actually experienced (usage, performance, errors), saved to docs/pulse-reports/; its follow-ups feed back into ideation and brainstorming |
/ce-debug |
Instead of brainstorm - > plan -> work when the input is a bug rather than a feature -- reproduce, trace root cause, fix, then polish/review before PR handoff when warranted |
/ce-pov |
On demand, before you commit -- a decisive, project-grounded adoption verdict, holistic document take, or position on supplied approaches; optionally cross-checked by named peers or oracle through a blind initial round and bounded reconciliation |
/ce-explain |
On demand, to account for the work or understand it -- turns a concept, a diff, an idea, or "what did I do this week?" into a dense, self-contained visual document built to keep, with an optional check-in (predict-then-reveal for diffs, corrected exercises) when the material is worth retaining |
For the full catalog and how each skill chains together, see docs/skills. The complete inventory is below.
Finding a direction -- when you don't have a specific idea yet, ideate first, then carry the strongest survivor into the loop:
/ce-ideate new drawing tools
/ce-ideate surprise me
/ce-ideate open issues # ground ideas in your tracker's open issues (GitHub, Linear, Jira)
/ce-ideate does the homework first (codebase, past learnings, prior art on the web, optionally your issue tracker), then hands you a ranked set of grounded candidates to take into /ce-brainstorm.
Standard feature 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
Simplifying code -- use it after fresh implementation work, or point it at code that keeps slowing changes down:
/ce-simplify-code
/ce-simplify-code simplify the code in my most-churned file
The first pass tightens recent branch changes before review. The targeted pass is useful when one file keeps absorbing unrelated fixes, follow-ups, or merge conflicts.
Debugging a bug -- when you start from broken behavior instead of a feature:
/ce-debug the checkout webhook sometimes creates duplicate invoices
/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 plans, works through the plan, simplifies, runs code review and applies the fixes, runs browser tests, commits, pushes, opens a PR, then watches CI and repairs failures until it's green. Start it after /ce-brainstorm so it plans against real requirements rather than a one-line prompt. It's the autopilot version of the standard loop -- neat when you want to step away and come back to an open, green PR. When an eligible multi-area plan still has unplanned work, lfg also recommends and justifies the next separately planned area; only if you accept does it create a /ce-handoff for a fresh session and separate plan.
After installing, run /ce-setup in any project. It checks repo-local config, reports optional tool capabilities, and helps keep machine-local CE settings safely gitignored.
The compound-engineering plugin currently ships 32 skills and 0 standalone agents. Specialist review, research, and workflow behavior lives inside the owning skills as skill-local prompt assets.
| Skill | Purpose |
|---|---|
/ce-strategy |
Create or maintain STRATEGY.md |
/ce-ideate |
Generate and critically evaluate grounded ideas |
/ce-pov |
Form a decisive, project-grounded POV on an adoption, document, or approach set |
/ce-explain |
Document a concept, diff, idea, or window of your own work as a visual artifact built to keep |
/ce-brainstorm |
Explore requirements and write a right-sized requirements doc |
/ce-plan |
Create structured implementation plans |
/ce-work |
Execute plans with native or cross-model implementation, durable progress, and transactional host-owned integration |
/ce-code-review |
Review code with skill-local reviewer personas |
/ce-doc-review |
Review requirements and plan documents |
/ce-debug |
Reproduce failures, trace root cause, fix bugs, and prepare non-trivial fixes for PR |
/ce-compound |
Document solved problems to compound team knowledge |
/ce-compound-refresh |
Refresh stale or drifting learnings |
/ce-optimize |
Run iterative optimization loops |
/ce-retune |
Retune a skill corpus for a new model, measurement-first |
/ce-product-pulse |
Generate time-windowed product pulse reports |
/ce-riffrec-feedback-analysis |
Convert Riffrec recordings or notes into structured feedback |
/ce-sweep |
Sweep feedback sources, track item lifecycles, and emit an /lfg-ready plan |
/ce-resolve-pr-feedback |
Resolve PR review feedback |
/ce-commit |
Create a git commit with a clear message |
/ce-commit-push-pr |
Commit, push, and open a PR that teaches any concept the change newly introduces |
/ce-babysit-pr |
Watch an open PR and keep it moving toward merge, reacting to review comments and CI as they arrive |
/ce-worktree |
Ensure work happens in an isolated git worktree |
/ce-promote |
Draft user-facing announcement copy |
/ce-test-browser |
Run browser tests on PR-affected pages |
/ce-test-xcode |
Build and test iOS apps on simulator |
/ce-setup |
Diagnose optional tool capabilities and project config |
/ce-handoff |
Create a session handoff at the default temp store or a requested destination, then resume from a selected source |
/ce-simplify-code |
Simplify recent code changes |
/ce-polish |
Start a dev server and iterate on UX polish |
/ce-proof |
Create, edit, and share Proof documents |
/ce-dogfood |
Hands-off diff-scoped browser QA of the active branch, with autonomous fixes |
/lfg |
Full autonomous engineering workflow |
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), so no Bun install step is needed. 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 :
- Run
Chat: Install Plugin from Sourcefrom the VS Code command palette - Use
EveryInc/compound-engineering-pluginfor the repo - Select
compound-engineeringwhen 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, so no separate Bun install step is needed.
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, so no Bun install step is needed.
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, so no Bun install step is needed.
Add Compound Engineering to the plugin array in your global or project opencode.json:
{
"plugin": ["compound-engineering@git+https://github.com/EveryInc/compound-engineering-plugin.git"]
}
Restart OpenCode after changing the config. The OpenCode plugin registers the Compound Engineering skills directory 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
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. An existing marketplace install keeps a cached marketplace snapshot that still points at the old plugins/compound-engineering path, so updating the plugin on its own reads that stale snapshot and leaves you on the previous version. Refresh the cached marketplace first , then update the plugin — order matters.
Claude Code
/plugin marketplace update compound-engineering-plugin
/plugin update compound-engineering
Codex CLI
codex plugin marketplace upgrade compound-engineering-plugin
codex plugin add compound-engineering@compound-engineering-plugin
There is no codex plugin update; re-running add reinstalls from the refreshed snapshot. For a non-default profile, run both commands against the same CODEX_HOME.
Codex App
Refresh the marketplace from the Plugins panel (remove and re-add the EveryInc/compound-engineering-plugin marketplace if there is no refresh control), then reinstall compound-engineering and restart Codex.
If you configured a host with a direct path or sparse path under plugins/compound-engineering, edit or reinstall that source so it points at the repository root with no sparse path.
If a previous Bun-installed copy is still shadowing native plugin skills, run the current cleanup command from a checkout of this repository:
git clone https://github.com/EveryInc/compound-engineering-plugin.git /tmp/compound-engineering-plugin-cleanup
cd /tmp/compound-engineering-plugin-cleanup
bun install
bun run cleanup --target all
bun install
bun test
bun run release:validate
For active development, load this checkout directly in the harness you want to test.
Claude Code
claude --plugin-dir "$PWD"
Cursor Agent CLI
cursor-agent --plugin-dir "$PWD"
Codex
For the normal production-like plugin installation, use the Codex App or Codex CLI instructions above. The workflow below is only for contributors who need Codex to load unreleased files from an exact checkout or linked worktree.
Advanced: test this exact checkout in Codex
Select the current worktree as the active Codex development source:
bun run codex:dev -- local
This creates one collection symlink at $CODEX_HOME/skills/compound-engineering-local (default ~/.codex/skills/compound-engineering-local) pointing to this worktree's skills/ directory. It removes installed Compound Engineering plugin variants through the Codex CLI so a cached marketplace plugin cannot shadow or duplicate the local skills. It does not copy skills, change the checkout, pull Git, or touch unrelated entries under $CODEX_HOME/skills.
The link exposes exactly what is in the selected worktree, including modified and untracked skills. Ordinary edits therefore need no reinstall, and current Codex versions detect direct skill changes automatically. Start a new session after switching between local and remote installation modes; if an ordinary skill edit does not appear, restart Codex.
Use these commands to inspect and switch modes:
bun run codex:dev -- status
bun run codex:dev -- refresh
bun run codex:dev -- remote
bun run codex:dev -- remove
statusreports local, remote, mixed, drifted, or absent state plus the linked checkout, worktree kind, branch, commit SHA, and dirty counts.refreshis an idempotent alias forlocal; use it to reconcile accidental plugin installs. The live link already reflects file changes.remoterefreshes the official Git marketplace, installs and verifiescompound-engineering@compound-engineering-plugin, then removes the local link. Use it to simulate the released user experience.removeremoves Compound Engineering plugin variants and the managed link, leaving the checkout and unrelated user skills intact.
The script derives the repository path, so it works from checkouts in any location, including paths with spaces. It inherits the active CODEX_HOME; set CODEX_HOME on the command when testing an isolated profile. Run every mode against the same CODEX_HOME you use to launch Codex.
Do not use codex plugin marketplace add "$PWD" for live local development. It installs a cached copy of this checkout, so later edits are not reflected until the plugin is installed again; a matching manifest version also does not prove the cache matches the worktree. The codex:dev workflow instead keeps Codex linked to the current skill files.
Kimi Code CLI
Inside Kimi Code CLI:
/plugins install /path/to/compound-engineering-plugin
To test the local marketplace catalog instead, pass the catalog path:
/plugins marketplace /path/to/compound-engineering-plugin/.kimi-plugin/marketplace.json
Cline
/path/to/compound-engineering-plugin/.cline/scripts/install-skills.sh --global
Enable Settings - > Features -> Enable Skills in the Cline extension, then start a new task.
Devin CLI
devin plugins install /path/to/compound-engineering-plugin
Local installs are linked to the checkout rather than copied, so skill edits apply on the next Devin session without reinstalling.
OpenCode
{
"plugin": ["/path/to/compound-engineering-plugin"]
}
Restart OpenCode after changing opencode.json.
Pi
Antigravity CLI (agy)
agy plugin install "$PWD"
agy plugin validate "$PWD"
Or install the bundled .agy/ entry point:
agy plugin install "$PWD/.agy"
See .agy/INSTALL.md for remote install and pinning examples.
OpenCode and Pi 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.
Do I need Bun to install Compound Engineering?
No. Bun is only needed for repo development tasks and converter maintenance.
Where do I see all available skills?
The skill inventory is in this README, and the deeper skill catalog is in docs/skills/README.md. Each skill's authoritative runtime spec lives in skills/<skill>/SKILL.md.
Where is release history?
GitHub Releases are the canonical release-notes surface. The root CHANGELOG.md points to that history.
Contributions are welcome. Issues, bug reports, and pull requests all help make this better, and we genuinely appreciate them — bug reports especially.
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.