agentleFS
xenitV1xenitV1/Antigravity-Workflows/skills/parallel-agents/SKILL.md

parallel-agents

Skill130 starsChanged 10 months agoMITView on GitHub

Native multi-agent orchestration using Claude Code's Agent Tool. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 126
  2. Distinctive:

    After all agents complete, synthesize:

    line 132
  3. Distinctive:

    Verify changes: - Always include test-engineer for code modifications

    line 165

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

AgentExpertiseTrigger Phrases
orchestratorCoordination"comprehensive", "multi-perspective"
security-auditorSecurity"security", "auth", "vulnerabilities"
penetration-testerSecurity Testing"pentest", "red team", "exploit"
backend-specialistBackend"API", "server", "Node.js", "Express"
frontend-specialistFrontend"React", "UI", "components", "Next.js"
test-engineerTesting"tests", "coverage", "TDD"
devops-engineerDevOps"deploy", "CI/CD", "infrastructure"
database-architectDatabase"schema", "Prisma", "migrations"
mobile-developerMobile"React Native", "Flutter", "mobile"
api-designerAPI Design"REST", "GraphQL", "OpenAPI"
debuggerDebugging"bug", "error", "not working"
explorer-agentDiscovery"explore", "map", "structure"
documentation-writerDocumentation"write docs", "create README", "generate API docs"
performance-optimizerPerformance"slow", "optimize", "profiling"
project-plannerPlanning"plan", "roadmap", "milestones"
seo-specialistSEO"SEO", "meta tags", "search ranking"
game-developerGame Development"game", "Unity", "Godot", "Phaser"

Claude Code Built-in Agents

These work alongside custom agents:

AgentModelPurpose
ExploreHaikuFast read-only codebase search
PlanSonnetResearch during plan mode
General-purposeSonnetComplex 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

  1. Available agents - 17 specialized agents can be orchestrated
  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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.