Ext Ops Panel
Open dashboard
Comparison

spec-driven vs tk

spec-driven is a plugin bundle for AI coding tools published by Anton Haskevych. Marketplaces we read that list it: 1 (Community GitHub marketplaces). tk is a plugin bundle for AI coding tools published by helderberto. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
Marketplacespec-driventk
Community marketplace anton-haskevych/spec-driven Listed
Version: 2.48.0
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.19.5
Forks (GitHub): 0
Stars (GitHub): 10
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

spec-driven vs tk
Factspec-driventk
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub10
Forks (GitHub) (differs)No figure on GitHub0
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)235
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/anton-haskevych/spec-drivengithub.com/helderberto/tracerkit
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-12

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

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.

tk

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

Spec-driven workflow for AI coding agents: PRD, plan, check, and archive features using tracer-bullet vertical slices.

How to run each

spec-driven As a Claude Code plugin

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

tk As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tk@claude-community

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

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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