Ext Ops Panel
Open dashboard
Comparison

spec-engine vs Go Spec Reviewer

spec-engine is a plugin bundle for AI coding tools published by farshidghyasi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Go Spec Reviewer is a plugin bundle for AI coding tools published by Steve Francia. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. 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-engineGo Spec Reviewer
Claude Code: claude-plugins-community Listed
Version: 2.3.0
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen
Not listed
Community marketplace spf13/go-skills Not listed Listed
Version: 1.1.0
Forks (GitHub): 38
Stars (GitHub): 698
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-engine vs Go Spec Reviewer
Factspec-engineGo Spec Reviewer
Marketplaces that list it11
Stars (GitHub) (differs)7 (worse)698 (better)
Forks (GitHub) (differs)1 (worse)38 (better)
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)32Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/farshidghyasi/spec-enginegithub.com/spf13/go-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-06

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-engine

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

Spec-driven development engine: turns feature specs into working code through structured requirements, wave-based parallel agent execution, and automated quality gates.

Go Spec Reviewer

In its own words, on Community GitHub marketplaces:

Review Go design documents before implementation begins — catches over-engineering, missing error paths, interface misuse, and Cobra/Viper convention violations while a plan is still cheap to change.

How to run each

spec-engine As a Claude Code plugin

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

Go Spec Reviewer As a Claude Code plugin

Claude Code
/plugin marketplace add spf13/go-skills
/plugin install go-spec-reviewer@go-skills

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-engine · What it can do: Go Spec Reviewer · 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 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