Know your product better than anyone in the room

The gap between knowing and deciding

You know your product. You have thought about it for weeks. You write the PRD, re-read it, and it feels complete.

But there is a difference between knowing something and having committed to it on paper. Your head fills in the gaps automatically. You know what "improve engagement" means to you. You know which segments matter more. You know the timeline risk. But none of that made it into the document, because you did not realize it was missing.

The strongest PMs are not the ones who write the longest documents. They are the ones who have thought through every dimension: the tradeoffs, the failure modes, the metrics that actually prove success, the scope they deliberately cut. And they can articulate why for each one.

SPM connects to Claude or Cursor and helps you get there. It finds the dimensions you have not addressed yet, and asks the questions that turn implicit knowledge into explicit decisions.

Setup: 2 minutes, once

SPM works as a connected tool (MCP server) inside Claude or Cursor. You set it up once. See the full setup guide for step-by-step instructions.

Then type "spm get started" to pick a review template, or paste your own team's PRD template and say "create a review system from this." SPM turns your standards into a review system. Next time, it uses yours automatically.

The flow

1. Get your document in

You are already in Claude or Cursor. You do not need to write your PRD somewhere else first.

• Paste your document directly into the chat
• Ask Claude to help draft one: "Help me write a PRD for [feature]"
• Reference a file in your repo: "Review docs/feature-spec.md"

2. See where you stand

Type spm analyze. You get a scorecard. Every section of your document scored against expert-level standards. Not "looks good" or "needs work." Specific scores, with specific gaps.

The score is not a grade. It is a map of the dimensions you have not thought through yet.

3. Think through the gaps

Type spm clarify. This is the real work.

SPM looks at the weakest areas in your document and asks the questions that turn vague intent into clear decisions:

"You mention 3 target segments but only define success metrics for 1. Which segments are you deprioritizing, and what is the criteria?"

"The timeline assumes backend and mobile can run in parallel. What is the dependency if the API contract is not finalized?"

"You list 'increased engagement' as a success metric. What is the baseline, and what number would tell you this is not working?"

These are not gotcha questions. They are the ones you would eventually need to answer anyway, when an engineer asks during sprint planning, or when you are three weeks into build and realize the scope was never clear.

You answer. Your scores update. SPM goes deeper on the next gap.

Do 2-3 rounds. Each round forces you to commit to decisions you were carrying in your head but had not written down. By the end, you do not just have a better document. You have a clearer understanding of your own product.

You do not need all the answers. When SPM asks something you genuinely do not know yet, say so. Knowing which questions you cannot answer is just as valuable. Those become your research list, not your blind spots.

4. Get the improved document

Type spm improve. SPM rewrites the weak sections using your answers from the clarification rounds. Your thinking goes into the document. Not generic filler. The decisions you actually made, in your own reasoning.

What changes

The obvious benefit: your documents get better. Gaps close. Metrics get specific. Scope gets explicit.

The deeper benefit: you start thinking this way on your own. After a few rounds with SPM, you start catching the gaps before you even run an analysis. You start writing with counter-metrics, rollback triggers, and scope boundaries from the first draft. The questions become part of how you think about product, not something an external tool has to remind you of.

That is the real outcome. Not a polished document. A PM who can see every dimension of a product decision, articulate the tradeoffs, and explain why they chose what they chose.

The document is the artifact. The sharper thinking is what you keep.

And yes, this also means your stakeholder reviews go differently. When you have already thought through every angle, the meeting starts at strategy, not gap-filling. But that is a side effect of better thinking, not the goal.

For teams

One person sets the review standards by pasting the team's template. Share the connector URL. Everyone develops the same thinking discipline, whether it is a junior PM's first PRD or a staff PM's quarterly roadmap.

Same rigor, same dimensions, consistent product thinking across the team.

Quick reference