By jbongaarts
Beads-native rewrite of obra's superpowers skills, built around bd for cross-session continuity
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use when backporting or forward-porting commits between long-lived branches (release, LTS, maintenance branches) - enforces scope analysis, correct ordering, target-context verification, and audit tracking before the picked code merges
Use when facing 2 or more independent tasks, failures, or work domains that can proceed concurrently without shared state or sequential dependencies
Use when you have a beads epic of planned issues to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A beads-native rewrite of obra's superpowers skills, built around bd (beads) for cross-session continuity.
The original superpowers skills persist work as markdown plan/spec files and in-session TodoWrite checklists. That works well within a single session but loses state on compaction, restart, or hand-off. bd gives us a local, dependency-aware issue store that survives all of those — so the same workflows can be expressed as graphs of issues that any future session can pick up via bd ready.
This plugin rewrites the skills to use bd as the source of truth for plans, tasks, debugging evidence, code-review feedback, and lessons learned — while keeping the rigor (TDD, verification-before-completion, systematic debugging) of the originals.
The plugin is verified against:
/plugin marketplace add jbongaarts/superpowers-beads. The skill activation matrix is run against this harness on every release.codex plugin marketplace add jbongaarts/superpowers-beads. Same skill source loads via the repo-level .agents/skills symlink. Matrix is run against this harness on every release.Other harnesses (Copilot CLI, Gemini CLI, etc.) may pick up the skills via their own discovery mechanisms but are not actively supported in 1.0. PRs adding cross-harness fixes or smoke coverage are welcome — see CONTRIBUTING.md.
Active. Skills currently shipped:
using-superpowers — entry-point skill explaining how to find and use the othersbrainstorming — turn ideas into approved feature epics in bdwriting-plans — produce a bd epic + child issues from an approved specexecuting-plans — work a bd epic to completion in a single sessionsubagent-driven-development — same-session execution with a fresh subagent per issue and two-stage reviewdispatching-parallel-agents — model parallel work as a bd swarm and dispatch one worker per ready beadusing-git-worktrees — create bd-managed worktrees that share the beads databasetest-driven-development — RED/GREEN/REFACTOR cycle with evidence recorded on bdsystematic-debugging — four-phase root-cause workflow with evidence persisted on the bug beadverification-before-completion — gate every completion claim on fresh verification recorded on the beadrequesting-code-review / receiving-code-review — dispatch and triage reviews with bd as the persistent recordfinishing-a-development-branch — verify, run preflight, integrate, and clean upcherry-picking-across-branches — scope, order, and verify backports / forward-ports between long-lived branches with bd as the audit trailwriting-skills — TDD for skills themselvesOpen work is tracked as bd issues — run bd ready to see what's queued.
Claude Code:
/plugin marketplace add jbongaarts/superpowers-beads
/plugin install superpowers-beads@superpowers-beads
Codex:
codex plugin marketplace add jbongaarts/superpowers-beads
For local checkout or fork testing:
git clone https://github.com/jbongaarts/superpowers-beads.git
cd superpowers-beads
codex plugin marketplace add "$(pwd)"
codex
Codex scans .agents/skills, which links to the shared skill source under
plugins/superpowers-beads/skills. The repository also exposes a Codex plugin
marketplace at .agents/plugins/marketplace.json; restart Codex after
installing or upgrading if newly installed skills do not appear immediately.
For beads-backed persistence:
bd installed and on PATHbd init) or a parent directoryIf bd is not installed, the skills should continue without beads for that
session rather than installing tools or initializing a repository automatically.
If bd is installed but no beads workspace is active, initialization is still
opt-in. See docs/beads-startup.md. See
docs/codex-publishing.md for Codex distribution
details.
The repo includes beads-native workflow formulas in .beads/formulas/.
Use bd formula list to see them, bd cook <name> --dry-run --var title="..." to preview them, and bd mol pour <name> --var title="..." to instantiate a workflow graph.
See docs/formulas.md for the current formula catalog.
npx claudepluginhub jbongaarts/superpowers-beads --plugin superpowers-beadsUltra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Frontend design skill for UI/UX implementation
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Memory compression system for Claude Code - persist context across sessions
Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.