interview vs spec-to-code
interview is a plugin bundle for AI coding tools published by duyet. Marketplaces we read that list it: 1 (Community GitHub marketplaces). spec-to-code is a plugin bundle for AI coding tools published by vkroz. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-21. 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
| Marketplace |  spec-to-code | |
|---|---|---|
| Community marketplace duyet/codex-claude-plugins | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 15 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | interview | spec-to-code |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 15 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | 15 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/duyet/codex-claude-plugins | github.com/vkroz/spec-to-code |
| Changes in the last 7 days (differs) | 6 | 0 |
| First seen (differs) | 2026-10-16 | 2026-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
interview
Interview the user to clarify requirements, then write a spec.
spec-to-code
Accelerates software delivery by automating SDLC stages inside Claude Code — Claude facilitates writing specs and designing architecture, then autonomously builds implementation plans, implements and tests the product — all driven by 13 structured /stc:* commands with built-in review gates and document consistency.
How to run each
interview As a Claude Code plugin
/plugin marketplace add duyet/codex-claude-plugins
/plugin install interview@duyet-claude-pluginsspec-to-code As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install spec-to-code@claude-communityCommands 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: interview · What it can do: spec-to-code · 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.