weave vs workflow-orchestrator
weave is a plugin bundle for AI coding tools published by AlphaBravo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). workflow-orchestrator is a plugin bundle for AI coding tools published by Nadav Barkai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace alphabravo-oss/guild | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Community marketplace barkain/claude-code-workflow-orchestration | Not listed | Listed Version: 2.1.1 Forks (GitHub): 14 Stars (GitHub): 87 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | weave | workflow-orchestrator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 87 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 14 (better) |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | 10 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/alphabravo-oss/guild | github.com/barkain/claude-code-workflow-orchestration |
| Changes in the last 7 days (differs) | 3 | 2 |
| First seen | 2026-10-15 | 2026-10-15 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
weave
Generate really good dynamic Workflow scripts on demand. /weave:make <task> classifies the task into an orchestration archetype (understand / design / review / research / migrate / generic), picks the right fan-out topology — pipeline by default, a barrier only when one stage genuinely needs all prior results — and authors a self-contained Workflow script that obeys the Workflow tool's hard rules: pure-literal meta block, schema'd agent returns instead of text parsing, .filter(Boolean) after fan-out, adversarial-verify for findings, loop-until-dry / loop-until-budget for unknown-size work, isolation:'worktree' only for parallel file mutation, budget loops guarded on budget.total, no Date.now/Math.random. Every script passes `node --check` and a 12-point self-audit before it is saved to .claude/workflows/ or run. Saved workflows are parameterized over args, so they're reusable — run now with --run, run later by name, or edit and re-run. Running is opt-in; authoring and saving are not.
workflow-orchestrator
Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code
How to run each
weave As a Claude Code plugin
/plugin marketplace add alphabravo-oss/guild
/plugin install weave@guildworkflow-orchestrator As a Claude Code plugin
/plugin marketplace add barkain/claude-code-workflow-orchestration
/plugin install workflow-orchestrator@barkain-pluginsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: weave · What it can do: workflow-orchestrator · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.