# Agent Orchestration Advisor

Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Design
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill agent-orchestration-advisor -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill agent-orchestration-advisor -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill agent-orchestration-advisor -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill agent-orchestration-advisor -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/agent-orchestration-advisor/SKILL.md