spec-driven vs StoriesOnBoard - structured specifications for AI Agents
spec-driven is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
spec-driven is a plugin bundle for AI coding tools published by Anton Haskevych. No marketplace we read lists it any more. StoriesOnBoard - structured specifications for AI Agents is an MCP server published by storiesonboard.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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 | ||
|---|---|---|
| Community marketplace anton-haskevych/spec-driven | Removed on 2026-10-17 Version: 2.48.0 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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-drivenno longer listed · | StoriesOnBoard - structured specifications for AI Agents |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.storiesonboard.com/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) | 23 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/anton-haskevych/spec-driven | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-26 |
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-driven
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Specification-driven development workflow: setup → specify → plan → tasks → implement
-
Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification
-
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…
-
Specification Driven Development workflow commands and agents, based on Github Spec Kit and OpenSpec. Uses specialized agents for effective context management and quality review.
-
Skills-first specification-driven development - automatic spec creation, lifecycle management, progress tracking, and PR generation with Agent Skills
What each says it does
spec-driven
Spec-driven development toolkit: create, review, and iterate on feature specifications with an expert review panel.
StoriesOnBoard - structured specifications for AI Agents
Turn PRDs and product ideas into structured specs so coding agents build your intent, not theirs.
How to run each
spec-driven
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
StoriesOnBoard - structured specifications for AI Agents As a remote MCP server
claude mcp add --transport http storiesonboard https://api.storiesonboard.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only StoriesOnBoard - structured specifications for AI Agents 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-driven · What it can do: StoriesOnBoard - structured specifications for AI Agents · 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.