compound-engineering-plugin
💡 Summary
A Claude Code plugin marketplace and CLI tool that provides a structured workflow (Plan, Work, Review, Compound) to improve engineering efficiency and knowledge retention.
🎯 Target Audience
🤖 AI Roast: “It promises to make future work easier, but first you have to learn its entire philosophical framework.”
The plugin interacts with the filesystem (writing to ~/.opencode, ~/.codex) and executes CLI commands, posing a risk if malicious plugins are installed. Mitigation: Implement a sandboxed execution environment and a code signing/verification process for plugins.
Compound Marketplace
A Claude Code plugin marketplace featuring the Compound Engineering Plugin — tools that make each unit of engineering work easier than the last.
Claude Code Install
/plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin /plugin install compound-engineering
OpenCode + Codex (experimental) Install
This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode and Codex.
# convert the compound-engineering plugin into OpenCode format bunx @every-env/compound-plugin install compound-engineering --to opencode # convert to Codex format bunx @every-env/compound-plugin install compound-engineering --to codex
Local dev:
bun run src/index.ts install ./plugins/compound-engineering --to opencode
OpenCode output is written to ~/.opencode by default, with opencode.json at the root and agents/, skills/, and plugins/ alongside it.
Both provider targets are experimental and may change as the formats evolve.
Codex output is written to ~/.codex/prompts and ~/.codex/skills, with each Claude command converted into both a prompt and a skill (the prompt instructs Codex to load the corresponding skill). Generated Codex skill descriptions are truncated to 1024 characters (Codex limit).
Workflow
Plan → Work → Review → Compound → Repeat
| Command | Purpose |
|---------|---------|
| /workflows:plan | Turn feature ideas into detailed implementation plans |
| /workflows:work | Execute plans with worktrees and task tracking |
| /workflows:review | Multi-agent code review before merging |
| /workflows:compound | Document learnings to make future work easier |
Each cycle compounds: plans inform future plans, reviews catch more issues, patterns get documented.
Philosophy
Each unit of engineering work should make subsequent units easier—not harder.
Traditional development accumulates technical debt. Every feature adds complexity. The codebase becomes harder to work with over time.
Compound engineering inverts this. 80% is in planning and review, 20% is in execution:
- Plan thoroughly before writing code
- Review to catch issues and capture learnings
- Codify knowledge so it's reusable
- Keep quality high so future changes are easy
Learn More
- Full component reference - all agents, commands, skills
- Compound engineering: how Every codes with agents
- The story behind compounding engineering
Pros
- Provides a structured, repeatable workflow for AI-assisted development.
- Focuses on knowledge compounding to reduce future work.
- Supports multiple AI agent platforms (Claude Code, OpenCode, Codex).
Cons
- Experimental support for OpenCode/Codex may be unstable.
- Workflow may be too rigid for simple or exploratory tasks.
- Relies on external AI agent environments to function.
Related Skills
pytorch
S“It's the Swiss Army knife of deep learning, but good luck figuring out which of the 47 installation methods is the one that won't break your system.”
agno
S“It promises to be the Kubernetes for agents, but let's see if developers have the patience to learn yet another orchestration layer.”
nuxt-skills
S“It's essentially a well-organized cheat sheet that turns your AI assistant into a Nuxt framework parrot.”
Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.
Copyright belongs to the original author EveryInc.