The most successful AI-enabled PMs use LLMs to augment their capabilities — insights, synthesis, speed — rather than to automate the decision itself. Models are notoriously bad at reading organizational nuance and stakeholder politics. They will happily generate a confident recommendation built on none of the unwritten context that actually drives the choice. Treat the output as a sharper first draft of your own thinking, never as the final verdict. The PM is still the one accountable in the room.

Stop starting fresh chats. Use Projects in Claude or Custom GPTs in ChatGPT to host your PRDs, persona docs, roadmap, metric definitions, and strategy memos. This gives the model a long-term memory of your specific product context, so it stops hallucinating generic advice and starts responding inside your actual constraints. Pair this with the PARA method (Projects, Areas, Resources, Archives) for keeping the source material organized, and a CLAUDE.md-style instruction file at the root so the agent knows your team's voice, abbreviations, and guardrails.

A growing share of PMs are no longer waiting for engineering bandwidth to show an idea. They build rough, functional prototypes with AI IDEs like Cursor or low-code builders like Lovable and Replit, then walk engineers through a real click-through instead of a slide deck. The point is not to replace engineering — it is to eliminate the ambiguity gap between “what I described” and “what got built.” Show, don't tell. Technical PMs are going a step further and using Cursor to index their entire company repo, then asking questions like “if we change this field, what else breaks?”

The community-favorite technique is the “word vomit” method: dictate your messy thoughts into an LLM, let it organize them into a structured PRD or exec email, then edit 100% of the output by hand. Strip the corporate fluff, the em-dash tics, the “it's worth noting that...” filler, and every factual claim the model generated without evidence. What you keep is your thinking, made legible faster. What you cut is the AI fingerprint that kills trust when a senior leader spots it.

The Stack Most PMs Actually Use

• Claude — cited repeatedly on Reddit as the strongest model for PRD drafting, nuanced writing, and logical reasoning without the ChatGPT “AI-isms.”
• Cursor — AI code editor. Index your repo, then ask upstream-impact questions in plain English.
• Granola / Fireflies — meeting transcripts. Feed them into Claude to extract pain themes or jobs-to-be-done.
• Gamma — turn data-heavy notes into exec decks using the Pyramid Principle: lead with the answer, then stack supporting points.
• n8n / Zapier — build small agents that watch Slack channels or support tickets, cluster them by sentiment, and surface emerging trends.

Five Prompts Worth Stealing

A fuller library lives below. These five are the ones working PMs reach for weekly:

1. Edge-case discovery— “I am building [Feature X] for [Persona Y]. Here is the current workflow. Identify 10 edge cases, technical constraints, or user friction points I might have missed.”
2. Synthesis— “Take these 5 raw customer interview transcripts. Using the Pyramid Principle, summarize the top 3 pain points and the supporting evidence for each.”
3. User stories— “Based on this PRD snippet, write 5 user stories in Gherkin format (Given/When/Then) specifically for the [mobile/web] experience.”
4. SQL generation— “Using this schema [paste], write a SQL query to find 30-day retention for users who triggered 'Event A' at least three times.”
5. Skeptical roleplay— “Act as a skeptical CTO. Review this roadmap and surface the biggest technical risks and architectural flaws in the Q3 plan.”

Further Reading for New PMs

The resources below are the ones experienced PMs hand new hires on day one. Bookmark, don't binge.