tech-spec vs SpecPilot
tech-spec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
tech-spec is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. SpecPilot is an MCP server published by specpilot.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
| Marketplace |  SpecPilot | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.3.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.3.2 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 4 Stars (GitHub): 38 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
| Fact | tech-specno longer listed · | SpecPilot |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 38 |
| Forks (GitHub) (differs) | 5 | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (init.specpilot.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/girishr/specpilot |
| Changes in the last 7 days (differs) | 6 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 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 tech-spec
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.
-
Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification
-
Specification-driven development workflow: setup → specify → plan → tasks → implement
-
Architecture and modernization toolkit: produce a cited architecture document for a locally-cloned repo, and generate a phased modernization plan that auto-runs Documentation mode…
-
Specification-driven development workflow skill. Orchestrates a spec-first discipline with advisory quality gates: a one-page Product Spec (problem, falsifiable bet, success…
-
Write the OpenAPI or AsyncAPI contract before anyone writes a handler.
What each says it does
tech-spec
Writes a typed call-stack architecture handoff: code-shaped contracts plus execution flows, implementation-ready for another engineer. User-invoked only. Not for weighing approaches or deciding the design; use architecture first.
SpecPilot
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
How to run each
tech-spec
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SpecPilot As a remote MCP server
claude mcp add --transport http specpilot https://init.specpilot.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SpecPilot 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: tech-spec · What it can do: SpecPilot · 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.