Read @context/product.md, @notes/, and the open tickets in @tickets.md. Produce /work/priorities-[today].md with: - Now (this sprint): max 3 items, each with the evidence that puts it here - Next (this quarter): up to 5 items - Later / park: everything else, with one line on why it waits - Assumptions that would change the ranking if proven wrong - One question to ask the team before locking the Now list
AI for Product Management: the first 5 workflows to start with
The 2026 competence gap is not "do you use ChatGPT." It is whether messy context becomes a saved PRD, a ranked Now list, or a stakeholder update without rebuilding the prompt every time. Five workflows with inputs, outputs, and copy-paste prompts. Start with research synthesis, then PRDs, priorities, handoff, and updates.
Open AI PM OS
Skip building these five workflows from scratch. AI PM OS ships them ready to run.
What is AI for product management?
AI for product management in 2026 means using agents and reusable workflows to turn product context into discovery synthesis, PRDs, specs, and decisions. Competence is a workflow problem, not a chatbot problem. Start with five workflows. An AI PM OS is the packed version of that operating layer.
By George NurijanianLast updated: September 01, 2026
The first 5 workflows
The five starter workflows are research synthesis, priority critique, PRD drafting, build handoff, and stakeholder updates. Research synthesis is marked Start here because its saved output can ground the later PRD workflow. Open any row for a copy-paste starter prompt.
Read every file in /research/interviews/. For each transcript, extract: - Interviewee role and company context - Top 3 pain points with direct quotes - Current workaround - Feature requests mentioned Then write /research/interview-synthesis.md with: - The 5 most common pain points ranked by frequency - Contradictions or outlier perspectives worth flagging - 3 hypotheses worth testing - What is still unknown
Read @brief.md and @research/interview-synthesis.md. Draft /work/prd-[feature].md covering: - Problem statement grounded in the evidence - Proposed solution with a clear scope boundary - Success metrics (leading + lagging) - Open questions for engineering and design - What is explicitly out of scope Flag any claim that is not backed by the research file.
Read @work/prd-[feature].md and @context/product.md. Produce: 1. /work/stories-[feature].md — user stories with acceptance criteria, ordered by dependency 2. /prototypes/[feature]-v1.html — a single-page clickable prototype of the primary flow with realistic mock data Ask before inventing UI that the PRD does not describe.
Read @sprint/this-week.md and @decisions/. Write /comms/update-[today].md with: - 5-sentence exec summary (outcome first) - What shipped / what slipped, with owners - Decisions needed this week (max 3) - FAQ for the broader team - Draft release-note language for anything user-facing Match the voice of examples in /comms/examples/ if that folder exists.
Open AI PM OS
Once the map is clear, install AI PM OS so the same jobs run against your product context.
Claude Code + Cursor setup
Claude Code is Anthropic's terminal-based agent for autonomous, multi-step work on files. Cursor is an AI code editor for interactive edits and visual prototypes. Both can use standing context such as CLAUDE.md or project rules, reusable skills, and a context library. You reuse that context next time instead of pasting it into a new chat.
Tool map by workflow
This starter map pairs meeting capture with Granola. It pairs document synthesis with NotebookLM. It pairs PRD drafting with Claude Code. It pairs prototyping with Cursor or v0. It pairs ticket work with Linear. Full testing notes live on the AI tools for product managers hub.
| Workflow | Primary | Also |
|---|---|---|
| Capture context / meetings | Granola | Otter, Fireflies |
| Research synthesis (your docs) | NotebookLM | Claude Projects |
| PRD / strategy drafting | Claude Code | Claude Projects, ChatPRD |
| Prototype / UI handoff | Cursor, v0 | Lovable, Framer AI |
| Execution / tickets | Linear (+ MCP) | Jira AI |
Chat vs agent vs Linear MCP vs AI PM OS
Buyers mix these up. ChatGPT is a conversation. Claude Code is an agent on files. Linear MCP is a tracker connector. An AI PM OS is the craft layer. Dated September 2026.
| Layer | What it does | What it is not |
|---|---|---|
| Chat (ChatGPT, Claude.ai) | One-off drafts | Standing context, files, MCP |
| Agent (Claude Code, Cursor) | Multi-step work on files | Encoded PM methodology |
| Linear MCP | Where work lives in Linear | An AI PM OS |
| AI PM OS | Skills, workflows, subagents — how PM thinking runs | An issue tracker |
What PMs are saying in 2026
Dated signals behind this starter kit, with links to the sources.
“Starting every AI chat from scratch is the fastest way to burn out… The 30% of professionals getting 15+ hours back… are using Skills and Systems inside Claude.”
“A production-ready Claude Code configuration for product managers. Drop these files into your project and Claude Code immediately understands PM work. Includes a CLAUDE.md context file, 6 PM skills, and 4 templates.”
Also circulating: Lenny × Anthropic Head of Product Dianne Penn on “evals are the new PRDs” (2026-07-27) — useful advanced framing once the five starter workflows are habit.
Frequently asked questions
What is AI for product management?
AI for product management means using AI agents and repeatable workflows to turn product context into discovery synthesis, PRDs, prototypes, stakeholder updates, and decisions. What lasts is a workflow with clear inputs, a saved output, and standing context. A one-off chat thread does not.
Where should a product manager start with AI?
Start with research synthesis. Drop interview transcripts or feedback into Claude Code, NotebookLM, or Claude Projects and ask for themes, quotes, and uncertainty flags. Research is usually the easiest first win, and the output feeds better PRDs at once. Move to PRD drafting once there is evidence to ground the draft.
Do product managers need Claude Code or is ChatGPT enough?
ChatGPT and Claude.ai are fine for one-off drafts. Claude Code and Cursor win on multi-step jobs. They can read a folder, write a file, pull Linear tickets via MCP, and chain steps without re-pasting context. Many AI-forward PMs in 2026 run an agentic tool for workflows and keep a chat tool for quick questions. See the Claude Code for product managers guide.
What is the difference between a prompt list and a PM workflow?
A prompt list is a pile of one-shot instructions. A workflow is a repeatable path with named inputs, a saved output, and standing context (CLAUDE.md, skills, MCP). Blank-chat prompting does not compound. Skill packs and operating systems do, which is why standing context (CLAUDE.md, skills, MCP) beats re-pasting every session.
Is Linear MCP an AI PM OS?
No. Linear MCP connects Claude Code or Codex to Linear so the agent can find, create, and update issues. That is where work lives. An AI PM OS encodes how PM thinking runs: skills, workflows, and review subagents. They complement each other. The full comparison is AI PM OS vs Linear MCP.
How does AI PM OS relate to these five starter workflows?
AI PM OS packages 231 PM skills, 150+ frameworks, and 11 guided workflows. The same jobs (research synthesis, PRDs, handoff, status) run against product context. You do not rebuild each prompt from scratch. The five workflows on this page are the starting map. PM OS is the pre-assembled system once the map is clear.
Should prioritization be automated with AI?
Prioritization is still under-automated relative to research and PRDs. A useful first step is a priority critique workflow: feed notes and tickets, get a Now/Next/Later draft with assumptions flagged, then decide as a human. Full automation of roadmap calls is not the goal, a better first draft is.
Next reads: 15 AI tools PMs use daily, Claude Code for product managers, AI PM OS vs Linear MCP, and AI PM OS.