compound-engineering

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

Cursor Install

/add-plugin compound-engineering

OpenCode, Codex, Droid, Pi, Gemini, Copilot & Kiro (experimental) Install

This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode, Codex, Factory Droid, Pi, Gemini CLI, GitHub Copilot, and Kiro CLI.

# 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

# convert to Factory Droid format
bunx @every-env/compound-plugin install compound-engineering --to droid

# convert to Pi format
bunx @every-env/compound-plugin install compound-engineering --to pi

# convert to Gemini CLI format
bunx @every-env/compound-plugin install compound-engineering --to gemini

# convert to GitHub Copilot format
bunx @every-env/compound-plugin install compound-engineering --to copilot

# convert to Kiro CLI format
bunx @every-env/compound-plugin install compound-engineering --to kiro

Local dev:

bun run src/index.ts install ./plugins/compound-engineering --to opencode

OpenCode output is written to ~/.config/opencode by default, with opencode.json at the root and agents/, skills/, and plugins/ alongside it. 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). Droid output is written to ~/.factory/ with commands, droids (agents), and skills. Claude tool names are mapped to Factory equivalents (Bash → Execute, Write → Create, etc.) and namespace prefixes are stripped from commands. Pi output is written to ~/.pi/agent/ by default with prompts, skills, extensions, and compound-engineering/mcporter.json for MCPorter interoperability. Gemini output is written to .gemini/ with skills (from agents), commands (.toml), and settings.json (MCP servers). Namespaced commands create directory structure (workflows:plan → commands/workflows/plan.toml). Skills use the identical SKILL.md standard and pass through unchanged. Copilot output is written to .github/ with agents (.agent.md), skills (SKILL.md), and copilot-mcp-config.json. Agents get Copilot frontmatter (description, tools: ["*"], infer: true), commands are converted to agent skills, and MCP server env vars are prefixed with COPILOT_MCP_. Kiro output is written to .kiro/ with custom agents (.json configs + prompt .md files), skills (from commands), pass-through skills, steering files (from CLAUDE.md), and mcp.json. Agents get includeMcpJson: true for MCP server access. Only stdio MCP servers are supported (HTTP servers are skipped with a warning).

All provider targets are experimental and may change as the formats evolve.

Sync Personal Config

Sync your personal Claude Code config (~/.claude/) to other AI coding tools:

# Sync skills and MCP servers to OpenCode
bunx @every-env/compound-plugin sync --target opencode

# Sync to Codex
bunx @every-env/compound-plugin sync --target codex

# Sync to Pi
bunx @every-env/compound-plugin sync --target pi

# Sync to Droid (skills only)
bunx @every-env/compound-plugin sync --target droid

# Sync to GitHub Copilot (skills + MCP servers)
bunx @every-env/compound-plugin sync --target copilot

This syncs:

• Personal skills from ~/.claude/skills/ (as symlinks)
• MCP servers from ~/.claude/settings.json

Skills are symlinked (not copied) so changes in Claude Code are reflected immediately.

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.