A product manager's job is turning scattered thoughts into structure. Claude helps with the drafts and tidying of tasks like user stories, requirements, PRD drafts, and priority reviews. This guide covers using Claude in PM work. (Claude's output is a starting point; the final call on facts, context, and priorities is the PM's.)
1. Writing user stories
Useful for turning a feature idea into sentences from the user's point of view.
"Write the following feature as user stories in the form 'As a ___, I want to ___, because ___.' Include acceptance criteria for each story. [feature description]"
- Break a feature bundle into several user stories
- Get a draft of acceptance criteria alongside
- Ask the check question: "Any user types or edge cases I missed?"
2. Requirements and PRD drafts
- "Draft a PRD for this feature with: Background / Goal / Users / Key features / Success metrics / Out of scope."
- "Point out missing items or ambiguous parts in this spec."
- "List edge cases an engineer would ask about."
It reduces blank-page friction and adds a review lens.
3. Priorities and decision support
- "Put these feature candidates in a table by user value / dev cost / urgency."
- "Lay out the trade-offs of this decision."
But the final priority call is yours. Claude goes as far as organizing and offering a lens.
4. Ideas and research
- Expand ideas: "Brainstorm 10 ways to solve this problem." → brainstorming well with Claude
- Tidy research/interviews: summarize and structure interview notes or material → summarizing long documents with Claude
- Pin recurring context: put product context and a glossary in Project knowledge so every chat references it
Things to watch for
- Verify facts and context: Claude's general claims about market, competitors, or users can be inaccurate. Confirm with real data and research.
- Domain knowledge is yours: Claude doesn't know your product's specific constraints and stakeholders. Give enough context or fill it in yourself.
- The PM decides: responsibility for priorities, scope, and decisions rests with a person.
- Mind sensitive data: for unreleased roadmaps or customer data, check your data policy and proceed carefully.
FAQ
Q. Can I hand over the whole spec?
A draft skeleton helps, but product context and decisions need the PM to complete it. Prefer a "draft → review and fill in" flow.
Q. Which model fits PM work?
For long documents and complex organizing, a high-capability model (e.g., Claude Opus 4.8); for light drafts and ideas, a faster model.
Q. Curious about other roles?
For developers, marketing, writers, students, etc. → Claude use cases by role