Ext Ops Panel
Open dashboard
Comparison

work-unit-roadmap vs ai.openhelm/dev-changes

work-unit-roadmap is a plugin bundle for AI coding tools published by truong170201. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ai.openhelm/dev-changes is an MCP server published by openhelm.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacework-unit-roadmapai.openhelm/dev-changes
Claude Code: claude-plugins-community Listed
Version: 2.0.6
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

work-unit-roadmap vs ai.openhelm/dev-changes
Factwork-unit-roadmapai.openhelm/dev-changes
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.openhelm.ai/dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)10Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/truong170201/work-unit-roadmapNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 h ago

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

work-unit-roadmap

In its own words, on Claude Code: claude-plugins-community:

An AI agent workflow for professional software development using roadmap-driven execution, atomic Work Units, verification evidence, and one verified commit per completed unit. It helps AI coding agents plan, implement, test, review, and recover work with clean Git history, strict scope control, and full traceability across every phase.

ai.openhelm/dev-changes

In its own words, on Official MCP Registry:

Turn described changes into reviewed pull requests: propose, triage, review, dependency audits.

How to run each

work-unit-roadmap As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install work-unit-roadmap@claude-community

ai.openhelm/dev-changes As a remote MCP server

Claude Code
claude mcp add --transport http dev-changes https://mcp.openhelm.ai/dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.openhelm/dev-changes has a remote endpoint we check. How we check endpoints

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: work-unit-roadmap · What it can do: ai.openhelm/dev-changes · 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. 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