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.
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 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.
Generate clickable prototypes from context workspace
Collapse feedback loops from weeks to hours
Connection:pol-probe-advisor (Vibe-Coded PoL Probes)
AI-Shaped Problems (Teresa Torres)
What makes a problem "AI-shaped"?
Previously difficult to scale due to human involvement (e.g., synthesizing 50 user interviews)
Falls short with current non-AI solutions (e.g., manual competitive tracking)
Requires consistency at scale (e.g., risk analysis across 100 features)
Key Insight: "While AI makes building easier, choosing what to build remains the primary challenge." Orchestration helps with the "building" part so PMs can focus on "choosing."
The Four Big Risks (Marty Cagan, AI Era)
The orchestrator manages these risks across the organization:
Risk
Standard Definition
AI Era Layer
Orchestrator's Role
Value Risk
Will customers pay?
Does AI provide enough incremental benefit vs. cost?
Validate value with PoL probes before orchestrating
Usability Risk
Can users figure it out?
Is the UX right? (Chat often isn't!)
Test workflows with real users
Feasibility Risk
Can we build it?
Do we understand "physics of AI"? Token budget?
Design within technical constraints
Viability Risk
Can we sell/support?
Legal limits? Data privacy? Sustainable OpEx?
Monitor costs, compliance, scalability
Anti-Patterns (What This Is NOT)
Not about replacing PMs: Orchestration amplifies judgment, doesn't eliminate it
Not about automating everything: Some tasks require human empathy and context
Not about complexity for its own sake: Only orchestrate when it saves significant time or improves quality
Not about "set it and forget it": Orchestrated workflows require monitoring and maintenance
When to Use This Skill
✅ Use this when:
You have repetitive PM tasks that take 5+ hours per week (competitive analysis, customer synthesis, roadmap maintenance)
You're doing sequential work that could be parallelized (research, then synthesis, then analysis)
You need consistency at scale (analyze 50 features for risk, synthesize 100 customer interviews)
You're spending time on execution instead of strategy
❌ Don't use this when:
The task is one-time or infrequent (not worth orchestration overhead)
Human judgment is critical at every step (empathy-driven work)
The task is already fast enough (don't over-engineer)
You haven't built context engineering foundations first (see context-engineering-advisor)
Application
This interactive skill uses adaptive questioning to design multi-agent workflows step-by-step.
Step 0: Gather Context
Agent asks:
Before we design your orchestrated workflow, let's gather context:
Current PM Work:
What repetitive tasks take the most time each week? (competitive analysis, customer synthesis, roadmap updates, etc.)
How much time do you spend on these tasks? (hours per week)
Are these tasks sequential (one after another) or could they run in parallel?
Desired Outcome:
What would "good enough" automation look like? (80% reduction in manual work? Higher consistency?)
What parts require human judgment? (final decisions, empathy, ethical considerations)
Technical Context:
Do you have context engineering foundations? (constraints registry, operational glossary—see context-engineering-advisor)
What AI tools do you currently use? (Claude Projects, ChatGPT, custom agents)
You can describe briefly or paste examples.
Step 1: Assess if Task is AI-Shaped
Agent asks:
Let's determine if your task is suited for orchestration. Which statement best describes your situation?
Select one:
"I spend 10+ hours per week on repetitive research/synthesis tasks"
Agent A (Research): Scrape competitors' product pages, extract features
Agent B (Launch Tracker): Monitor competitors' release notes, blog posts, social media
Agent C (Pricing Analyzer): Track pricing pages, identify changes
Agent D (Synthesis): Compile findings from A, B, C into structured report
Agent E (Gap Analysis): Compare our roadmap vs. competitor features, flag gaps
Total: Agents A-C run in parallel (3 hours), then D and E run sequentially (2 hours) = 5 hours + 1 hour PM review = 6 hours total (50% time saved)
Agent offers:
I'll help you decompose your task. Describe your current process step-by-step, and I'll identify:
Which steps can be agent-handled
Which steps can run in parallel
Which steps require human judgment
User response: [Describe process]
Agent provides: Decomposed workflow with agent assignments.
Step 3: Design Parallel vs. Sequential Flows
Agent asks:
Now let's design the workflow topology—which agents run in parallel vs. sequentially.
