The PM AI Agent Fleet: 39 Agents Mapped to the 7-Stage Operating System

A live index of every AI agent for product managers, mapped to the 7 stages of the PM Operating System: Sense, Discover, Decide, Build, Ship, Measure, Amplify.

Falk GottlobUpdated 8 min readUpdated

The short version

The PM AI agent fleet is a set of autonomous agents that cover every repeated decision and output a product manager makes, mapped to the seven stages of the PM Operating System: Sense, Discover, Decide, Build, Ship, Measure, Amplify. Each agent runs on a schedule, pulls from connected data sources via Model Context Protocol (MCP), and delivers reports where you already work. Setup takes about an hour. Deploy them incrementally starting with Red Flag Detection. By month two the whole fleet is running. This page is the live index, auto-generated from the blog, and it updates every time I publish a new agent post.

For the honest meta-look at the fleet, what stuck, what died, what I'd do differently, see 39 PM AI Agents Deployed: What Stuck, What Died, and Why, the field-research piece behind this index.

Why a full fleet, and why full automation is a PM superpower

I started with 18 agents. They saved me 10+ hours a week. Then I realized the architecture was incomplete.

The agents were only covering parts of the PM job. I had good visibility into what was broken (Sense), but no agents orchestrating research into customer insights (Discover). I could spot priorities (Decide) but couldn't automatically generate PRDs or coordinate releases. The infrastructure was there, MCP wired up, vector DB running, but the playbook was thin.

So I mapped the entire PM Operating System across 7 stages and kept adding agents until each major decision or output a PM makes repeatedly had one. The result: I'm not doing PM work anymore. I'm doing PM thinking. The data flows, analysis happens, decisions get shaped, and I focus on judgment, strategy, and leadership.

This is what full PM automation looks like.

The data foundation

Your agent stack sits on three layers:

Structured data via MCP (Model Context Protocol) Connected data sources are everything. Agents pull from Jira, Slack, Zendesk, Salesforce, GitHub, Google Calendar, Notion, Google Drive, and analytics (Amplitude, Mixpanel). MCP standardizes the access, write once, agents read across all systems.

Unstructured data via vector database (Weaviate) Call transcripts from Gong. Support ticket descriptions. Meeting notes. Emails. These live in a vector database so agents can semantically search, finding patterns that share meaning, not just keywords.

Delivery and scheduling Agents output via Slack webhooks (reports land where you check them). They run on cron schedules (daily, weekly, bi-weekly). Automated but you control the cadence.

To get started:

Setup takes one hour. Then you have the foundation.

The 7-stage PM Operating System

Every agent I've written about slots into one of seven stages. The list below is generated from the blog at build time, so when I publish a new agent-*.mdx post and tag it with a stage, it appears here automatically. No article edit required.

🔮

Try the live sandbox first. Open the Agent Sandbox (PM Version) to poke at an interactive version of the fleet before reading every blueprint. You can click through agents, see sample outputs, and feel the cadence in about five minutes.

44 agents live in the fleet today, grouped into the 7 stages of the PM Operating System. This list is generated from the blog, add a newagent-*.mdxpost with agentStageand agentSchedulefrontmatter and it appears here automatically.
Stage 1

SENSE, Signal Detection

6 agents

These agents scan for what you need to know right now. Daily noise that might be signal.

Stage 2

DISCOVER, Research & Synthesis

5 agents

These agents synthesize the noise into insight. Customer research, market trends, patterns, hypotheses.

Stage 3

DECIDE, Prioritization & Planning

8 agents

These agents turn research into prioritized decisions. What to build? When? Why? This is where strategy becomes action.

Stage 4

BUILD, Prototyping & Execution

7 agents

These agents keep the team unblocked and shipping. The day-to-day operations of building.

Stage 5

SHIP, Release & GTM

5 agents

These agents own the release process. From readiness to launch to post-release validation.

Stage 6

MEASURE, Impact & Health

8 agents

These agents tell you if what you built actually worked. Did it move the needle?

Stage 7

