Ext Ops Panel
Open dashboard
Comparison

ai-driven-development vs vibe-extras

ai-driven-development is a plugin bundle for AI coding tools published by CodeAlive-AI. Marketplaces we read that list it: 1 (Community GitHub marketplaces). vibe-extras is a plugin bundle for AI coding tools published by doodledood. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. 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

Where each is published
Marketplaceai-driven-developmentvibe-extras
Community marketplace codealive-ai/ai-driven-development Listed
Version: 10.0.1
Forks (GitHub): 15
Stars (GitHub): 166
Not marked · First seen
Not listed
Community marketplace doodledood/claude-code-plugins Not listed Listed
Version: 2.6.0
Forks (GitHub): 5
Stars (GitHub): 37
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

ai-driven-development vs vibe-extras
Factai-driven-developmentvibe-extras
Marketplaces that list it11
Stars (GitHub) (differs)166 (better)37 (worse)
Forks (GitHub) (differs)15 (better)5 (worse)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2213
LicenceMITMIT
Repository (differs)github.com/codealive-ai/ai-driven-developmentgithub.com/doodledood/claude-code-plugins
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-16

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

ai-driven-development

In its own words, on Community GitHub marketplaces:

An umbrella collection of 23 skills + 1 hook for AI-driven development: agent self-configuration (MCP / hooks / settings / skills / plugins / cross-agent repository readiness / safe CLI installation), engineering practices (maintainable complexity, prompt engineering, FPF problem solving, bug-fix protocol, planning gate, repository-history investigation, repository activity summary, C# refactoring), AI infrastructure (OpenRouter endpoint ranking and routing), research & docs (Semantic Scholar deep research, URL-to-Markdown, ubiquitous-language thesaurus), macOS & Windows health & cleanup, and niche utilities (clipboard, Windows QA). Plus a Claude Code Bash safety hook.

vibe-extras

In its own words, on Community GitHub marketplaces:

Standalone utilities for codebase exploration, web research, git operations, and code maintenance

How to run each

ai-driven-development As a Claude Code plugin

Claude Code
/plugin marketplace add codealive-ai/ai-driven-development
/plugin install ai-driven-development@ai-driven-development

vibe-extras As a Claude Code plugin

Claude Code
/plugin marketplace add doodledood/claude-code-plugins
/plugin install vibe-extras@claude-code-plugins-marketplace

Commands 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: ai-driven-development · What it can do: vibe-extras · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built