Use when: You have a lot of rough thinking and need to get it organized fast.
Here's everything I know about [topic/problem/feature] dumped without structure:
[Your raw notes, bullet points, half-thoughts]
Based on this:
Identify the core problem in one sentence
List the key unknowns or gaps in my thinking
Suggest a structure for turning this into a [PRD / strategy doc / exec memo]
Use when: You want to stress-test something before sharing it.
Here is my [PRD / prioritization rationale / strategy doc]:
[Content]
Now play the role of a skeptical [senior engineer / head of sales / VP of Product].
What are your top 3 objections?
What questions would you ask that this document doesn't answer?
What assumptions does this make that you'd want validated first?
Use when: You're stuck on one approach and want to see alternatives.
I'm trying to solve this problem: [describe the problem]
My current approach is: [describe it]
Generate 4 alternative approaches I haven't mentioned. For each one:
Describe the approach in 2–3 sentences
State what it's best suited for
State its biggest weakness
Don't recommend one I just want the options laid out clearly.
Use when: Claude's output is technically correct but feels generic.
The output you gave is good structurally, but it's too generic it could apply to any product.
Make it specific to our situation:
Product: [describe it]
Users: [describe them]
Key constraint: [describe it]
Rewrite the [section/document] with this specificity built in. Every point should be something that couldn't apply verbatim to a random SaaS product.
Use when: You have a long document and need an exec-ready version.
Here is a [PRD / research synthesis / strategy doc]:
[Content]
Compress this into an executive summary for [audience: e.g., VP of Product in a weekly review].
Rules:
Maximum 200 words
Lead with what we're doing and why
Include the single most important risk
End with the one decision you need from them
No jargon, no passive voice