AMPLIFY, Communication & Learning

5 agents

These agents share what you know with the people who need to know it. Strategy, leadership, alignment.

Your daily and weekly rhythm

Across the fleet, agents fire on a staggered schedule so information arrives when it's useful, not when it's fresh off the keyboard.

7:00 AM (daily, weekdays) Daily Focus, PM Issues, Documentation Gaps, GTM Monitoring fire. You know your priorities, what's broken, what's missing, and what's happening in market before you open email.

8:00 AM (daily, weekdays) Support Ticket Signals and NPS/CSAT Analysis run. Signal detection deepens, customer sentiment and issue patterns become visible.

Monday, 8:00 AM Weekly Ops Digest, Engineering Capacity, Customer Segmentation, and Sprint Planning kick off. This is your week-setup moment, patterns from last week, capacity reality, customer shifts, and your sprint crystallizes.

9:00 AM (daily, weekdays) Red Flag Detection, Product Ops, Roadmap Tracker, Team Triage, and Signal-to-Ship Cycle Time fire. Second wave of daily signals, catches what slipped through morning scan, and refreshes the in-flight portfolio view.

Monday, 9:00 AM Signal-to-Ship Cycle Time digest lands. The weekly meta-view of the whole fleet's output: where time is going across the seven stages (Signal, Prototype, Design partner, Production code, Rollout, Launch, Measure), which stage is the bottleneck, and how cycle time is trending. The agent that tells you whether the PM transformation is real.

Monday, 1:00 PM Executive Report compiles after morning agents finish. Prep for leadership conversations.

Monday, 4:00 PM Opportunity Prioritization and Assumption Tracker run. Your week's prioritized bets and validation plan are ready.

Tuesday, 9:00 AM Product Dashboard updates metric views before any stakeholder conversations.

Wednesday, 7:00 AM Interview Synthesis processes this week's customer calls into structured insights.

Wednesday, 8:00 AM Release Readiness Review and Release Documentation assess what's ready to ship.

Thursday, 10:00 AM Release Checker validates post-release stability.

Thursday, 2:00 PM Customer Journey Mapping updates your understanding of where friction lives.

Friday, 10:00 AM OKR Tracker and Retrospective Synthesis wrap the week. Did you hit outcomes? What did you learn?

Friday, 2:00 PM Opportunity Prioritization finalizes next week's top bets. Stakeholder Communication generates tailored updates for every team.

4:00 PM (daily, weekdays) Product Health and Feature Adoption run as your closing scan. OKR Tracker checks progress.

Hourly (continuous) KPI Watchdog watches your core metrics and pages you the moment a KPI drops outside its band, with a prototype fix attached.

Bi-weekly (rotating) Competitive Intelligence, Market Intelligence, Customer Commitments, Journey Mapping, Win/Loss Analysis cycle through. Strategic slower-burn agents that feed your monthly planning.

Building this yourself

The full agent fleet runs on:

  • Claude (Desktop, Code, or Projects) with Model Context Protocol (MCP) connected to your data sources
  • Weaviate vector database for semantic search across unstructured data
  • Slack webhooks for report delivery
  • Cron scheduling for agent execution

Setup guides walk you through all of it: Jira, Slack, Zendesk, Salesforce, GitHub, Google Calendar, Gong, analytics, PagerDuty, Sentry connections. One hour to wire. Then deploy agents incrementally.

Don't try to run them all at once. Start with SENSE (Red Flag Detection, Support Signals, NPS Analysis). Then add DISCOVER (Weekly Ops Digest, Interview Synthesis). Build from there.

By month two, your entire PM function is instrumented. By month three, you're operating at a completely different level.

What's still human

Agents handle data gathering, analysis, synthesis, and pattern detection. But PM judgment still lives here:

  • Customer empathy. An agent tells you 14 customers mentioned a pain. Only you sit across from them and feel the real problem.
  • Strategic trade-offs. The agent can prioritize by impact and effort. You decide whether market timing overrides the math.
  • Organizational persuasion. Your agent can't convince your CEO that the roadmap shifted. You can.
  • Hypothesis design. The agent flags assumptions. You decide which ones matter and how to test them.
  • Creative problem-solving. The agent finds the constraint. You figure out how to design around it.

