Ext Ops Panel
Open dashboard
Comparison

spec vs io.github.fathyshalaby/specky

spec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.

spec is a plugin bundle for AI coding tools published by elct9620. No marketplace we read lists it any more. io.github.fathyshalaby/specky is an MCP server published by fathyshalaby. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacespecio.github.fathyshalaby/specky
Community marketplace elct9620/claudekit Removed on 2026-10-24
Version: 0.10.0
Forks (GitHub): 0
Stars (GitHub): 2
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

spec vs io.github.fathyshalaby/specky
Factspecno longer listed · io.github.fathyshalaby/specky
Marketplaces that list it (differs)01
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (www.specky.space/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/elct9620/ai-spec-skillsNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-162026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of spec

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • spec-reviewer

    Specification review: analyze specs for gaps, inconsistencies, and scope estimation

    by Danil Pismenny · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • spec-dd

    Specification-driven development workflow skill. Orchestrates a spec-first discipline with advisory quality gates: a one-page Product Spec (problem, falsifiable bet, success…

    by Florian Buetow · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • spec-engine

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

    by farshidghyasi · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • specops

    Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.

    by sanmak · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • spec-driven-dev

    Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification

    by Daan Ferdinandusse · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • openspec

    OpenSpec workflow management: init, plan, design, develop, review, test, sync, reflect, replan

    by dstoic · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

spec

In its own words, on Community GitHub marketplaces:

A plugin for maintaining project specifications

io.github.fathyshalaby/specky

In its own words, on Official MCP Registry:

Turn raw customer feedback into evidence-cited specs (free, no key) plus 16 PM tools.

How to run each

spec

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.fathyshalaby/specky As a remote MCP server

Claude Code
claude mcp add --transport http specky https://www.specky.space/api/mcp

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

Only io.github.fathyshalaby/specky 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: spec · What it can do: io.github.fathyshalaby/specky · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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