sickn33/antigravity-awesome-skills/parallel-agents

Native Parallel Agents

Orchestration through Claude Code's built-in Agent Tool

Overview

This skill enables coordinating multiple specialized agents through Claude Code's native agent system. Unlike external scripts, this approach keeps all orchestration within Claude'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 quality
4. frontend-specialist: UI/UX patterns
5. test-engineer: Test coverage
6. Synthesize all findings

Pattern 2: Feature Review

Agents: affected-domain-agents → test-engineer
 
1. Identify affected domains (backend? frontend? both?)
2. Invoke relevant domain agents
3. test-engineer verifies changes
4. Synthesize recommendations

Pattern 3: Security Audit

Agents: security-auditor → penetration-tester → synthesis
 
1. security-auditor: Configuration and code review
2. penetration-tester: Active vulnerability testing
3. Synthesize with prioritized remediation

Agent names and model assignments below are illustrative upstream roles, not bundled definitions or guaranteed built-ins. Discover the actual host tools/installed agents and respect its delegation permissions. Pass the relevant context explicitly, assign disjoint files/worktrees and clear output contracts, and reserve shared edits/integration to one owner. Active testing/deployment never inherits authorization merely from delegation.

Available Agents

Claude Code Built-in Agents

These work alongside custom agents:

Use Explore for quick searches, custom agents for domain expertise.

Synthesis Protocol

After all agents complete, synthesize:

## Orchestration Synthesis
 
### Task Summary
[What was accomplished]
 
### Agent Contributions
| Agent | Finding |
|-------|---------|
| security-auditor | Found X |
| backend-specialist | Identified Y |
 
### Consolidated Recommendations
1.**Critical**: [Issue from Agent A]
2.**Important**: [Issue from Agent B]
3.**Nice-to-have**: [Enhancement from Agent C]
 
### Action Items
-[ ] Fix critical security issue
-[ ] Refactor API endpoint
-[ ] Add missing tests

Best Practices

1. Available agents - Use only roles actually installed or supported by the host
2. Logical order - Discovery → Analysis → Implementation → Testing
3. Share context - Pass relevant findings to subsequent agents
4. Single synthesis - One unified report, not separate outputs
5. Verify changes - Always include test-engineer for code modifications

Key Benefits

• ✅ Coordinated session - Share only relevant context explicitly; inheritance varies by host
• ✅ AI-controlled - Claude orchestrates autonomously
• ✅ Native integration - Works with built-in Explore, Plan agents
• ✅ Resume support - Can continue previous agent work
• ✅ Context passing - Findings flow between agents

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.