spec vs ido4specs
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. 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-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 |  ido4specs | |
|---|---|---|
| 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 |
| 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 | specno longer listed · | ido4specs |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 1 |
| Forks (GitHub) | 0 | 0 |
| 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) | 6 | 12 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/elct9620/ai-spec-skills | github.com/ido4-dev/ido4specs |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
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.
-
Specification review: analyze specs for gaps, inconsistencies, and scope estimation
-
Specification-driven development workflow skill. Orchestrates a spec-first discipline with advisory quality gates: a one-page Product Spec (problem, falsifiable bet, success…
-
Spec-driven development engine: turns feature specs into working code through structured requirements, wave-based parallel agent execution, and automated quality gates.
-
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.
-
open spec-driven development workflow: OpenSpec, PRPs, Spec Kit, spec-workflow-mcp, BMad-Method, 6A workflow
-
Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification
What each says it does
spec
A plugin for maintaining project specifications
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
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ido4specs 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 · 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.