u/Far-Reality-3659

I’ve been noticing that as AI has gotten better, the PM workflow seems to be changing pretty quickly.

Instead of making static mockups, I’m seeing more people talk about building actual working prototypes with tools like Claude, Codex, Bolt, Lovable, Replit, etc.

I’m curious how this actually works in practice.
If you’re a PM, are you using these tools yourself?

Do you just spin something up in Bolt or Lovable, or are you opening VS Code with Claude Code/Codex and iterating there?

And what do you expect from these prototypes? Are they just meant to communicate an idea and get stakeholder feedback, or are they detailed enough that engineering can actually build from them?

I’m mostly asking because I’m trying to understand how AI is changing the role of PMs. It feels like the line between product, design, and engineering is getting blurrier, and I’d love to hear how people are approaching it on their teams.

I’ve been noticing that as AI has gotten better, the PM workflow seems to be changing pretty quickly.

Instead of making static mockups, I’m seeing more people talk about building actual working prototypes with tools like Claude, Codex, Bolt, Lovable, Replit, etc.

I’m curious how this actually works in practice.
If you’re a PM, are you using these tools yourself?

Do you just spin something up in Bolt or Lovable, or are you opening VS Code with Claude Code/Codex and iterating there?

And what do you expect from these prototypes? Are they just meant to communicate an idea and get stakeholder feedback, or are they detailed enough that engineering can actually build from them?

I’m mostly asking because I’m trying to understand how AI is changing the role of PMs. It feels like the line between product, design, and engineering is getting blurrier, and I’d love to hear how people are approaching it on their teams.

I’ve seen a lot of people lately saying requirements management is becoming “just throw a prompt into Claude Code” or that requirements are so vague engineers end up figuring things out as they build.

As a CS student who’s been trying to learn more about product management, I’m curious how this actually works in practice.

When requirements are vague or constantly changing, how do you usually manage them? Do you keep everything in Jira, Confluence, Notion, PRDs, or somewhere else? How much back-and-forth happens before engineering starts building?
I’m mainly interested in hearing how experienced PMs keep everyone aligned when requirements aren’t crystal clear.

I’m close to finishing my MVP, and now I’m trying to validate whether it’s actually worth continuing.

The next step is talking to real users, but I keep running into a problem: I struggle to confidently answer basic questions like:

\- Why should I use this?

\- How does it actually help me?

\- How is this different from existing tools?

In my head, I do have answers. But when I say them out loud, I sound unsure, and it feels like I don’t fully believe in what I’m building.

Part of it is this constant thought in the back of my mind: “What if they know something I don’t, and this whole idea is flawed?”

For those who’ve been through this stage:

How did you get better at confidently explaining why people should use your product while still being open to feedback