Ext Ops Panel
Open dashboard
Comparison

Design vs spec-driven

Design is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). spec-driven is a plugin bundle for AI coding tools published by Anton Haskevych. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplaceDesignspec-driven
Claude: knowledge-work-plugins Listed
Version: 1.2.0
Forks (GitHub): 3 345
Stars (GitHub): 29 497
Not marked · First seen
Not listed
Community marketplace anton-haskevych/spec-driven Not listed Listed
Version: 2.48.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

Design vs spec-driven
FactDesignspec-driven
Marketplaces that list it11
Stars (GitHub) (differs)29 497No figure on GitHub
Forks (GitHub) (differs)3 345No figure on GitHub
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1623
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/anton-haskevych/spec-driven
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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

Design

In its own words, on Claude: knowledge-work-plugins:

Accelerate design workflows — critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs.

spec-driven

In its own words, on Community GitHub marketplaces:

Spec-driven development toolkit: create, review, and iterate on feature specifications with an expert review panel.

How to run each

Design As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install design@knowledge-work-plugins

spec-driven As a Claude Code plugin

Claude Code
/plugin marketplace add anton-haskevych/spec-driven
/plugin install spec-driven@spec-driven-marketplace

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: Design · What it can do: spec-driven · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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