Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Dispatching Parallel Agents
## Overview
You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.
**Core principle:** Dispatch one agent per independent problem domain. Let them work concurrently.
## When to Use
```dot
digraph when_to_use {
"Multiple failures?" [shape=diamond];
"Are they independent?" [shape=diamond];
"Single agent investigates all" [shape=box];
"One agent per problem domain" [shape=box];
"Can they work in parallel?" [shape=diamond];
"Sequential agents" [shape=box];
"Parallel dispatch" [shape=box];
"Multiple failures?" -> "Are they independent?" [label="yes"];
"Are they independent?" -> "Single agent investigates all" [label="no - related"];
…
The line at the top of this page pins the label git:20260815.6743039, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_3bfghr3qzrtahxa2
GET https://markdownregistry.com/api/v1/resolve?ref=takaakit/superpowers-uml/dispatching-parallel-agents
GET https://markdownregistry.com/api/v1/blob/5b3666a801bc21a43dc53c2c92d29b04aa994b6926c105f5e831bf48f3825e66
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
takaakit/superpowers-uml · plugins/superpowers-uml/skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
takaakit/superpowers-uml · plugins/superpowers-uml/skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
takaakit/superpowers-uml · plugins/superpowers-uml/skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
takaakit/superpowers-uml · plugins/superpowers-uml/skills/subagent-driven-development/SKILL.md · Use when executing implementation plans with independent tasks in the current session
takaakit/superpowers-uml · plugins/superpowers-uml/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
takaakit/superpowers-uml · plugins/superpowers-uml/skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
takaakit/superpowers-uml · plugins/superpowers-uml/skills/using-git-worktrees/SKILL.md · Use when starting feature work that needs isolation from current workspace or before executing implementation plans -…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/using-superpowers/SKILL.md · Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/writing-plans/SKILL.md · Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
a5c-ai/babysitter · library/methodologies/superpowers/skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
ganyuanran/aegis · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential…
coco-research/coco · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
jamditis/claude-skills-journalism · superjawn/skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
ibrahim-3d/orchestrator-supaconductor · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies