Skip to main content

Slash command: Run Superpowers Plan Parallel

Posted on · Updated

Superseded. Use Slash command: Implement Plan instead. The new command reads the dependency graph from the task index that Slash command: Write Plan writes, so it does not make its own batches. After the run, group the changes with Skill: Prepare commits.

Prerequisites

Superpowers is an agentic skills framework & software development methodology that works.

https://github.com/obra/superpowers

Content

run-plan-parallel.mdmd
---
description: Implement a plan with MULTIPLE parallel agents via Superpowers (no commits)
argument-hint: [path to plan file] [agent count — optional, default: auto]
allowed-tools: Read, Glob, Grep, Edit, Write, TodoWrite, Task, Bash(git status:*), Bash(git diff:*)
---

Implement this plan file using MULTIPLE parallel subagents: $1

This command is explicitly multi-agent. Do not run the plan single-threaded.

## Execution strategy

1. Read the plan and break it into batches the way Superpowers normally would.
2. Build a dependency graph of the batches: which depend on which, and which files/modules each one touches.
3. Choose the agent count:
   - If $2 is given, fan out across that many agents.
   - Otherwise (auto), use one agent per independent batch, capped at a sensible max (~4–6).
4. Dispatch independent batches to parallel subagents via the Task tool. Rules:
   - Each agent owns a DISJOINT set of files — no two agents may edit the same file.
   - Batches that share files or depend on another batch's output run AFTER their dependency, in a later wave — never in the same parallel wave.
   - If the plan turns out to be one indivisible chain with no parallelism available, say so explicitly, then execute it as a single agent rather than forcing a useless split.
5. Run in waves: dispatch a wave of independent agents, wait for all to return, then dispatch the next wave whose dependencies are now satisfied.
6. Each subagent implements its batch with TDD where applicable (tests fail first → implement → refactor), then lints and formats only its own changes.
7. After all waves complete, run the code-reviewer agent ONCE over the combined result — implementation vs plan, coding standards, architecture, and the integration between the parallel pieces. Resolve findings before finishing.

## Constraints

- Work directly on the main branch
- Do NOT commit any changes
- Never let two agents write the same file concurrently — serialize on any conflict

## Report

- The batch dependency graph and how you assigned work to waves/agents
- What each agent did (its batch + the files it owned)
- Code-reviewer findings and any follow-ups