parallel-agents_skill

Overview

This skill coordinates multiple specialized agents to run in parallel or sequence for multi-domain tasks. It keeps orchestration native to the system so agents share context in a single session. Use it to combine discovery, domain analysis, testing, and synthesis into one cohesive workflow.

How this skill works

You invoke built-in or custom agents by trigger phrases or explicit agent IDs, then define an orchestration pattern (parallel, sequential, or context-passing). The explorer agent can map the codebase, domain agents perform focused analyses, and a final synthesis step consolidates findings into prioritized recommendations and action items. Sessions can be resumed and context passed from one agent to the next to maintain continuity.

When to use it

• When a task needs expertise from multiple domains (security, backend, frontend, testing).
• For comprehensive reviews: architecture, security, performance, and test coverage.
• When implementing features that touch several layers (API, UI, database).
• When you need a unified, prioritized remediation plan from multiple perspectives.
• For coordinated penetration testing followed by remediation planning.

Best practices

• Start with an explorer or discovery agent to map scope before invoking specialists.
• Follow a logical order: discovery → analysis → implementation → testing → synthesis.
• Pass relevant findings as context to downstream agents to avoid duplication and drift.
• Use a single synthesis step to produce a unified report with prioritized action items.
• Include a test-engineer whenever code changes are proposed to verify fixes and add coverage.

Example use cases

• Comprehensive codebase audit: explorer-agent → security-auditor → performance-optimizer → synthesis.
• Feature rollout review: identify affected domains, run backend-specialist and frontend-specialist in parallel, then have test-engineer validate.
• Security program: security-auditor → penetration-tester → synthesis with prioritized fixes and remediation steps.
• Database migration: explorer-agent maps schema, database-architect plans migrations, devops-engineer prepares CI/CD deployment, synthesis documents steps.
• Bug triage: debugger analyzes failing areas while backend and frontend specialists propose fixes; test-engineer confirms resolution.