By kapoorsunny
Brainstorm, plan, debug, review, and compound learnings with AI agents
Create or update STRATEGY.md. Use when starting a product, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.
Babysits or watches an open GitHub PR until merge-ready, continuously reacting to new review comments and CI failures throughout the PR's life. Use when asked to 'babysit the PR', 'watch the PR', monitor, or keep an eye on a PR over time — not a one-shot request to resolve review comments or debug one CI failure (those are separate skills). GitHub only, including GitHub Enterprise.
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning. Also use when the user must scope work in territory they say they do not know ("I know nothing about X but need to...") or asks for a blindspot pass — mapping the decision surface before questions begin. Not for executing already-specified work — direct implementation, debugging, or code review where no product scope is left to decide. Not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform — brainstorming scopes what to build, not whether to commit to an outside option.
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
Create a git commit with a clear, value-communication message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate, value-communicating message.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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 Add / Add plugin marketplace.
Enter:
| Field | Value |
|---|---|
| Source | EveryInc/compound-engineering-plugin |
| Git ref | main |
| Sparse paths | leave blank |
Click Add marketplace.
Select Compound Engineering, install compound-engineering, 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.
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.
npx claudepluginhub kapoorsunny/compound-engineering-pluginAI-powered development tools for code review, research, design, and workflow automation.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Evidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.9.0 with optional Serena LSP intelligence. Includes blast-radius planning, test/cycle gates, independent review, and Windows Git Bash hook auto-resolution.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Matt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
v9.52.0 - Reliability wave: tangle contextual review correction loop with hard round ceiling, progress-supervised review rounds (per-agent stall watch, descendant-tree kills), council diversity and agy pin fixes, marketplace generator source-of-truth fix, provider troubleshooting runbook and cost-expectations docs. Run /octo:setup.