This is the PM job as it should always have been. Data gathering automated. Analysis automated. Thinking and judgment remain yours.

The honest limitations

They hallucinate. Claude is confident when it's wrong. Every output needs your eye. Always verify critical findings.

They need real data. A DISCOVER agent is useless if your Gong transcripts aren't in the vector DB. Garbage in, garbage out.

They need tuning. Deploy an agent with bad thresholds and it alerts you 20 times a day. Best agents are the ones you've trained over 2-3 weeks.

They miss context. An agent can tell you which customers churned. It can't explain the political situation that drove the churn.

They need management. Set up the foundation once. But manage the agents like a small team, review outputs weekly, adjust parameters, add new data sources, prune noise.

Start this week

Don't read about agents. Build them.

Today:

Tomorrow: Deploy Red Flag Detection and Daily Focus. These two reclaim 60+ minutes per day.

This week: Add Product Health and Support Signals. You now have basic signal detection.

Next week: Add Weekly Ops Digest, Interview Synthesis, and Market Intelligence. DISCOVER stage activates.

Week 3-4: Opportunity Prioritization, Assumption Tracker, Sprint Planning. DECIDE stage runs.

Month 2: Full fleet deployed and running. Your entire PM Operating System. You're operating at a different level entirely.

Your team will notice. Your manager will notice. Your customers will notice. That's the real point.

Share this post

Frequently asked

What is the PM AI agent fleet?+

A set of autonomous AI agents that cover every repeated decision and output a product manager makes. The fleet is mapped to the seven stages of the PM Operating System: Sense, Discover, Decide, Build, Ship, Measure, Amplify. Each agent runs on a schedule (hourly, daily, weekly, or bi-weekly), pulls from connected data sources via MCP, and delivers reports to Slack or email.

What are the seven stages of the PM Operating System?+

Sense (signal detection), Discover (research and synthesis), Decide (prioritization and planning), Build (prototyping and execution), Ship (release and GTM), Measure (impact and health), Amplify (communication and learning). Every agent in the fleet maps to one of these stages.

How long does it take to set up the full agent fleet?+

One hour to wire the foundation (MCP connections to Jira, Slack, Zendesk, Salesforce, GitHub, Google Calendar, analytics, PagerDuty, Sentry). Then deploy agents incrementally, starting with Sense-stage agents (Red Flag Detection, Support Signal Processing, NPS Deep Dive). By month two, all agents are running. By month three, you're operating at a completely different level.

Which AI agent should a PM deploy first?+

Red Flag Detection. It runs daily at 9:00 AM, pulls from Zendesk, PagerDuty, Jira, Slack, and Salesforce, and scans for active incidents, unassigned tickets, escalations, and at-risk accounts. It reclaims about 45 minutes of morning triage per day and gives you a clean morning briefing before your first meeting.

What data sources do the agents need?+

Jira, Slack, Zendesk, Salesforce, GitHub, Google Calendar, Notion, Google Drive, analytics (Amplitude or Mixpanel), plus Gong or Chorus for customer call transcripts, and optionally Weaviate for semantic search across unstructured data. MCP (Model Context Protocol) standardizes access across all of them.

Do I need Claude Desktop, Claude Code, or something else to run the fleet?+

Any of three works: Claude Desktop with MCP, Claude Code (developer-focused), or Claude Projects. OpenClaw is a self-hosted alternative for teams that need on-premise data control. All four setups use the same agent definitions and MCP data connections.

What is the Signal-to-Ship Cycle Time Agent?+

The meta-agent of the fleet. It watches how every active product change moves through all seven PM OS stages, computes end-to-end cycle time, and names the weekly bottleneck. It tells you whether the PM transformation is real or performative by turning vague speed debates into a single compounding number.

Related reading

Deeper essays and other handbook chapters on the same thread.