spec-interview vs SpecPilot
spec-interview is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑29.
spec-interview is a plugin bundle for AI coding tools published by Leandro Zubrezki. 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-29. 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 leandroz/claude-plugins | Removed on 2026-10-29 Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 15 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 3 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 | spec-interviewno longer listed · | SpecPilot |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 15 | 38 |
| Forks (GitHub) (differs) | 0 | 3 |
| 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 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/leandroz/claude-plugins | github.com/girishr/specpilot |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-26 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-25 |
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-interview
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
An expert-guided skill for creating layered software specification documents for greenfield projects. Produces Vision, Business Requirements, Software Requirements, Architecture…
-
Interview command for fleshing out big feature plans and specifications
-
Spec-driven development methodology with skills for requirements, design, tasks, AI prompting, QA, and troubleshooting
-
Specification review: analyze specs for gaps, inconsistencies, and scope estimation
-
Drive work from written specifications: author and update spec files, derive GitHub issues and epics, break down features and test plans, write product requirements, and refine a…
-
Create and review technical specifications
What each says it does
spec-interview
Multi-round interview to refine a rough SPEC.md into a complete, implementation-ready specification with tasks
SpecPilot
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
How to run each
spec-interview
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: spec-interview · 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.