By pjhoberman
Project decomposition and orchestration on top of the compound-engineering plugin. Turns a multi-feature project into a committed, diffable task-graph and drives its nodes through the CE pipeline.
Decompose a large project into a committed, diffable task-graph — a markdown index plus one file per node under docs/plans/, each node tagged with its next CE stage (brainstorm/plan/work) and a model tier, embedding a ready plan when a node is settled or a brief otherwise. Manual-invoke only. Use when starting a multi-feature project you want broken into dependency-mapped, individually-drivable tasks instead of one monolithic plan. Builds on the compound-engineering plugin (ce-plan / ce-brainstorm / ce-work / lfg).
Execute a task-graph's ready work in parallel: sequence the collision-free batches into runtime-safe waves, show a visible preview, and drive each wave's nodes through /lfg in worktree-isolated parallel runs, merging in dependency order and checkpointing recovery state at every wave boundary. Runtime-exclusive nodes run as solo waves. Manual-invoke only. Use when a committed task-graph has multiple ready nodes you want shipped as parallel PRs. Builds on the compound-engineering plugin (ce-work / lfg) and the sibling orch-decompose, orch-next, and recovery-manifest scripts.
Read an orch-decompose task-graph, compute the ready frontier, and recommend the single highest-leverage next move — with a one-line rationale and the exact command — then fire it inline. Manual-invoke only. Use when you have a committed task-graph and want to be told what to do next instead of scanning a list. Builds on the compound-engineering plugin (ce-plan / ce-brainstorm / ce-work / lfg) and the sibling orch-decompose skill.
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 claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Project decomposition and orchestration layered on top of the compound-engineering plugin.
Compound Engineering ships excellent per-feature primitives — ce-plan decomposes one
feature into units, ce-work fans out worktree-isolated sub-agents, lfg runs the full
single-unit pipeline. What it doesn't do is operate one level above a single feature:
nothing decomposes a whole multi-feature project, maps dependencies across tickets, or
tracks where the project stands outside one chat session.
This plugin fills that layer. It is a hard dependency on compound-engineering: its
skills compose CE skills (ce-plan, ce-brainstorm, ce-work, lfg) rather than
reimplement them.
The three skills operate over one durable artifact — a committed, diffable task-graph
under docs/plans/<project-slug>/. Structure lives in git; live status is derived from
git on read, so any session or machine resumes by reading the files.
flowchart TB
P(["project / brainstorm doc"]) --> OD["/orch-decompose<br/>build + audit the task-graph"]
OD --> TG[("task-graph<br/>committed in git;<br/>status derived on read")]
TG --> ON["/orch-next<br/>ready frontier,<br/>recommend one move"]
TG --> OF
subgraph OF["/orch-fanout — runtime-safe parallel waves"]
direction LR
PA["partition:<br/>collision-free batches"] --> WP["wave-plan:<br/>exclusive-runtime<br/>nodes run solo"]
WP --> EX["executor:<br/>worktree /lfg per node,<br/>per-node model tier,<br/>dependency-order merge"]
EX --> CB["circuit breaker:<br/>halt after K<br/>consecutive fails"]
end
ON -.->|drive a node| OF
OF -.->|recovery manifest per wave| TG
In words: /orch-decompose builds the committed task-graph → /orch-next recommends the
single highest-leverage next move → /orch-fanout runs it in parallel waves
(partition → wave-plan → executor → circuit breaker), checkpointing recovery state each wave.
Every skill reads and writes the one task-graph; nothing holds project state in a chat session.
All three are manual-invoke (disable-model-invocation: true).
/orch-decomposeTurns a big project (or a brainstorm/strategy doc) into the committed task-graph: a markdown
index.md plus one file per node. Each node is a feature-sized unit tagged with the CE stage
it next enters (brainstorm / plan / work), a model tier, and exclusive_runtime,
embedding a ce-plan-shaped plan when settled or a brief otherwise.
scripts/graph_compute.py).gh (scripts/reorient.py).ce-plan,
ce-brainstorm, or lfg./orch-nextReads the task-graph, computes the dependency ready frontier, and recommends the single
highest-leverage next move (lowest slack, then most-unblocking) with the exact command to run
it — then fires it. A pure consumer (scripts/frontier.py) of the graph + status JSON.
/orch-fanoutExecutes ready work in runtime-safe parallel waves: partition the ready set into
collision-free batches (scripts/partition.py), sequence them into waves where
exclusive_runtime nodes run solo (scripts/wave_plan.py), show a visible preview, then
drive each wave through /lfg in worktree-isolated runs (reusing ce-work), merging in
dependency order. Recovery state is checkpointed at every wave boundary
(scripts/manifest.py) and reconciled against live git on resume (scripts/reconcile.py); a
circuit breaker (scripts/circuit_breaker.py) halts the run after K consecutive wave failures.
Shared vocabulary (CONCEPTS.md): task-graph, node, stage, model tier,
no_pr node, manual status pin, ready frontier, fan-out batch,
exclusive_runtime, wave, circuit breaker. Learnings captured along the way live in
docs/solutions/.
This plugin is distributed as a Claude Code marketplace. It requires the compound-engineering plugin to be installed as well.
# from GitHub
claude plugin marketplace add pjhoberman/compound-engineering-orchestrator
claude plugin install compound-engineering-orchestrator@compound-engineering-orchestrator
# or from a local checkout (for iterating)
claude plugin marketplace add /path/to/compound-engineering-orchestrator
claude plugin install compound-engineering-orchestrator@compound-engineering-orchestrator
Autonomous experiment loops on any codebase — one file, one metric, one loop. Based on Karpathy's autoresearch pattern.
npx claudepluginhub pjhoberman/compound-engineering-orchestrator --plugin compound-engineering-orchestratorAI-powered development tools for code review, research, design, and workflow automation.
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,640 supported skills.