top of page

Top 1% PM AI Toolkit - exact prompts you can start using today!

  • nikitarpatil
  • 4 days ago
  • 3 min read

Updated: 2 days ago

The exact prompts you can use daily. Save these. Reuse them.


Your unfair advantage starts here…



1. The Strategy Challenger

👉🏼 When to use: Before committing to any roadmap or big decision

Code
You're a ruthless product strategist.

Here's my product strategy: 
[Paste]

Your job:
1. Identify the weakest assumptions
2. Highlight where this could fail in the real world
3. Suggest 3 alternative strategies that could outperform this
4. Point out any user segments I am ignoring

Be brutally honest. Do not sugarcoat.

🔥 Why it matters: Most PMs seek validation. Top PMs seek disconfirmation.


2. The User Insight Extractor

👉🏼 When to use: After collecting reviews, feedback, or support tickets

Code
You’re a world-class UX researcher.

Here’s my raw user feedback: 
[Paste data]

Tasks:
1. Cluster feedback into 5-7 key themes
2. Identify underlying user needs (not surface complaints)
3. Highlight emotional signals (frustration, delight, confusion)
4. Suggest 3 product opportunities based on this

Output in structured format.

🔥 Why it matters: Works insanely well for products with large feedback loops.


3. The Synthetic Persona Simulator

👉🏼 When to use: Before designing flows or features

Code
Act as this user persona:
- Age:
- Occupation:
- Goals:
- Frustration:
- Context of use:

Now simulate:
1. How you would discover this product
2. Your first impression
3. Points of confusion or friction
4. What would make you abandon the product

Be specific and realistic.

🔥 Why it matters: Compress weeks of research into hours


4. The PRD Generator

👉🏼 When to use: Writing product requirements

Code
You’re a senior PM at a top tech company.

Write a clear, concise PRD for the following feature: 
[Feature description]

Include:
1. Problem statement
2. User personas
3. Goals and success metrics
4. Key features
5. Edge cases
6. Risks and trade-offs

Keep it structured and easy for engineers and designers to follow.

🔥 Why it matters: PRD instantly become crisp.


5. The Experiment Designer

👉🏼 When to use: Planning A/B tests

Code
You’re a data-driven product manager.

I want to test this hypothesis: 
[Hypothesis]

Help me:
1. Define control vs variant
2. Identify primary and secondary metrics
3. Estimate sample size considerations
4. List potential pitfalls or biases
5. Suggest how to interpret ambiguous results

🔥 Why it matters: Turn experiments into decision-grade experiments.


6. The Metric Storyteller

👉🏼 When to use: After analyzing data

Code
You’re a PM presenting to executives.

Here’s the data: 
[Paste metrics]

Your Tasks:
1. Summarize key insights in plain English
2. Identify what matters vs what doesn't
3. Suggest the most likely causes
4. Recommend clear next steps

Keep it concise and impactful.

🔥 Why it matters: Data without narrative is useless.


7. The Competitor Deconstructor

👉🏼 When to use: Understanding known products

Code
Act as a product strategist.

Analyze this product: 
[Competitor/Product]

Break it down into:
1. Core value proposition
2. Key user segments
3. Strengths and weaknesses
4. Growth strategy
5. Monetization model

Then suggest how we can outperform them.

🔥 Why it matters: You’re not just benchmarking — you’re finding attach vectors.


8. The Roadmap Prioritizer

👉🏼 When to use: Too many ideas, not enough time

Code
You’re a senior PM.

Here’re potential features: 
[List]

Help me:
1. Score them into RICE (Reach, Impact, Confidence, Effort)
2. Rank them
3. Justify the prioritization
4. Identify quick wins vs long-term bets

Output in structured format.

🔥 Why it matters: Cuts through endless prioritization debates.


9. The “Why Are We Wrong?” Prompt

👉🏼 When to use: Before launch (CRITICAL)

Code
Assume our product decision is wrong.

Your job:
1. Explain why it will fail
2. Identify blind spots in our thinking
3. Suggest what we are underestimating
4. Recommend safeguards or mitigations

🔥 Why it matters: Avoid career-limiting mistakes.


10. The Communication Translator

👉🏼 When to use: Stakeholder alignment

Code
Rewrite this update for three audiences:

1. Executives (high-level, impact-focused)
2. Engineers (technical clarity)
3. Designers (user experience focus)

Here's the update:
[Paste]

🔥 Why it matters: One input —> three perfectly tailored outputs.

 
 
 

Comments


bottom of page