spec-driven vs ido4specs
spec-driven is a plugin bundle for AI coding tools published by habib0x. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ido4specs is a plugin bundle for AI coding tools published by ido4-dev. 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 |  ido4specs | |
|---|---|---|
| Community marketplace habib0x0/spec-driven-plugin | Listed Version: 5.3.3 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.4.3 Forks (GitHub): 0 Stars (GitHub): 1 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-driven | ido4specs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 10 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | 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 |
| Hooks it runs (differs) | Not published | 3 |
| Parts of the bundle (differs) | 29 | 12 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/habib0x0/spec-driven-plugin | github.com/ido4-dev/ido4specs |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
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-driven
Structured workflow for spec-driven development with EARS notation, guiding features through Requirements, Design, and Tasks phases
ido4specs
ido4specs is the bridge between a strategic spec and GitHub issues. It analyzes your codebase, decomposes capabilities into implementation tasks with effort, risk, type, and dependency metadata, and produces a structurally-validated technical spec any downstream tool can consume. Key features: - Code-grounded decomposition - parallel Explore subagents ground every task in concrete files, services, and patterns from your actual codebase (not fabricated from the spec) - Structured output enforced by a bundled zero-dependency parser - every task carries effort (S/M/L/XL), risk (low → critical), type (feature/infrastructure), AI-suitability (full/assisted/pair/human), and dependency graph - Two-layer validation - deterministic structural parser + independent qualitative review before handoff Built for tech leads, staff engineers, and founder-engineers who want to skip the manual decomposition tax.
How to run each
spec-driven As a Claude Code plugin
/plugin marketplace add habib0x0/spec-driven-plugin
/plugin install spec-driven@spec-drivenido4specs As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ido4specs@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: spec-driven · What it can do: ido4specs · 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.