jpskill.com
🛠️ 開発・MCP コミュニティ 🔴 エンジニア向け 👤 エンジニア・AI開発者

🧑‍🤝‍🧑 並列マルチエージェント実行パターン

parallel-agents

独立した複数タスクを別ドメイン専門エージェントに並列割り当てするSkill。

⏱ テスト計画作成 2時間 → 20分

📺 まず動画で見る(YouTube)

▶ 【衝撃】最強のAIエージェント「Claude Code」の最新機能・使い方・プログラミングをAIで効率化する超実践術を解説! ↗

※ jpskill.com 編集部が参考用に選んだ動画です。動画の内容と Skill の挙動は厳密には一致しないことがあります。

📜 元の英語説明(参考)

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

🇯🇵 日本人クリエイター向け解説

一言でいうと

独立した複数タスクを別ドメイン専門エージェントに並列割り当てするSkill。

※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。

⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。

🎯 このSkillでできること

下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。

📦 インストール方法 (3ステップ)

  1. 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
  2. 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
  3. 3. 展開してできたフォルダを、ホームフォルダの .claude/skills/ に置く
    • · macOS / Linux: ~/.claude/skills/
    • · Windows: %USERPROFILE%\.claude\skills\

Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。

詳しい使い方ガイドを見る →
最終更新
2026-05-17
取得日時
2026-05-17
同梱ファイル
1

💬 こう話しかけるだけ — サンプルプロンプト

  • 並列マルチエージェント実行パターン を使って、最小構成のサンプルコードを示して
  • 並列マルチエージェント実行パターン の主な使い方と注意点を教えて
  • 並列マルチエージェント実行パターン を既存プロジェクトに組み込む方法を教えて

これをClaude Code に貼るだけで、このSkillが自動発動します。

📖 Claude が読む原文 SKILL.md(中身を展開)

この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。

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

  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