Skip to main content

​
Quick Start

Get started with the compound-engineering plugin in under a minute. This guide shows you how to install it to OpenCode, but the same process works for any supported platform.

​
Install to OpenCode

The fastest way to get started is installing the bundled compound-engineering plugin:
1

Run the install command

Use bunx to install the plugin to OpenCode without any setup:
bunx @every-env/compound-plugin install compound-engineering --to opencode
This command:
  • Downloads the latest version of the CLI
  • Converts the compound-engineering plugin to OpenCode format
  • Installs agents, commands, skills, and MCP servers to ~/.config/opencode/
2

Verify the installation

Check what was installed:
ls ~/.config/opencode/agents/
ls ~/.config/opencode/commands/
ls ~/.config/opencode/skills/
You should see:
  • 29 agents organized by category (review, research, design, workflow, docs)
  • 22 commands for workflow automation and utilities
  • 20 skills for architecture, development, and orchestration
3

Use your first command

Try the core workflow commands in OpenCode:
# Create an implementation plan
/ce:plan

# Run a comprehensive code review
/ce:review

# Execute work items systematically
/ce:work

# Document learnings for future use
/ce:compound

​
What Gets Installed

​
Agents (29)

Specialized AI agents for different aspects of development:

Review Agents (15)

  • Architecture strategist
  • Security sentinel
  • Performance oracle
  • DHH Rails reviewer
  • Data integrity guardian
  • Schema drift detector
  • And 9 more specialized reviewers

Research Agents (5)

  • Best practices researcher
  • Framework docs researcher
  • Git history analyzer
  • Learnings researcher
  • Repo research analyst

Design Agents (3)

  • Design implementation reviewer
  • Design iterator
  • Figma design sync

Workflow Agents (5)

  • Bug reproduction validator
  • Every style editor
  • Lint runner
  • PR comment resolver
  • Spec flow analyzer

​
Commands (22)

Workflow automation and utilities: Core Workflow Commands (use ce: prefix): 
/ce:plan          # Create implementation plans
/ce:work          # Execute work items systematically
/ce:review        # Run comprehensive code reviews
/ce:compound      # Document solved problems
/ce:brainstorm    # Explore requirements before planning
Utility Commands: 
/lfg              # Full autonomous engineering workflow
/slfg             # Full autonomous workflow with swarm mode
/deepen-plan      # Enhance plans with parallel research
/changelog        # Create engaging changelogs
/create-agent-skill  # Create or edit skills
/resolve_parallel # Resolve TODOs in parallel
/triage           # Triage and prioritize issues

​
Skills (20)

Reusable knowledge modules:
  • Architecture - agent-native-architecture, skill-creator
  • Development - dhh-rails-style, dspy-ruby, frontend-design, andrew-kane-gem-writer
  • Workflow - brainstorming, git-worktree, file-todos, proof, document-review
  • Orchestration - orchestrating-swarms for multi-agent coordination
  • Tools - agent-browser, rclone, gemini-imagegen

​
MCP Server

The Context7 MCP server provides framework documentation lookup:
  • resolve-library-id - Find library ID for a framework/package
  • get-library-docs - Get documentation for specific libraries
  • Supports 100+ frameworks (Rails, React, Next.js, Vue, Django, Laravel, etc.)

​
Install to Other Platforms

The same plugin works across all supported platforms: 
bunx @every-env/compound-plugin install compound-engineering --to opencode

​
Example: Complete Workflow

Here’s how to use the compound engineering workflow on a real feature:
1

Brainstorm the approach

/ce:brainstorm
Explore requirements and discuss different approaches before committing to a plan.
2

Create a detailed plan

/ce:plan
Turn your feature idea into a detailed implementation plan with steps, considerations, and testing strategy.
3

Execute the work

/ce:work
Work through your plan systematically with git worktrees and task tracking.
4

Run comprehensive review

/ce:review
Multi-agent code review covers:
  • Security vulnerabilities
  • Performance bottlenecks
  • Architecture compliance
  • Code simplicity
  • Data integrity
  • Framework best practices
5

Document learnings

/ce:compound
Capture what you learned to make similar features easier next time. This is how the workflow compounds.

​
Sync Your Personal Config

Already using Claude Code? Sync your personal skills, commands, and MCP servers to other platforms automatically.
# Sync to all detected AI coding tools
bunx @every-env/compound-plugin sync

# Sync to specific platform
bunx @every-env/compound-plugin sync --target opencode
This syncs:
  • Personal skills from ~/.claude/skills/ (as symlinks)
  • Personal slash commands from ~/.claude/commands/
  • MCP servers from ~/.claude/settings.json
Skills are symlinked, so changes in Claude Code are reflected immediately in other tools.

​
Next Steps

CLI Reference

Explore all available commands and options

Plugin Components

Learn about the 29 agents, 22 commands, and 20 skills

Conversion Guide

Convert your own Claude Code plugins

Configuration

Customize behavior and output locations

​
Troubleshooting

​
MCP Server Not Loading

If the Context7 MCP server doesn’t auto-load, manually add it to your config: For OpenCode (~/.config/opencode/opencode.json): 
{
  "mcpServers": {
    "context7": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

​
Commands Not Found

If commands aren’t recognized after installation:
  1. Restart your AI coding assistant
  2. Check that files were written to the correct location: 
    ls ~/.config/opencode/commands/
  3. Verify the assistant is configured to read from that directory

​
Permission Errors

If you see permission errors during installation: 
# Ensure the config directory exists and is writable
mkdir -p ~/.config/opencode
chmod u+w ~/.config/opencode

​
Learn More