superpowers-multi

Superpowers Multi

A fork of obra/superpowers.

For the core concepts, workflow, skills library, and design philosophy, see the upstream README.

What This Fork Adds

Multi-AI Code Review Dispatch

Adds a configurable mechanism to dispatch code reviews to different AI providers (Codex CLI, Claude Code, etc.). The provider is selected via review_provider in either ${XDG_CONFIG_HOME:-~/.config}/superpowers/review-config.json (user global; recommended for personal defaults) or .superpowers/review-config.json (project; overrides global per-project). Both files are optional; when both exist, project keys override global by key — with coding.rules as the documented exception (merged by category; see below). Provider definitions live in skills/requesting-code-review/providers/*.json. Falls back to host-AI subagents when the configured provider is unavailable.

• requesting-code-review — reviews dispatch to the configured provider with automatic host-AI fallback
• subagent-driven-development — both stages of the two-stage review (spec compliance + code quality) and the final whole-implementation review go through the same dispatch. Final review uses git merge-base for stable diff boundaries
• executing-plans — batch review checkpoint every 3 tasks via superpowers-multi:requesting-code-review
• Provider-agnostic templates — review-prompt.md (code quality) and spec-review-prompt.md (spec compliance) replace the previous Codex/Claude-specific pair

Multi-AI Coding Dispatch

Routes implementation tasks to AI providers by task category, so frontend and backend work can be handled by different providers. Configured via the coding key in the same review-config.json files described above (global at ${XDG_CONFIG_HOME:-~/.config}/superpowers/, project at <repo>/.superpowers/). The coding.rules array merges by category: a project override of backend keeps the global frontend entry intact. An empty rules: [] in the project config explicitly disables global rules for that project.

{
  "review_provider": "codex",
  "coding": {
    "enabled": true,
    "default_provider": "codex",
    "rules": [
      { "category": "frontend", "provider": "claude-code" },
      { "category": "backend", "provider": "codex" }
    ]
  }
}

• subagent-driven-development — before the host implementer runs, each task is classified (frontend / backend / fullstack) via plan tag or AI auto-classification, then routed to the configured provider. Results are validated (file changes, non-empty output, no timeout) before passing into the existing two-stage review. On failure or when disabled, falls back to the existing host implementer
• writing-plans — plan tasks can include an optional category: field that overrides auto-classification
• Provider-agnostic coding template — coding-prompt.md is used by all providers; provider JSON files may add invoke_coding / plugin_override_coding for coding-specific CLI args
• Backward compatible — when the coding block is absent or coding.enabled is false, the existing implementer flow is unchanged. (coding.enabled defaults to true when omitted from a coding block, so configs that only set default_provider or rules remain active.)

Prerequisites

Works out of the box with no additional dependencies. For enhanced multi-AI dispatch:

• Codex Plugin (recommended): When the Codex plugin for Claude Code is installed, reviews and coding tasks can be dispatched via Codex for an independent perspective. Without the plugin, both fall back to host-AI subagents (fully functional).
• Optional global config at ${XDG_CONFIG_HOME:-~/.config}/superpowers/review-config.json (recommended for personal defaults across all projects) and/or project config at .superpowers/review-config.json (overrides global per-project). Both are optional. Without either, the system prompts to set one up the first time it runs and asks where to save (global / project / session-only).

Installation

Claude Code

Register the marketplace, then install the plugin:

/plugin marketplace add undrthemt/superpowers-multi

/plugin install superpowers-multi@superpowers-multi

To update:

/plugin marketplace update superpowers-multi

/plugin install superpowers-multi@superpowers-multi

/plugin install reads from the local marketplace clone, not from GitHub directly, so the marketplace clone must be updated first. /reload-plugins only reloads the currently-installed version — it does not fetch new releases.