harness-designing-plugin vs MCP Task Orchestrator
harness-designing-plugin is a plugin bundle for AI coding tools published by BilLogic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-17. 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 |  harness-designing-plugin |  MCP Task Orchestrator |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 3.0.0 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.16.0 Forks (GitHub): 24 Stars (GitHub): 208 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:eab0bb62611a Forks (GitHub): 24 Stars (GitHub): 208 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 | harness-designing-plugin | MCP Task Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 5 (worse) | 208 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 24 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.context7.com/mcp) | On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 42 |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 0 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/billogic/harness-designing-plugin | github.com/jpicklyk/task-orchestrator |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
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
harness-designing-plugin
Harness Designing Plugin helps design teams turn their scattered AI setup — Notion prompts, Figma comments, AGENTS.md rules, chat histories — into a five-layer design harness that compounds across sessions and rotations. Four skills walk you through the assembly: • /hd:learn — Q&A about the five-layer concept (Context Engineering, Skill Curation, Workflow Orchestration, Rubric Setting, Knowledge Compounding) • /hd:setup — detects existing harness artifacts, pre-analyzes all five layers in parallel (5× harness-auditor + rubric-recommender), then walks you through link / critique / scaffold / skip per layer • /hd:maintain — captures lessons and promotes them to team rules in AGENTS.md with SHA-256 plan-hash proof-of-consent • /hd:review — audits harness health in a 2-batch parallel dispatch (5 layer-specialist agents + 2–3 context agents); critiques harness artifacts against quality rubrics Ships 9 sub-agents and 14 starter rubrics (distilled from pbakaus/impeccable, Nielsen's 10 heuristics, Material 3, Fluent
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
How to run each
harness-designing-plugin As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install harness-designing-plugin@claude-communityMCP Task Orchestrator As a local MCP server: Docker image
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only harness-designing-plugin has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of harness-designing-plugin publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of harness-designing-plugin publish no settings it asks for, so we do not compare settings.
What it can do: harness-designing-plugin · What it can do: MCP Task Orchestrator · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.