dispatching-parallel-agents
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
More from grnfromdark/autodevskill
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
22auto-dev
>
21systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
21requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
21subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
21brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
20