界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
数据与研究 · SKILL.md

parallel-agents

parallel-agents

【数据与研究】Multi-agent orchestration patterns for Claude Code's native Agent tool. Use when coordinating multiple specialized agents for comprehensive reviews, cross-domain feature implementation, or parallel analysis from multiple perspectives. Adapted to this workspace's 42 actual agents.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: parallel-agents description: Multi-agent orchestration patterns for Claude Code's native Agent tool. Use when coordinating multiple specialized agents for comprehensive reviews, cross-domain feature implementation, or parallel analysis from multiple perspectives. Adapted to this workspace's 42 actual agents. allowed-tools: Read, Glob, Grep metadata: triggers: comprehensive review, multi-perspective analysis, parallel agents, orchestrate agents, coordinate agents, run multiple agents, full audit, cross-domain implementation related-skills: subagent-driven-development, multi-agent-patterns, multi-agent-brainstorming, architecture-design domain: workflow role: architect scope: design output-format: report last-reviewed: "2026-03-15"

Iron Law

USE THIS WORKSPACE'S ACTUAL AGENTS — never reference placeholder agents (security-auditor, backend-specialist) that don't exist here; always dispatch from the 42 agents in .claude/agents/

Explanation: Dispatching a non-existent agent silently fails. Every agent name in this skill maps to a real .md file in .claude/agents/.

Parallel Agents Orchestration

Orchestration guide for coordinating multiple specialized agents through Claude Code's native Agent tool. Keeps all orchestration within Claude's control using the built-in Agent tool and TeamCreate.


When to Use Orchestration

Good for:

  • Complex tasks requiring multiple expertise domains (security + code quality + tests)
  • Comprehensive reviews (architecture + security + accessibility)
  • Feature implementation needing backend + frontend + database work
  • Full pre-deploy audits across all stack layers

Not for:

  • Simple, single-domain tasks (use the relevant specialist agent directly)
  • Quick fixes or small changes within one file
  • Tasks where one agent suffices

Decision rule: If dispatching more than 1 agent, use this skill for orchestration patterns and synthesis protocol.


Workspace Agent Catalog

Load references/workspace-agent-catalog.md for full descriptions. Quick reference:

AgentDomainUse For
code-reviewerGeneralQuality, security, maintainability for any language
security-reviewerSecurityOWASP Top 10, input validation, secret scanning
threat-modeling-expertSecuritySTRIDE analysis, attack trees, security architecture
silent-failure-hunterError HandlingSwallowed exceptions, missing error states
spring-reactive-reviewerJava/SpringReactive correctness, Resilience4j, R2DBC
nestjs-reviewerNestJSModule correctness, JWT, Prisma patterns
riverpod-reviewerFlutterProvider types, ref usage, AsyncValue handling
agentic-ai-reviewerLangGraphGraph correctness, guardrails, cost, production readiness
postgresql-database-reviewerPostgreSQLQuery optimization, schema, security, performance
pgvector-schema-reviewerpgvectorVector schema, index alignment, embedding model
weaviate-schema-reviewerWeaviateCollection definition, vectorizer, multi-tenancy
rag-pipeline-reviewerRAGChunking, model pinning, reranking, error handling
accessibility-auditorAccessibilityWCAG 2.1, Semantics, focus management
ui-standards-expertUI/UXDesign tokens, theming, touch targets
flutter-security-expertFlutterSecure storage, certificate pinning, GDPR
dedup-code-agentTech DebtDuplication, unused code, dependency bloat
plan-challengerPlanningAdversarial plan review (5 attack dimensions)
output-evaluatorQuality GateLLM-as-Judge: APPROVE / NEEDS_REVIEW / REJECT
pr-test-analyzerTestingBehavioral coverage gaps, critical paths
architectArchitectureC4 diagrams, API contracts, ADRs
java-spring-apiJavaSpring Boot WebFlux implementation
nestjs-apiNestJSNestJS modules, controllers, services
python-devPythonFastAPI services, async patterns
flutter-mobileFlutterCross-platform mobile features
angular-spaAngularStandalone components, signals, routing
agentic-ai-devAgentic AILangChain/LangGraph agents
google-adkADKGoogle ADK agents, Gemini integration
database-designerDatabaseSchema design, ERD, migrations
deployment-engineerCI/CDGitHub Actions, Docker, Cloud Run
terraform-specialistGCP InfraCloud Run, Cloud SQL, Artifact Registry
frontend-designDesignLanding pages, dashboards, visual identity
a2ui-angularA2UIAgent-to-User Interface Angular renderers
mobile-developerReact NativeReact Native, native iOS/Android, Fastlane
browser-testingTestingChrome DevTools, E2E flows, performance
error-detectiveDebuggingLog analysis, stack traces, root cause
comment-analyzerDocumentationComment accuracy vs implementation
code-simplifierRefactoringComplexity reduction, over-engineering
type-design-analyzerTypesTypeScript, Dart, Java type design quality
mermaid-expertDiagramsFlowcharts, sequences, ERDs
tutorial-engineerEducationOnboarding guides, feature tutorials
dx-optimizerDev ExperienceTooling, automation, local dev setup
skill-reviewerSkillsSkill file compliance audit
reality-checkerValidationVisual evidence gate before PR merge

