Ext Ops Panel
Open dashboard
Comparison

workflow-orchestrator vs claude-taskflow

workflow-orchestrator is a plugin bundle for AI coding tools published by Nadav Barkai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). claude-taskflow is a plugin bundle for AI coding tools published by heggria. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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

Where each is published
Marketplaceworkflow-orchestratorclaude-taskflow
Community marketplace barkain/claude-code-workflow-orchestration Listed
Version: 2.1.1
Forks (GitHub): 14
Stars (GitHub): 87
Not marked · First seen
Not listed
Community marketplace heggria/taskflow Not listed Listed
Version: 1.0.0
Forks (GitHub): 11
Stars (GitHub): 78
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

workflow-orchestrator vs claude-taskflow
Factworkflow-orchestratorclaude-taskflow
Marketplaces that list it11
Stars (GitHub) (differs)87 (better)78 (worse)
Forks (GitHub) (differs)14 (better)11 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (claude-taskflow)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)102
LicenceMITMIT
Repository (differs)github.com/barkain/claude-code-workflow-orchestrationgithub.com/heggria/taskflow
Changes in the last 7 days22
First seen (differs)2026-10-152026-10-20

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

workflow-orchestrator

In its own words, on Community GitHub marketplaces:

Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code

claude-taskflow

In its own words, on Community GitHub marketplaces:

Multi-phase subagent orchestration for Claude Code: 20 taskflow_* MCP tools (run/runs/resume/version/list/show/verify/compile/lint/plan/analytics/peek/trace/replay/why_stale/why_effect/recompute/reconcile_workspace/save/search) plus a routing skill. Background runs support status/wait/cancel; compile returns SVG + text outline. The server runs via npx (claude-taskflow).

How to run each

workflow-orchestrator As a Claude Code plugin

Claude Code
/plugin marketplace add barkain/claude-code-workflow-orchestration
/plugin install workflow-orchestrator@barkain-plugins

claude-taskflow As a Claude Code plugin

Claude Code
/plugin marketplace add heggria/taskflow
/plugin install claude-taskflow@taskflow

Commands 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: workflow-orchestrator · What it can do: claude-taskflow · 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.

Where the data comes from: how the catalog is built