| layout | default |
|---|---|
| title | Compound Engineering Plugin Tutorial |
| nav_order | 146 |
| has_children | true |
| format_version | v2 |
Learn how to use
EveryInc/compound-engineering-pluginto run compound engineering workflows in Claude Code and convert plugin assets for other coding-agent ecosystems.
Compound Engineering Plugin combines workflow discipline, reusable agent assets, and cross-toolchain conversion support for teams running mixed coding-agent environments.
This track focuses on:
- installing and operating the core
compound-engineeringplugin - understanding how workflows, agents, commands, and skills compound over time
- using conversion/sync tooling for OpenCode, Codex, and Droid targets
- applying quality and governance controls to compound engineering loops
- repository:
EveryInc/compound-engineering-plugin - stars: about 10.7k
- latest release:
compound-engineering-v2.47.0(published 2026-03-20)
flowchart LR
A[Feature idea] --> B[Plan workflow]
B --> C[Work execution]
C --> D[Multi-agent review]
D --> E[Compound learnings]
E --> F[Future cycles become faster]
| Chapter | Key Question | Outcome |
|---|---|---|
| 01 - Getting Started | How do I install and run the core plugin quickly? | Working baseline |
| 02 - Compound Engineering Philosophy and Workflow Loop | How does plan/work/review/compound create leverage? | Strong workflow model |
| 03 - Architecture of Agents, Commands, and Skills | How are components organized and selected? | Better capability mapping |
| 04 - Multi-Provider Conversion and Config Sync | How do I target OpenCode, Codex, and Droid from same source? | Cross-toolchain portability |
| 05 - MCP Integrations and Browser Automation | How do Context7/Playwright integrations fit into workflows? | Strong integration strategy |
| 06 - Daily Operations and Quality Gates | How do teams run compound workflows consistently? | Operational reliability |
| 07 - Troubleshooting and Runtime Maintenance | How do I recover from plugin/runtime failures quickly? | Faster recovery loops |
| 08 - Contribution Workflow and Versioning Discipline | How do contributors evolve the plugin safely? | Contributor readiness |
- how to operationalize compound engineering principles in real coding loops
- how to exploit reusable agents/commands/skills for quality and speed
- how to synchronize capabilities across Claude Code and other agent platforms
- how to govern plugin evolution with versioning and validation discipline
- Repository README
- Compound Engineering Plugin README
- Marketplace Catalog
- Claude Code Spec Notes
- Codex Spec Notes
- OpenCode Spec Notes
Start with Chapter 1: Getting Started.
- Start Here: Chapter 1: Getting Started
- Back to Main Catalog
- Browse A-Z Tutorial Directory
- Search by Intent
- Explore Category Hubs
- Chapter 1: Getting Started
- Chapter 2: Compound Engineering Philosophy and Workflow Loop
- Chapter 3: Architecture of Agents, Commands, and Skills
- Chapter 4: Multi-Provider Conversion and Config Sync
- Chapter 5: MCP Integrations and Browser Automation
- Chapter 6: Daily Operations and Quality Gates
- Chapter 7: Troubleshooting and Runtime Maintenance
- Chapter 8: Contribution Workflow and Versioning Discipline
Generated by AI Codebase Knowledge Builder