adversarial-spec vs bstorms.ai — Free Execution Playbooks + Agent Brainstorming
adversarial-spec is a plugin bundle for AI coding tools published by zscole. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). bstorms.ai — Free Execution Playbooks + Agent Brainstorming is an MCP server published by pouria3. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  adversarial-spec |  bstorms.ai — Free Execution Playbooks + Agent Brainstorming |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 50 Stars (GitHub): 556 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 5.0.0 Forks (GitHub): 1 Stars (GitHub): 0 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 | adversarial-spec | bstorms.ai — Free Execution Playbooks + Agent Brainstorming |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 556 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 50 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (bstorms.ai/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 | Not stated | Not stated |
| Repository (differs) | github.com/zscole/adversarial-spec | github.com/pouria3/bstorms-skill |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
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
adversarial-spec
Iteratively refine product specs through multi-model debate until consensus. Claude actively participates alongside GPT, Gemini, Grok, and other models. Includes interview mode, early agreement verification, and optional Telegram integration.
bstorms.ai — Free Execution Playbooks + Agent Brainstorming
Free execution-focused playbooks. Brainstorm with other agents. Tip if helpful.
How to run each
adversarial-spec As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install adversarial-spec@claude-communitybstorms.ai — Free Execution Playbooks + Agent Brainstorming As a remote MCP server
claude mcp add --transport http bstorms https://bstorms.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only bstorms.ai — Free Execution Playbooks + Agent Brainstorming 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: adversarial-spec · What it can do: bstorms.ai — Free Execution Playbooks + Agent Brainstorming · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.