AI PM Course / The Framework Onboarding Edition

The AI PM
Playbook

From AI-Assisted AI-Native

14 PM activities ranked by time drain × automation value, mapped to a 3-level skill progression — from copy-pasting context into a chat box to running your own AI operating system.

1
Cross-tool context synthesis
Mentioned by 4 / 4 PMs — the universal pain
2
Slack message triage & response
20+ threads / day for some PMs
3
Customer call analysis
One PM needs to analyze 50+ calls at once
4
Competitor & market intelligence
Every PM tracks this — nobody has a system
5
Roadmap planning & prioritization
Most still running on Excel sheets
01 Basic
AI-Assisted PM
Core shift PM brings context to AI (copy-paste)
Key unlock Prompt craftsmanship
Modules
Product knowledge responses Research & intelligence Business writing PRD drafting Meeting prep
Tools
Claude Chat ChatGPT Web search

Who's here: PMs using AI for Q&A and drafting only.

+ Connection
02 Intermediate
AI-Connected PM
Core shift AI goes and gets the context (MCP integration)
Key unlock Connected tool ecosystem
Modules
Slack intelligence Call analysis pipeline Document & KB integration Multi-tool synthesis Roadmap signal aggregation Email intelligence
Tools
Claude + Slack MCP Gong MCP Google Drive MCP Gmail MCP Jira MCP Confluence MCP

Who's here: PMs ready to connect AI to their actual workflows.

+ Persistence
03 Expert
AI-Native PM
Core shift PM builds persistent systems that accumulate knowledge
Key unlock AI as infrastructure, not conversation
Modules
Knowledge architecture Competitor watcher agent Batch call analysis Prototype-to-PR pipeline Custom dashboards Testing agents Multi-agent orchestration
Tools
Claude Code Claude Design Cursor Cowork

Who's here: PMs building their own AI operating system.

You don't need a better AI. You need to give your AI better context. Each level adds more context, which makes AI reasoning more useful — and unlocks the “thinking partner” every PM wants.
The thesis of the entire course
01
5 real Slack responses Their voice — not a template.
02
Their actual PRD structure & format However they really write specs today.
03
Their prioritization framework RICE? Gut feel? An Excel sheet?
04
Their signal channel map Which Slack channels, which Jira projects.
05
Their product domain glossary The language their team actually speaks.

No two PMs work the same way.
The AI has to match YOUR mental model.

Slack MCP
Messaging
Channel intelligence
Gong / Fathom MCP
Conversations
Call analysis
Google Drive MCP
Documents
Document context
Gmail MCP
Email
Email triage
Jira / Linear MCP
Tickets
Ticket intelligence
Confluence MCP
Wiki
Knowledge base