retro-bot vs strategy-pack
retro-bot is a plugin bundle for AI coding tools published by CR8-OS. Marketplaces we read that list it: 1 (Community GitHub marketplaces). strategy-pack is a plugin bundle for AI coding tools published by kyoon3. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-26. 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 | ||
|---|---|---|
| Community marketplace cometogather/retro-bot | Listed Version: 1.3.0 Forks (GitHub): 0 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.6.1 Forks (GitHub): 0 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 | retro-bot | strategy-pack |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 0 (worse) |
| 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 |
| Parts of the bundle (differs) | 1 | 7 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/cr8-os/retro-bot | github.com/kyoon3/claude-strategy-pack |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-12 |
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
retro-bot
An agile retrospective skill for your Claude collaboration sessions. Capture what you learned. Apply the fix. Make the next session better.
strategy-pack
Two read-only Claude Code subagents designed for solo founders and small teams whose strategy lives in distributed markdown docs. **/business-critic** — daily devil's-advocate. Reads your BUSINESS.md, ROADMAP.md, and recent session log; does live web search for competitor moves and industry news; produces a critique where every doubt cites a URL or a falsifiable experiment. Rotates through seven critique dimensions (positioning, activation gates, monetization, competitive substitution, GTM, founder reality, strategic drift), going deep on three or four per run. No cheerleading. **/pm** — weekly cross-document alignment auditor. Scans BUSINESS.md, ROADMAP.md, every backlog (todo-*.md / BACKLOG-*.md), in-flight plan files, API contract docs, and git log. Flags orphaned commitments ("ROADMAP promised X, no owning task"), blocked-by mismatches across domains, stale plans, and API doc lag. Drafts follow-up plan stubs without ever editing your docs. Both agents are strictly read-only — they produce reports you act
How to run each
retro-bot As a Claude Code plugin
/plugin marketplace add cometogather/retro-bot
/plugin install retro-bot@retro-bot-marketplace
strategy-pack As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install strategy-pack@claude-community
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: retro-bot · What it can do: strategy-pack · 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.