parallel-agents
Coordinate multiple specialized agents through native orchestration to handle complex, multi-domain coding tasks.
Install
mkdir -p .claude/skills/parallel-agents && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/776" && unzip -o skill.zip -d .claude/skills/parallel-agents && rm skill.zipInstalls to .claude/skills/parallel-agents
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.Key capabilities
- →Coordinate multiple specialized agents within a single session
- →Pass context and findings between different domain agents
- →Resume previous agent work using unique identifiers
- →Synthesize findings from multiple perspectives into a single report
- →Execute sequential chains of domain-specific tasks
How it works
The skill uses Claude Code's native agent system to invoke specialized agents in a logical order, sharing context across the session to produce a unified output.
Inputs & outputs
When to use parallel-agents
- →Comprehensive code review
- →Feature implementation requiring full-stack changes
- →Complex system analysis
About this skill
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
Available Agents
| Agent | Expertise | Trigger Phrases |
|---|---|---|
orchestrator | Coordination | "comprehensive", "multi-perspective" |
security-auditor | Security | "security", "auth", "vulnerabilities" |
penetration-tester | Security Testing | "pentest", "red team", "exploit" |
backend-specialist | Backend | "API", "server", "Node.js", "Express" |
frontend-specialist | Frontend | "React", "UI", "components", "Next.js" |
test-engineer | Testing | "tests", "coverage", "TDD" |
devops-engineer | DevOps | "deploy", "CI/CD", "infrastructure" |
database-architect | Database | "schema", "Prisma", "migrations" |
mobile-developer | Mobile | "React Native", "Flutter", "mobile" |
api-designer | API Design | "REST", "GraphQL", "OpenAPI" |
debugger | Debugging | "bug", "error", "not working" |
explorer-agent | Discovery | "explore", "map", "structure" |
documentation-writer | Documentation | "write docs", "create README", "generate API docs" |
performance-optimizer | Performance | "slow", "optimize", "profiling" |
project-planner | Planning | "plan", "roadmap", "milestones" |
seo-specialist | SEO | "SEO", "meta tags", "search ranking" |
game-developer | Game Development | "game", "Unity", "Godot", "Phaser" |
Claude Code Built-in Agents
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.
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
- Available agents - 17 specialized agents can be orchestrated
- Logical order - Discovery → Analysis → Implementation → Testing
- Share context - Pass relevant findings to subsequent agents
- Single synthesis - One unified report, not separate outputs
- Verify changes - Always include test-engineer for code modifications
Key Benefits
- ✅ Single session - All agents share context
- ✅ 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
When not to use it
- →Simple, single-domain tasks
- →Quick fixes or small changes
- →Tasks where one agent is sufficient
Limitations
- →Requires logical ordering of agents for effective results
- →Synthesis protocol must be followed for consolidated reporting
How it compares
This approach keeps orchestration within the assistant's control rather than relying on external scripts to manage agent workflows.
Compared to similar skills
parallel-agents side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| parallel-agents (this skill) | 6 | 6mo | No flags | Intermediate |
| rp-eng-review | 0 | 2mo | No flags | Intermediate |
| multi-agent-brainstorming | 1 | 4mo | No flags | Intermediate |
| architect-review | 109 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by davila7
View all by davila7 →You might also like
rp-eng-review
ryan-papa
[5] 엔지 리뷰. Codex-led 5항목 점수제 독립 리뷰. Use when Codex should run or follow the harness rp-eng-review stage, or when the user invokes /rp-eng-review, $rp-eng-review, or asks for this workflow step.
multi-agent-brainstorming
sickn33
Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.
architect-review
sickn33
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.