agent-orchestration-advisor

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: agent-orchestration-advisor
argument-hint: "[workflow or task to orchestrate]"
description: Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
intent: >-
  Guide product managers through designing multi-agent workflows — breaking complex, repetitive tasks into parallel, specialized AI agents rather than linear, sequential processes. Covers the 4 dimensions of orchestration, agent boundary design, launch control tower monitoring, and evaluation frameworks.
type: interactive
theme: ai-agents
best_for:
  - "Breaking a complex PM workflow into parallel, specialized AI agents"
  - "Designing agent boundaries, handoffs, and human review points"
  - "Setting up launch control tower monitoring for agentic workflows"
scenarios:
  - "I spend hours on competitive research every week — help me design agents to run it in parallel"
  - "Our AI workflow is one giant sequential prompt chain — help me re-architect it as an orchestrated system"
estimated_time: "15-25 min"
---

## Purpose

Guide product managers through designing **multi-agent workflows**—breaking complex, repetitive PM tasks into parallel, specialized AI agents rather than linear, sequential processes or manual execution. Use this to transition from "document-heavy administrator" to "systems-level orchestrator" who coordinates a "living system" of AI agents, human teams, and market data interacting continuously.

**Key Shift:** From linear project management (one task at a time) to orchestration (multiple agents working simultaneously, each with clear boundaries and handoffs).

This is not about prompt writing—it's about **architecting workflows where AI agents handle repetitive research, synthesis, and validation while PMs focus on strategy and decision-making**.

## Input

**Works best with:** The workflow or recurring task you want to orchestrate — described in a sentence or two, however manual or messy it is today.
**Also useful:** Where it breaks down now (too slow, too sequential, too dependent on you), the tools your team already uses, and whether you've worked through [context-engineering-advisor](../context-engineering-advisor/SKILL.md) first (it's the prerequisite discipline).

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The advisor opens by asking which PM workflow eats the most of your week, then walks the four orchestration dimensions against it.

**Example invocation:** `Design an orchestration for our weekly competitive intel: today one PM spends 6 hours scraping, summarizing, and briefing — sequentially.`

## Key Concepts

### Orchestration vs. Project Management

| Dimension | Project Management | Orchestration |
|-----------|-------------------|---------------|
| **Approach** | Linear oversight of schedules and human tasks | Managing "living system" where AI agents, humans, and data interact continuously |
| **Task Flow** | Sequential (finish A, then B, then C) | Parallel (A, B, C run simultaneously) |
| **PM Role** | Document-heavy administrator | Systems-level leader coordinating automated systems + human judgment |
| **Focus** | Output (features shipped) | Outcome (business results, learning velocity) |
| **Risk Management** | Manual tracking and mitigation | Real-time monitoring with agentic systems flagging gaps |

**Critical Insight:** Orchestration is not about replacing humans—it's about **force-multiplying human judgment** by automating repetitive, time-consuming tasks.

---

### The Four Dimensions of Orchestration

#### 1. **Coordination of Multi-Agent Workflows**
Breaking complex tasks into specialized agents that run in parallel.

**Example:**
- **Manual (Old):** PM spends 8 hours compiling competit