Skip to content

charlieviettq/awesome-agent-skill / .claude/skills/dispatching-parallel-agents

dispatching-parallel-agents

Verified

Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files.

Dispatching parallel agents

Gate (required)

Use this skill only if:

  • User or parent explicitly allows parallel subagents, and
  • Tasks are independent (no shared files, no ordering dependency on partial output)

If either condition fails, use sequential incremental-implementation instead.

When to use

  • Independent reviews (security + tests + API contract) on the same commit
  • Parallel research spikes with separate output files
  • Large plan with disjoint file ownership per task

When not to use

  • Single shared module being edited by multiple agents
  • Database migrations or sequential deploy steps
  • User did not approve multi-agent execution

Workflow

  1. Partition — list tasks with disjoint Files: sets
  2. Brief — each agent gets scope, constraints, verify command, output format
  3. Dispatch — run parallel agents; cap concurrency to what the harness supports
  4. Collect — gather outputs without assuming correctness
  5. Integrate — parent reconciles conflicts, runs full verification, single commit strategy per user rules

Integration checklist

  • No conflicting edits to the same paths
  • Combined diff reviewed by parent (or requesting-code-review)
  • Full test/lint suite on integrated result
  • User informed of what each agent did

Anti-patterns

  • Parallel implementers on the same feature branch without file boundaries
  • Merging subagent output without reading diffs
  • Spawning agents to avoid reading the codebase

Related

subagent-driven-development, incremental-implementation, requesting-code-review, verify-before-done

Orchestration patterns inspired by obra/superpowers (MIT).

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall