parallel-agents

Q: How do I install parallel-agents?

Run npx skills add https://github.com/sickn33/agentic-awesome-skills --skill parallel-agents in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/parallel-agents/ (personal) or .claude/skills/parallel-agents/ (project).

by sickn33AI & Agents

Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.

Installs: 708
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/sickn33/agentic-awesome-skills --skill parallel-agents

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads parallel-agents automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

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 - Use only roles actually installed or supported by the host
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

✅ 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.

FAQ

What does the parallel-agents skill do?

Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.

How do I install parallel-agents?

Run npx skills add https://github.com/sickn33/agentic-awesome-skills --skill parallel-agents in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/parallel-agents/ (personal) or .claude/skills/parallel-agents/ (project).

Which AI agents can use parallel-agents?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is parallel-agents safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains parallel-agents?

It is published by sickn33 in sickn33/agentic-awesome-skills. It has 708 recorded installs.