parallel-agentslisted

# Native Parallel Agents > Orchestration through AIM's built-in Agent Tool ## Overview This skill enables coordinating multiple specialized agents through AIM's native agent system. Unlike external scripts, this approach keeps all orchestration within AIM's control. ## When to Use Orchestration ✅ **Good for:** - Complex tasks requiring multiple expertise domains - Code analysis from security, performance, and quality perspectives - Comprehensive reviews (architecture + security + testing) - Feature implementation needing backend + frontend + database work ❌ **Not for:** - Simple, single-domain tasks - Quick fixes or small changes - Tasks where one agent suffices --- ## Native Agent Invocation ### Single Agent ``` Use the security-auditor agent to review authentication ``` ### Sequential Chain ``` First, use the explorer-agent to discover project structure. Then, use the backend-specialist to review API endpoints. Finally, use the test-engineer to identify test gaps. ``` ### With Context Passing ``` Use the frontend-specialist to analyze React components. Based on those findings, have the test-engineer generate component tests. ``` ### Resume Previous Work ``` Resume agent [agentId] and continue with additional requirements. ``` --- ## Orchestration Patterns ### Pattern 1: Comprehensive Analysis ``` Agents: explorer-agent → [domain-agents] → synthesis 1. explorer-agent: Map codebase structure 2. security-auditor: Security posture 3. backend-specialist: API qual