Compound Engineering
Every's open-source agent workflow plugin connects discovery, planning, implementation, debugging, review, delivery, and captured learnings through 33 skills, with native installation paths for Claude Code, Codex, Cursor, and other hosts.
Project overview
Compound Engineering is Every's end-to-end engineering workflow plugin for coding agents. It is neither one prompt nor a loose command collection: the repository divides discovery, planning, implementation, debugging, simplification, code review, pull-request handling, and captured learnings into 33 composable skills, with manifests or conversion paths for Claude Code, Codex, Cursor, and additional hosts. Its central idea is to write validated decisions and solved problems back into project documentation so later tasks can retrieve and reuse them. The actual automation surface still depends on the invoked skill, host permissions, and repository configuration.
Core capabilities
Discovery to executable planning
ce-brainstorm, ce-plan, ce-product-pulse, and prototype-oriented skills clarify goals, gather evidence, record decisions, and produce plans that implementation can consume.
Implementation, debugging, and local verification
ce-work implements a plan or concrete request, while ce-debug handles open-ended faults. Their instructions place gates around repository state, working trees, and verification evidence.
Structured code review
ce-code-review selects review lenses from the change risk, can run an independent cross-model pass when permitted, and reports findings without pushing by default.
Automated delivery pipeline
lfg connects planning, implementation, simplification, review, browser testing, commits, pushes, pull requests, and CI monitoring. Its instructions fall back to local commits when no remote exists and do not merge the pull request.
Captured and reusable learnings
ce-compound writes solved problems into repository documentation for later planning runs to retrieve. docs_root is configurable but must remain inside the repository.
Installation and usage
Prefer the active host's native plugin path. Claude Code and Codex CLI first add the EveryInc marketplace and then install compound-engineering. Existing installations must refresh the marketplace before upgrading. Restart or begin a new session, then run the ce-setup health check.
Let an AI Agent install it
Send this prompt to Codex, Claude Code, or another AI agent that can work with your local environment.
Help me install Compound Engineering from https://github.com/EveryInc/compound-engineering-plugin. First identify the current host and version, then read the README, the matching installation section, docs/install/upgrading.md, PRIVACY.md, SECURITY.md, and the manifest that will be enabled. Explain file writes, shell, browser, Git/GitHub, cross-model, and optional external-integration boundaries. After I confirm, run only the documented native installation commands. Refresh the marketplace first when upgrading. Restart or start a new session, then run only the ce-setup health check. Do not invoke lfg, push, open a pull request, connect third-party services, or modify a production repository.- Claude Code, Codex, or Cursor with plugin support is installed
- Public GitHub repositories and the host marketplace are reachable
- A non-production Git repository and a clear branch protection policy are available for initial testing
- You have decided whether cross-model review, browser automation, GitHub, and optional external integrations are allowed
/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering- 1Choose a host and confirm versions
Identify Claude Code, Codex, Cursor, or another host explicitly listed in the README, and confirm that the current version supports the native plugin path.
- 2Add the marketplace and install
Run the README commands for the selected host. Existing users should refresh the marketplace first to avoid an older cached package.
- 3Restart and run the health check
Restart the host or create a new session, then run ce-setup to inspect the plugin version, docs_root, configuration layers, and missing optional tools.
- 4Begin with a low-risk workflow
Use brainstorm or plan on a small non-production branch first, review the generated artifacts, and expand implementation, Git, browser, or integration permissions gradually.
Restart the host after installation, confirm that Compound Engineering skills appear, and invoke ce-setup first to inspect the plugin version, optional tools, docs_root, and repository configuration. Do not point the first check at production writes or invoke lfg before reviewing permissions.
- Host commands can change with releases; recheck the current README or target release before installing
- A stale marketplace cache can keep an upgrade on an older version
- Install optional tools only for workflows that actually need them
Use cases
Plan and implement a complex feature
Turn an ambiguous request into a plan with evidence and acceptance criteria, then let the implementation workflow make and locally verify the changes.
Review high-risk changes from multiple angles
Select security, performance, architecture, or testing lenses from the diff, with an independent model pass when organizational policy allows it.
Keep incident knowledge in the repository
Write a verified root cause, fix, and regression guidance into solution documents so future plans can discover the constraint.
Run a controlled delivery pipeline
In an environment with deliberate remote, branch, and CI permissions, use lfg to reach an open pull request while preserving unapplied review findings.
Assessment
Compound Engineering's value is the way it turns engineering stages, evidence gates, and reusable learnings into inspectable skills, not any single command. The repository has clear multi-host setup, an MIT license, privacy documentation, releases, and recent maintenance, with a substantial test and manifest structure. Its permission surface is also much larger than an ordinary prompt: the full pipeline may edit files, run commands, route code, push branches, and open pull requests. A sensible adoption path begins with ce-setup and low-risk planning, then enables capabilities one by one under team policy. This assessment uses first-party repository evidence and source structure; installation and functionality were not tested.
Why it may be useful
- Covers the full loop from discovery through delivery and captured learnings
- Provides explicit installation paths for Claude Code, Codex, Cursor, and other hosts
- Includes versioned releases, privacy and security documentation, and active maintenance
- Defines detailed gates around working trees, branches, verification, cross-model routing, and delivery
What to know first
- Natural-language instructions still rely on correct host behavior and are not an operating-system or platform sandbox
- Automated delivery and cross-model features require additional governance for code, network, and GitHub permissions
- Hosts differ in capabilities and command surfaces
- No skill was installed or run for this publication
README
Compound Engineering
Overview
Every's open-source agent workflow plugin connects discovery, planning, implementation, debugging, review, delivery, and captured learnings through 33 skills, with native installation paths for Claude Code, Codex, Cursor, and other hosts. Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more.
Getting started
- Prefer the active host's native plugin path. Claude Code and Codex CLI first add the EveryInc marketplace and then install compound-engineering. Existing installations must refresh the marketplace before upgrading. Restart or begin a new session, then run the ce-setup health check.
- The README presents a brainstorm, plan, work, review, and compound loop: form a plan, implement and review it, then write reusable conclusions into project documentation.
- The repository currently contains 33 skills spanning product strategy, prototyping, debugging, code review, pull-request feedback, browser testing, commits, and continuous learning.
- Restart the host after installation, confirm that Compound Engineering skills appear, and invoke ce-setup first to inspect the plugin version, optional tools, docs_root, and repository configuration. Do not point the first check at production writes or invoke lfg before reviewing permissions.
Configuration
/plugin marketplace add EveryInc/compound-engineering-plugin
/plugin install compound-engineering