Compound Engineering is an AI-powered autonomous engineering pipeline that takes a software task from vague idea to shipped PR: it clarifies requirements, plans implementation, writes and tests code, simplifies and reviews changes, commits with conventional messages, opens PRs with value-first descriptions, and monitors CI until green. It also handles code review, debugging, documentation, and optimization workflows.
npx claudepluginhub everyinc/compound-engineering-pluginBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Build and test iOS apps on simulator using XcodeBuildMCP. Use after making iOS code changes, before creating a PR, or when verifying app behavior and checking for crashes on simulator.
Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", or "consolidate overlapping docs", or when ce-compound flags an older doc as superseded. Do not trigger for general refactor, debugging, or code-review work unless the user has explicitly pointed at docs/solutions/.
AI skills that make each unit of engineering work easier than the last.
Each unit of engineering work should make subsequent units easier -- not harder.
Traditional development accumulates technical debt. Every feature adds complexity. Every bug fix leaves behind a little more local knowledge that someone has to rediscover later. The codebase gets larger, the context gets harder to hold, and the next change becomes slower.
Compound engineering inverts this. 80% is in planning and review, 20% is in execution:
/ce-brainstorm and /ce-plan/ce-code-review and /ce-doc-review/ce-compoundThe point is not ceremony. The point is leverage. A good brainstorm makes the plan sharper. A good plan makes execution smaller. A good review catches the pattern, not just the bug. A good compound note means the next agent does not have to learn the same lesson from scratch.
Learn more
/ce-strategy is upstream of the loop -- it captures the product's target problem, approach, persona, metrics, and tracks as a short durable anchor at STRATEGY.md. Ideate, brainstorm, and plan read it as grounding when present, so strategy choices flow into feature conception, prioritization, and spec.
The core loop is: brainstorm the requirements, plan the implementation, work through the plan, review the result, compound the learning, then repeat with better context.
Use /ce-ideate before the loop when you want the agent to generate and critique bigger ideas before choosing one to brainstorm. It produces a ranked ideation artifact, not requirements, plans, or code.
| Skill | Purpose |
|---|---|
/ce-strategy | Create or maintain STRATEGY.md -- the product's target problem, approach, persona, key metrics, and tracks. Read as grounding by ideate, brainstorm, and plan |
/ce-ideate | Optional big-picture ideation: generate and critically evaluate grounded ideas, then route the strongest one into brainstorming |
/ce-brainstorm | Interactive Q&A to think through a feature or problem and write a right-sized requirements doc before planning |
/ce-plan | Turn feature ideas into detailed implementation plans |
/ce-work | Execute plans with worktrees and task tracking |
/ce-debug | Systematically reproduce failures, trace root cause, and implement fixes |
/ce-code-review | Multi-agent code review before merging |
/ce-compound | Document learnings to make future work easier |
/ce-product-pulse | Generate a single-page, time-windowed pulse report on usage, performance, errors, and followups. Saves to docs/pulse-reports/ |
/ce-product-pulse is the read-side companion -- a time-windowed report on what users actually experienced and how the product performed over a given window (24h, 7d, etc.), saved to docs/pulse-reports/ so past pulses form a browseable timeline of user outcomes. The next strategy update and the next brainstorm get real signal to anchor to.
Each cycle compounds: brainstorms sharpen plans, plans inform future plans, reviews catch more issues, patterns get documented.
A typical cycle starts by turning a rough idea into a requirements doc, then planning from that doc before handing execution to /ce-work:
/ce-brainstorm "make background job retries safer"
/ce-plan docs/brainstorms/background-job-retry-safety-requirements.md
/ce-work
/ce-code-review
/ce-compound
For a focused bug investigation:
/ce-debug "the checkout webhook sometimes creates duplicate invoices"
/ce-code-review
/ce-compound
After installing, run /ce-setup in any project. It checks repo-local config, reports optional tool capabilities, and helps keep machine-local CE settings safely gitignored.
The compound-engineering plugin currently ships 27 skills and 0 standalone agents. Specialist review, research, and workflow behavior lives inside the owning skills as skill-local prompt assets.
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 claimPersonalized coding tutorials that use your actual codebase for examples with spaced repetition quizzes
EveryIncAI-powered development tools for code review, research, design, and workflow automation.
EveryIncKnowledge compounds. Brainstorm, plan, review, execute, and save what you learn — so the next cycle starts smarter. 6 skills, 5 agents.
EveryIncA focused kit of feedback-first writing review skills for stress-testing drafts, arguments, pacing, clarity, and line-level prose.
EveryIncAgent-native PowerPoint manipulation. One CLI (deck.py) lets agents inspect, edit, create, and verify .pptx files through atomic JSON patches — with self-correcting errors, deterministic geometry repair, and built-in visual verification.
EveryIncAI-powered development tools for code review, research, design, and workflow automation.
EveryIncAnalyze completed development work to identify automation, systematization, and delegation opportunities. Build compounding engineering systems.
aviflombaumCompound Engineering workflow: PRD-driven sprints, isolated worktrees, hook-enforced safety, automated learning. Skills become /vini-workflow:plan, /vini-workflow:compound, etc.
vinicius91carvalhoSpec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
jsegovVGV Wingspan - AI-native workflows following Very Good Ventures best practices.
VeryGoodOpenSourcePlan and autonomously build a software task end-to-end. Recons the codebase, applies preloaded memory, decomposes into the right number of phases, gets one confirmation, then prepares a single ready-to-paste /goal command — one paste between you and done — that drives execution to completion with built-in retry, fix-spec recovery, and per-phase memory writeback. Works on Claude Code and Codex.
robzilla1738