Orchestration Patterns

Load references/orchestration-patterns.md for full pattern details.

Pattern 1: Comprehensive Feature Review

For any feature touching security-sensitive code, database, or multiple services:

Step 1: code-reviewer          → overall quality gate
Step 2: [stack-specific reviewer] → framework-specific patterns
Step 3: security-reviewer      → OWASP + auth + input validation
Step 4: silent-failure-hunter  → error handling completeness
Step 5: pr-test-analyzer       → behavioral test coverage
Step 6: Synthesize all findings

Pattern 2: Pre-Deploy Audit

Before merging any significant feature branch:

Parallel:
  security-reviewer     → security findings
  [stack reviewer]      → framework correctness
  pr-test-analyzer      → test coverage gaps
Sequential:
  output-evaluator      → APPROVE / NEEDS_REVIEW / REJECT verdict

Pattern 3: Full Flutter Feature

riverpod-reviewer         → state management
flutter-security-expert   → secure storage, GDPR
accessibility-auditor     → WCAG 2.1
ui-standards-expert       → design tokens, touch targets
silent-failure-hunter     → error handling in async code

Pattern 4: Agentic AI System Review

agentic-ai-reviewer       → graph correctness, guardrails
security-reviewer         → prompt injection, input validation
rag-pipeline-reviewer     → chunking, model pinning (if RAG used)
silent-failure-hunter     → tool error handling

Synthesis Protocol

Load references/synthesis-protocol.md for the full template.

After all agents complete:

## Orchestration Synthesis

### Task Summary
[What was accomplished]

### Agent Contributions
| Agent | Key Finding |
|-------|------------|
| [agent] | [finding] |

### Consolidated Recommendations (severity-ordered)
1. **CRITICAL** — [issue] — must fix before merge
2. **HIGH** — [issue] — should fix before merge
3. **MEDIUM** — [issue] — fix in follow-up PR
4. **LOW** — [issue] — note for tech debt backlog

### Verdict
[APPROVE | NEEDS_REVIEW | BLOCK] — based on finding severity

Constraints

MUST DO

  • Only dispatch agents that exist in .claude/agents/ (42 agents listed in catalog above)
  • Pass explicit context to every agent — agents do NOT inherit CLAUDE.md or conversation history
  • Produce a single synthesized report, not separate outputs per agent
  • Include test coverage review (pr-test-analyzer) for any code-modifying orchestration

MUST NOT DO

  • Dispatch agents with only "review this code" — always pass specific context and scope
  • Run more agents than needed — match agent count to actual coverage gaps
  • Skip synthesis — raw agent outputs are not a deliverable

Knowledge Reference

Agent orchestration, multi-agent coordination, parallel dispatch, reviewer agents, synthesis protocol, pre-deploy gate, Claude Code Agent tool, TeamCreate, context passing

我的收藏