Claude prompts product managers actually reuse

Not a prompt-engineering course — a short list of asks that hold up in day-to-day product work, from interview synthesis to stakeholder updates.

Most prompt lists are padding. These are the asks that survive contact with real product work — the ones that keep earning their place after the novelty wears off. They assume you're in Sofos with your project files in the workspace, so Claude can read the actual material rather than working from vibes. Adjust the wording freely; the structure is what matters.

Working with evidence

• "Read every file in research/ and list the recurring complaints, each with a count of how many sources mention it and one direct quote." — counts and quotes keep the synthesis honest.
• "Here's a CSV of feature requests. Group them into themes, but flag any request that doesn't fit a theme instead of forcing it." — the leftovers are often the interesting part.
• "Which claims in strategy.md would a skeptical board member challenge, and what evidence do we have for each?"

Drafting and revising

• "Turn my notes into a one-pager for [audience]. Anything you can't support from my notes, mark as OPEN rather than inventing."
• "Rewrite this for the exec readout: half the length, lead with the decision we need, move the method to an appendix."
• "Read this as the head of engineering. Where would you push back?" — cheaper than finding out in the meeting.

The recurring stuff

• "Compare this week's metrics CSV to last week's and draft the Monday update: what moved, why we think it moved, what we're doing about it."
• "Go through today's meeting notes and pull every commitment anyone made, with owner and date. Anything ambiguous, list separately as needs-confirmation."
• "Draft replies to these three stakeholder emails. Keep my position from decisions.md, but make the no to the second one gentler."

What the good asks have in common

Three things, if you look closely. They point at real material — a folder, a file, a paste — instead of asking Claude to imagine the inputs. They name the audience, because a one-pager for engineers and a one-pager for the board are different documents. And they give Claude permission to say "I don't know": the OPEN markers, the doesn't-fit flags, the needs-confirmation lists. That last one is the difference between an assistant that looks impressive and one you can actually rely on.

When you notice yourself typing the same ask every week, stop retyping it — turn it into a skill. That's exactly what the skills in the library below are: prompts like these, promoted to a file, so the format stays consistent no matter who on the team asks.