You code faster than you can think about product. Vibe Code PM runs the process you skip, discovery, the spec, the flow, the metrics, the ship gate, the launch, and offers each one unprompted the moment it matters.
you ▸ let's build an app that chases overdue invoices
pm ▸ Hold on. Before you write a prompt, who feels this pain worst, and what do they do about it today? Let's run discovery first.
→ offering discovery, decline and it notes the call and stays quiet
You generate code faster than you can think about product. So you skip the seat that asks the slow questions.
No spec. Scope drift by day two. Flows nobody walked. Features nobody wanted. A launch into silence.
You have a folder of side projects that died, and you know why each one died. The code was fine. Fast, even. The product was the miss.
Vibe Code PM does not ask you to learn a process or run the right command at the right time. If you already knew discovery comes before code and instrumentation comes before launch, you would not need a PM. So it reads where your project is and offers the next step unprompted, once.
Say "I want to build an app that does X" and it offers discovery before you write a prompt. Say "let's start coding" with no spec and it offers the PRD. Say "ship it" and it walks your build as a first-time user before you push. Decline any step and it notes the decision and never asks again. Your project, your risk.
No PRD before the idea is validated. No build before the flow is mapped. No launch before the numbers exist. Each phase writes one markdown file into a .vibecodepm/ folder in your project. Yours, readable, forever. Each phase reads the one before it, and that is how the sequence holds.
Pressure-tests the idea. Who has the problem, what they do today, real demand, an honest kill-or-go call, and a customer interview kit.
A one-page spec. Scope, the non-scope you will be tempted to add, success and kill criteria, milestones sequenced riskiest-bet-first.
Maps the whole experience before you build. Entry points, happy path, every state, every recovery path.
Defines success as a number before launch. Activation event, north star, week-one targets, and the instrumentation to actually capture them.
Walks your build as a first-time user against the flow map, verifies the metrics landed, then blocks or blesses.
The launch plan. Positioning, who to sell to, pricing, ranked channels, and a first-ten-users list you can work this week.
You have tried the Notion template and the "act as a senior PM" prompt. They all require you to remember to use them, which is the exact muscle a vibecoder does not have.
Vibe Code PM shows up when you need it, once, and gets out of the way when you don't. Say no and it stays quiet for good. A prompt cannot remember what phase you are in. This does.
If you have launched into silence, scope-crept a weekend into a quarter, or built a feature nobody touched, this is the seat you were missing.
Pricing goes live once the plugin has survived enough real builds. The waitlist installs first, in order, and keeps the launch price.
It is in final hardening now, being run against real builds until the rough edges are gone. The waitlist gets install access first, in order, and keeps the $19 launch price.
No. It reads your project and offers each step unprompted, once. Commands exist if you want them, and you never need them.
Decline it. It logs the decision and never offers that step again for that project.
In a .vibecodepm/ folder in your own repo, plain markdown, versioned with your code. Nothing leaves your machine that Claude Code does not already handle.
No. It is a sequenced lifecycle with gates. Ship-check literally walks your build as a stranger and can block a launch. A prompt cannot remember what phase you are in. This does.
Then you will fly through the gates, and still catch the one flow you didn't walk. The PM that annoys you the least is the one that is right.