Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
Orchestration through Claude Code's built-in Agent Tool
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.
✅ Good for:
❌ Not for:
Use the security-auditor agent to review authentication
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.
Use the frontend-specialist to analyze React components.
Based on those findings, have the test-engineer generate component tests.
Resume agent [agentId] and continue with additional requirements.
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
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
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 | Expertise | Trigger Phrases |
|---|---|---|
orchestrator | Pipeline driver | "comprehensive", "multi-phase", "end-to-end" |
explorer | Discovery | "explore", "map", "structure", "find files" |
planner | Architecture/DAG | "plan", "design", "roadmap", "wave" |
researcher | Deep investigation | "research", "investigate", "best practices" |
coder | Implementation | "implement", "build", "code", "write" |
reviewer | Code/plan review | "review", "audit", "check", "OWASP" |
frontend-specialist | UI/React/Next.js | "React", "UI", "components", "Next.js", "CSS" |
debug | Bug fixing | "bug", "error", "not working", "fix" |
workflow-engineer | GitHub Actions | "CI/CD", "workflow", "actions", "deploy" |
doc-writer | Documentation | "write docs", "README", "API docs" |
codebase-maintainer | Cleanup/tech debt | "cleanup", "refactor", "dead code", "tech debt" |
git | Version control | "git", "branch", "PR", "commit" |
arch-linux-expert | Arch Linux | "arch", "pacman", "systemd", "AUR" |
repo-architect | Repo structure | "repo setup", "AI config", "AGENTS.md", "Copilot" |
janitor | Dead code removal | "janitor", "clean", "remove unused", "bloat" |
swe | General engineering | "senior engineer", "direct task", "implement for me" |
qa | Test planning | "QA", "test plan", "bug hunt", "test coverage" |
These work alongside custom agents:
| Agent | Model | Purpose |
|---|---|---|
| Explore | Haiku | Fast read-only codebase search |
| Plan | Sonnet | Research during plan mode |
| General-purpose | Sonnet | Complex multi-step modifications |
Use Explore for quick searches, custom agents for domain expertise.
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