
Compound Engineering Core
- 1 repo stars
- Updated July 9, 2026
- adam-badar/compound-engineering-system
Shared planning, execution, and review-gate workflows for a compound-engineering development process.
About
The core of a compound-engineering system for Claude Code. It provides shared planning, execution, and review-gate workflows that other plugins build on. It standardizes how engineering work is planned, run, and reviewed across a team's agent workflows.
- Shared planning workflows
- Execution workflows
- Review-gate workflows
- Compound engineering
Compound Engineering Core by the numbers
- Data as of Jul 10, 2026 (Skillselion catalog sync)
/plugin marketplace add adam-badar/compound-engineering-system/plugin install compound-engineering-core@compound-engineering-marketplaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | July 9, 2026 |
| Repository | adam-badar/compound-engineering-system ↗ |
What it does
Shared planning, execution, and review-gate workflows for a compound-engineering development process.
README.md
Compound Engineering Core Plugin
Private plugin for shared compound engineering workflows.
Includes
- Workflow commands:
compound-engineering-core:workflows:brainstormcompound-engineering-core:workflows:researchcompound-engineering-core:workflows:deepen-plancompound-engineering-core:workflows:plancompound-engineering-core:workflows:plan-loopcompound-engineering-core:workflows:debugcompound-engineering-core:workflows:explaincompound-engineering-core:workflows:frontend-validatecompound-engineering-core:workflows:workcompound-engineering-core:workflows:compoundcompound-engineering-core:workflows:epic-delta-loopcompound-engineering-core:workflows:pr-review
- Review and research agents for teammate/research workflows
- Legacy compatibility Codex agent shims for older repos
Notes
- Use plugin-prefixed command names to guarantee you are invoking the shared plugin implementation.
- Agent teams are opt-in per command run via
teams=on. brainstorm,debug, andexplainprovide non-coding workflows for discovery, diagnosis, and decision traceability.brainstormsupports freshness-aware research controls:research=auto|on|off,research_depth=quick|standard|deep, andas_of=YYYY-MM-DD.researchprovides deep-research style investigation with iterative PM Q&A loops and dated evidence capture.deepen-planupgrades an existing plan through targeted research passes and confidence-tracked PM feedback loops.- External Codex gate expects a configured
codex-xhighMCP server. - Codex plan and PR passes are invoked directly by the current Claude agent; dedicated Codex-only Claude sub-agents are no longer the default path.
- Frontend browser validation uses gstack headless Chromium. Install gstack skill at
~/.claude/skills/gstack/and run./setup. - Planning enforces an Epic PR Ladder with per-PR size/test expectations.
- PR review enforces teammate + Codex correctness + Codex edge-case + test/CI gates for code PRs.
frontend-validateprovides the browser-validation gate using gstack persistent headless Chromium.workflows:workauto-runsfrontend-validatewhen a batch touches qualifying frontend/browser validation changes.workflows:pr-reviewfails closed for qualifying PRs when current-SHA frontend validation evidence is missing, stale, or failed.- The two Codex PR passes are both required on the current SHA and are run directly by the current Claude agent by default.
- PR review requires SHA authorization via
approve_sha=<current-head-sha>(auto-supplied when invoked fromworkflows:work). workflows:workauto-runs/re-runs PR review after each pushed SHA on the active PR.workflows:workenforces a post-merge CI/CD confirmation gate on target-branch SHA before continuing to the next slice/closeout.workflows:workauto-runs post-mergeworkflows:compoundafter CI/CD is green, and records created/updated/skipped evidence in the execution tracker.- Non-blockers must be triaged (
implement_now|defer|reject) and cannot be silently ignored. - Default triage artifact is existing gate evidence + execution tracker (no extra todo-file system required).
- Multi-reviewer consensus non-blockers are escalation-candidates and default to promotion unless counterevidence + PM signoff are captured.
Meta-governance
Changes to this plugin (workflow commands, agent definitions, review policies) are themselves subject to the same compound engineering workflow:
- Branch + PR: All changes must go through a feature branch and pull request in the plugin repository, never committed directly.
- PR review: Plugin changes are classified as
code_pr(they affect execution, review, and trust boundaries) and must pass the same teammate + Codex review gates. - Compound capture: Non-trivial changes should produce a
docs/solutions/entry in the consuming repository if the change was motivated by a process failure.
The methodology must enforce itself. If an agent skips these gates for "meta" changes, that is a process violation equivalent to skipping them for application code.