Product manager toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/product-manager-toolkit, including the files SKILL.md points to. - Describe your job in plain words. Claude Code follows the skill from there.
npx degit alirezarezvani/claude-skills/product-team/skills/product-manager-toolkit#main ~/.claude/skills/product-manager-toolkitFor one project only, change the path to .claude/skills/product-manager-toolkit. This skill also uses interview_transcript.txt, transcript.txt, interview.txt, priorities.json, insights.json — copying SKILL.md alone won't be enough. See the folder on GitHub.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Product manager toolkit
Show the full text353 lines
| name | description |
|---|---|
| product-manager-toolkit | Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy. |
Product Manager Toolkit
Essential tools and frameworks for modern product management, from discovery to delivery.
Table of Contents
Quick Start
For Feature Prioritization
# Create sample data file
python scripts/rice_prioritizer.py sample
# Run prioritization with team capacity
python scripts/rice_prioritizer.py sample_features.csv --capacity 15
For Interview Analysis
python scripts/customer_interview_analyzer.py interview_transcript.txt
For PRD Creation
- Choose template from
references/prd_templates.md - Fill sections based on discovery work
- Review with engineering for feasibility
- Version control in project management tool
Core Workflows
Feature Prioritization Process
Gather → Score → Analyze → Plan → Validate → Execute
Step 1: Gather Feature Requests
- Customer feedback (support tickets, interviews)
- Sales requests (CRM pipeline blockers)
- Technical debt (engineering input)
- Strategic initiatives (leadership goals)
Step 2: Score with RICE
# Input: CSV with features
python scripts/rice_prioritizer.py features.csv --capacity 20
See references/frameworks.md for RICE formula and scoring guidelines.
Step 3: Analyze Portfolio
Review the tool output for:
- Quick wins vs big bets distribution
- Effort concentration (avoid all XL projects)
- Strategic alignment gaps
Step 4: Generate Roadmap
- Quarterly capacity allocation
- Dependency identification
- Stakeholder communication plan
Step 5: Validate Results
Before finalizing the roadmap:
- Compare top priorities against strategic goals
- Run sensitivity analysis (what if estimates are wrong by 2x?)
- Review with key stakeholders for blind spots
- Check for missing dependencies between features
- Validate effort estimates with engineering
Step 6: Execute and Iterate
- Share roadmap with team
- Track actual vs estimated effort
- Revisit priorities quarterly
- Update RICE inputs based on learnings
Customer Discovery Process
Plan → Recruit → Interview → Analyze → Synthesize → Validate
Step 1: Plan Research
- Define research questions
- Identify target segments
- Create interview script (see
references/frameworks.md)
Step 2: Recruit Participants
- 5-8 interviews per segment
- Mix of power users and churned users
- Incentivize appropriately
Step 3: Conduct Interviews
- Use semi-structured format
- Focus on problems, not solutions
- Record with permission
- Take minimal notes during interview
Step 4: Analyze Insights
python scripts/customer_interview_analyzer.py transcript.txt
Extracts:
- Pain points with severity
- Feature requests with priority
- Jobs to be done patterns
- Sentiment and key themes
- Notable quotes
Step 5: Synthesize Findings
- Group similar pain points across interviews
- Identify patterns (3+ mentions = pattern)
- Map to opportunity areas using Opportunity Solution Tree
- Prioritize opportunities by frequency and severity
Step 6: Validate Solutions
Before building:
- Create solution hypotheses (see
references/frameworks.md) - Test with low-fidelity prototypes
- Measure actual behavior vs stated preference
- Iterate based on feedback
- Document learnings for future research
PRD Development Process
Scope → Draft → Review → Refine → Approve → Track
Step 1: Choose Template
Select from references/prd_templates.md:
| Template | Use Case | Timeline |
|---|---|---|
| Standard PRD | Complex features, cross-team | 6-8 weeks |
| One-Page PRD | Simple features, single team | 2-4 weeks |
| Feature Brief | Exploration phase | 1 week |
| Agile Epic | Sprint-based delivery | Ongoing |
Step 2: Draft Content
- Lead with problem statement
- Define success metrics upfront
- Explicitly state out-of-scope items
- Include wireframes or mockups
Step 3: Review Cycle
- Engineering: feasibility and effort
- Design: user experience gaps
- Sales: market validation
- Support: operational impact
Step 4: Refine Based on Feedback
- Address technical constraints
- Adjust scope to fit timeline
- Document trade-off decisions
Step 5: Approval and Kickoff
- Stakeholder sign-off
- Sprint planning integration
- Communication to broader team
Step 6: Track Execution
After launch:
- Compare actual metrics vs targets
- Conduct user feedback sessions
- Document what worked and what didn't
- Update estimation accuracy data
- Share learnings with team
Tools Reference
RICE Prioritizer
Advanced RICE framework implementation with portfolio analysis.
Features:
- RICE score calculation with configurable weights
- Portfolio balance analysis (quick wins vs big bets)
- Quarterly roadmap generation based on capacity
- Multiple output formats (text, JSON, CSV)
CSV Input Format:
name,reach,impact,confidence,effort,description
User Dashboard Redesign,5000,high,high,l,Complete redesign
Mobile Push Notifications,10000,massive,medium,m,Add push support
Dark Mode,8000,medium,high,s,Dark theme option
Commands:
# Create sample data
python scripts/rice_prioritizer.py sample
# Run with default capacity (10 person-months)
python scripts/rice_prioritizer.py features.csv
# Custom capacity
python scripts/rice_prioritizer.py features.csv --capacity 20
# JSON output for integration
python scripts/rice_prioritizer.py features.csv --output json
# CSV output for spreadsheets
python scripts/rice_prioritizer.py features.csv --output csv
Customer Interview Analyzer
NLP-based interview analysis for extracting actionable insights.
Capabilities:
- Pain point extraction with severity assessment
- Feature request identification and classification
- Jobs-to-be-done pattern recognition
- Sentiment analysis per section
- Theme and quote extraction
- Competitor mention detection
Commands:
# Analyze interview transcript
python scripts/customer_interview_analyzer.py interview.txt
# JSON output for aggregation
python scripts/customer_interview_analyzer.py interview.txt json
Input/Output Examples
→ See references/input-output-examples.md for details
Integration Points
Compatible tools and platforms:
| Category | Platforms |
|---|---|
| Analytics | Amplitude, Mixpanel, Google Analytics |
| Roadmapping | ProductBoard, Aha!, Roadmunk, Productplan |
| Design | Figma, Sketch, Miro |
| Development | Jira, Linear, GitHub, Asana |
| Research | Dovetail, UserVoice, Pendo, Maze |
| Communication | Slack, Notion, Confluence |
JSON export enables integration with most tools:
# Export for Jira import
python scripts/rice_prioritizer.py features.csv --output json > priorities.json
# Export for dashboard
python scripts/customer_interview_analyzer.py interview.txt json > insights.json
Common Pitfalls to Avoid
| Pitfall | Description | Prevention |
|---|---|---|
| Solution-First | Jumping to features before understanding problems | Start every PRD with problem statement |
| Analysis Paralysis | Over-researching without shipping | Set time-boxes for research phases |
| Feature Factory | Shipping features without measuring impact | Define success metrics before building |
| Ignoring Tech Debt | Not allocating time for platform health | Reserve 20% capacity for maintenance |
| Stakeholder Surprise | Not communicating early and often | Weekly async updates, monthly demos |
| Metric Theater | Optimizing vanity metrics over real value | Tie metrics to user value delivered |
Best Practices
Writing Great PRDs:
- Start with the problem, not the solution
- Include clear success metrics upfront
- Explicitly state what's out of scope
- Use visuals (wireframes, flows, diagrams)
- Keep technical details in appendix
- Version control all changes
Effective Prioritization:
- Mix quick wins with strategic bets
- Consider opportunity cost of delays
- Account for dependencies between features
- Buffer 20% for unexpected work
- Revisit priorities quarterly
- Communicate decisions with context
Customer Discovery:
- Ask "why" five times to find root cause
- Focus on past behavior, not future intentions
- Avoid leading questions ("Wouldn't you love...")
- Interview in the user's natural environment
- Watch for emotional reactions (pain = opportunity)
- Validate qualitative with quantitative data
Quick Reference
# Prioritization
python scripts/rice_prioritizer.py features.csv --capacity 15
# Interview Analysis
python scripts/customer_interview_analyzer.py interview.txt
# Generate sample data
python scripts/rice_prioritizer.py sample
# JSON outputs
python scripts/rice_prioritizer.py features.csv --output json
python scripts/customer_interview_analyzer.py interview.txt json
Reference Documents
references/prd_templates.md- PRD templates for different contextsreferences/frameworks.md- Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)
| 1 | |
| 2 | name "product-manager-toolkit" |
| 3 | description Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy. |
| 4 | |
| 5 | |
| 6 | # Product Manager Toolkit |
| 7 | |
| 8 | Essential tools and frameworks for modern product management, from discovery to delivery. |
| 9 | |
| 10 | |
| 11 | |
| 12 | ## Table of Contents |
| 13 | |
| 14 | [Quick Start] |
| 15 | [Core Workflows] |
| 16 | [Feature Prioritization] |
| 17 | [Customer Discovery] |
| 18 | [PRD Development] |
| 19 | [Tools Reference] |
| 20 | [RICE Prioritizer] |
| 21 | [Customer Interview Analyzer] |
| 22 | [Input/Output Examples] |
| 23 | [Integration Points] |
| 24 | [Common Pitfalls] |
| 25 | |
| 26 | |
| 27 | |
| 28 | ## Quick Start |
| 29 | |
| 30 | ### For Feature Prioritization |
| 31 | |
| 32 | # Create sample data file |
| 33 | python scripts/rice_prioritizer.py sample |
| 34 | |
| 35 | # Run prioritization with team capacity |
| 36 | python scripts/rice_prioritizer.py sample_features.csv --capacity 15 |
| 37 | |
| 38 | |
| 39 | ### For Interview Analysis |
| 40 | |
| 41 | python scripts/customer_interview_analyzer.py interview_transcript.txt |
| 42 | |
| 43 | |
| 44 | ### For PRD Creation |
| 45 | Choose template from `references/prd_templates.md` |
| 46 | Fill sections based on discovery work |
| 47 | Review with engineering for feasibility |
| 48 | Version control in project management tool |
| 49 | |
| 50 | |
| 51 | |
| 52 | ## Core Workflows |
| 53 | |
| 54 | ### Feature Prioritization Process |
| 55 | |
| 56 | |
| 57 | Gather → Score → Analyze → Plan → Validate → Execute |
| 58 | |
| 59 | |
| 60 | #### Step 1: Gather Feature Requests |
| 61 | Customer feedback (support tickets, interviews) |
| 62 | Sales requests (CRM pipeline blockers) |
| 63 | Technical debt (engineering input) |
| 64 | Strategic initiatives (leadership goals) |
| 65 | |
| 66 | #### Step 2: Score with RICE |
| 67 | |
| 68 | # Input: CSV with features |
| 69 | python scripts/rice_prioritizer.py features.csv --capacity 20 |
| 70 | |
| 71 | |
| 72 | See `references/frameworks.md` for RICE formula and scoring guidelines. |
| 73 | |
| 74 | #### Step 3: Analyze Portfolio |
| 75 | Review the tool output for: |
| 76 | Quick wins vs big bets distribution |
| 77 | Effort concentration (avoid all XL projects) |
| 78 | Strategic alignment gaps |
| 79 | |
| 80 | #### Step 4: Generate Roadmap |
| 81 | Quarterly capacity allocation |
| 82 | Dependency identification |
| 83 | Stakeholder communication plan |
| 84 | |
| 85 | #### Step 5: Validate Results |
| 86 | **Before finalizing the roadmap:** |
| 87 | [ ] Compare top priorities against strategic goals |
| 88 | [ ] Run sensitivity analysis (what if estimates are wrong by 2x?) |
| 89 | [ ] Review with key stakeholders for blind spots |
| 90 | [ ] Check for missing dependencies between features |
| 91 | [ ] Validate effort estimates with engineering |
| 92 | |
| 93 | #### Step 6: Execute and Iterate |
| 94 | Share roadmap with team |
| 95 | Track actual vs estimated effort |
| 96 | Revisit priorities quarterly |
| 97 | Update RICE inputs based on learnings |
| 98 | |
| 99 | |
| 100 | |
| 101 | ### Customer Discovery Process |
| 102 | |
| 103 | |
| 104 | Plan → Recruit → Interview → Analyze → Synthesize → Validate |
| 105 | |
| 106 | |
| 107 | #### Step 1: Plan Research |
| 108 | Define research questions |
| 109 | Identify target segments |
| 110 | Create interview script (see `references/frameworks.md`) |
| 111 | |
| 112 | #### Step 2: Recruit Participants |
| 113 | 5-8 interviews per segment |
| 114 | Mix of power users and churned users |
| 115 | Incentivize appropriately |
| 116 | |
| 117 | #### Step 3: Conduct Interviews |
| 118 | Use semi-structured format |
| 119 | Focus on problems, not solutions |
| 120 | Record with permission |
| 121 | Take minimal notes during interview |
| 122 | |
| 123 | #### Step 4: Analyze Insights |
| 124 | |
| 125 | python scripts/customer_interview_analyzer.py transcript.txt |
| 126 | |
| 127 | |
| 128 | Extracts: |
| 129 | Pain points with severity |
| 130 | Feature requests with priority |
| 131 | Jobs to be done patterns |
| 132 | Sentiment and key themes |
| 133 | Notable quotes |
| 134 | |
| 135 | #### Step 5: Synthesize Findings |
| 136 | Group similar pain points across interviews |
| 137 | Identify patterns (3+ mentions = pattern) |
| 138 | Map to opportunity areas using Opportunity Solution Tree |
| 139 | Prioritize opportunities by frequency and severity |
| 140 | |
| 141 | #### Step 6: Validate Solutions |
| 142 | **Before building:** |
| 143 | [ ] Create solution hypotheses (see `references/frameworks.md`) |
| 144 | [ ] Test with low-fidelity prototypes |
| 145 | [ ] Measure actual behavior vs stated preference |
| 146 | [ ] Iterate based on feedback |
| 147 | [ ] Document learnings for future research |
| 148 | |
| 149 | |
| 150 | |
| 151 | ### PRD Development Process |
| 152 | |
| 153 | |
| 154 | Scope → Draft → Review → Refine → Approve → Track |
| 155 | |
| 156 | |
| 157 | #### Step 1: Choose Template |
| 158 | Select from `references/prd_templates.md`: |
| 159 | |
| 160 | | Template | Use Case | Timeline | |
| 161 | |----------|----------|----------| |
| 162 | | Standard PRD | Complex features, cross-team | 6-8 weeks | |
| 163 | | One-Page PRD | Simple features, single team | 2-4 weeks | |
| 164 | | Feature Brief | Exploration phase | 1 week | |
| 165 | | Agile Epic | Sprint-based delivery | Ongoing | |
| 166 | |
| 167 | #### Step 2: Draft Content |
| 168 | Lead with problem statement |
| 169 | Define success metrics upfront |
| 170 | Explicitly state out-of-scope items |
| 171 | Include wireframes or mockups |
| 172 | |
| 173 | #### Step 3: Review Cycle |
| 174 | Engineering: feasibility and effort |
| 175 | Design: user experience gaps |
| 176 | Sales: market validation |
| 177 | Support: operational impact |
| 178 | |
| 179 | #### Step 4: Refine Based on Feedback |
| 180 | Address technical constraints |
| 181 | Adjust scope to fit timeline |
| 182 | Document trade-off decisions |
| 183 | |
| 184 | #### Step 5: Approval and Kickoff |
| 185 | Stakeholder sign-off |
| 186 | Sprint planning integration |
| 187 | Communication to broader team |
| 188 | |
| 189 | #### Step 6: Track Execution |
| 190 | **After launch:** |
| 191 | [ ] Compare actual metrics vs targets |
| 192 | [ ] Conduct user feedback sessions |
| 193 | [ ] Document what worked and what didn't |
| 194 | [ ] Update estimation accuracy data |
| 195 | [ ] Share learnings with team |
| 196 | |
| 197 | |
| 198 | |
| 199 | ## Tools Reference |
| 200 | |
| 201 | ### RICE Prioritizer |
| 202 | |
| 203 | Advanced RICE framework implementation with portfolio analysis. |
| 204 | |
| 205 | **Features:** |
| 206 | RICE score calculation with configurable weights |
| 207 | Portfolio balance analysis (quick wins vs big bets) |
| 208 | Quarterly roadmap generation based on capacity |
| 209 | Multiple output formats (text, JSON, CSV) |
| 210 | |
| 211 | **CSV Input Format:** |
| 212 | |
| 213 | name,reach,impact,confidence,effort,description |
| 214 | User Dashboard Redesign,5000,high,high,l,Complete redesign |
| 215 | Mobile Push Notifications,10000,massive,medium,m,Add push support |
| 216 | Dark Mode,8000,medium,high,s,Dark theme option |
| 217 | |
| 218 | |
| 219 | **Commands:** |
| 220 | |
| 221 | # Create sample data |
| 222 | python scripts/rice_prioritizer.py sample |
| 223 | |
| 224 | # Run with default capacity (10 person-months) |
| 225 | python scripts/rice_prioritizer.py features.csv |
| 226 | |
| 227 | # Custom capacity |
| 228 | python scripts/rice_prioritizer.py features.csv --capacity 20 |
| 229 | |
| 230 | # JSON output for integration |
| 231 | python scripts/rice_prioritizer.py features.csv --output json |
| 232 | |
| 233 | # CSV output for spreadsheets |
| 234 | python scripts/rice_prioritizer.py features.csv --output csv |
| 235 | |
| 236 | |
| 237 | |
| 238 | |
| 239 | ### Customer Interview Analyzer |
| 240 | |
| 241 | NLP-based interview analysis for extracting actionable insights. |
| 242 | |
| 243 | **Capabilities:** |
| 244 | Pain point extraction with severity assessment |
| 245 | Feature request identification and classification |
| 246 | Jobs-to-be-done pattern recognition |
| 247 | Sentiment analysis per section |
| 248 | Theme and quote extraction |
| 249 | Competitor mention detection |
| 250 | |
| 251 | **Commands:** |
| 252 | |
| 253 | # Analyze interview transcript |
| 254 | python scripts/customer_interview_analyzer.py interview.txt |
| 255 | |
| 256 | # JSON output for aggregation |
| 257 | python scripts/customer_interview_analyzer.py interview.txt json |
| 258 | |
| 259 | |
| 260 | |
| 261 | |
| 262 | ## Input/Output Examples |
| 263 | → See references/input-output-examples.md for details |
| 264 | |
| 265 | ## Integration Points |
| 266 | |
| 267 | Compatible tools and platforms: |
| 268 | |
| 269 | | Category | Platforms | |
| 270 | |----------|-----------| |
| 271 | | **Analytics** | Amplitude, Mixpanel, Google Analytics | |
| 272 | | **Roadmapping** | ProductBoard, Aha!, Roadmunk, Productplan | |
| 273 | | **Design** | Figma, Sketch, Miro | |
| 274 | | **Development** | Jira, Linear, GitHub, Asana | |
| 275 | | **Research** | Dovetail, UserVoice, Pendo, Maze | |
| 276 | | **Communication** | Slack, Notion, Confluence | |
| 277 | |
| 278 | **JSON export enables integration with most tools:** |
| 279 | |
| 280 | # Export for Jira import |
| 281 | python scripts/rice_prioritizer.py features.csv --output json > priorities.json |
| 282 | |
| 283 | # Export for dashboard |
| 284 | python scripts/customer_interview_analyzer.py interview.txt json > insights.json |
| 285 | |
| 286 | |
| 287 | |
| 288 | |
| 289 | ## Common Pitfalls to Avoid |
| 290 | |
| 291 | | Pitfall | Description | Prevention | |
| 292 | |---------|-------------|------------| |
| 293 | | **Solution-First** | Jumping to features before understanding problems | Start every PRD with problem statement | |
| 294 | | **Analysis Paralysis** | Over-researching without shipping | Set time-boxes for research phases | |
| 295 | | **Feature Factory** | Shipping features without measuring impact | Define success metrics before building | |
| 296 | | **Ignoring Tech Debt** | Not allocating time for platform health | Reserve 20% capacity for maintenance | |
| 297 | | **Stakeholder Surprise** | Not communicating early and often | Weekly async updates, monthly demos | |
| 298 | | **Metric Theater** | Optimizing vanity metrics over real value | Tie metrics to user value delivered | |
| 299 | |
| 300 | |
| 301 | |
| 302 | ## Best Practices |
| 303 | |
| 304 | **Writing Great PRDs:** |
| 305 | Start with the problem, not the solution |
| 306 | Include clear success metrics upfront |
| 307 | Explicitly state what's out of scope |
| 308 | Use visuals (wireframes, flows, diagrams) |
| 309 | Keep technical details in appendix |
| 310 | Version control all changes |
| 311 | |
| 312 | **Effective Prioritization:** |
| 313 | Mix quick wins with strategic bets |
| 314 | Consider opportunity cost of delays |
| 315 | Account for dependencies between features |
| 316 | Buffer 20% for unexpected work |
| 317 | Revisit priorities quarterly |
| 318 | Communicate decisions with context |
| 319 | |
| 320 | **Customer Discovery:** |
| 321 | Ask "why" five times to find root cause |
| 322 | Focus on past behavior, not future intentions |
| 323 | Avoid leading questions ("Wouldn't you love...") |
| 324 | Interview in the user's natural environment |
| 325 | Watch for emotional reactions (pain = opportunity) |
| 326 | Validate qualitative with quantitative data |
| 327 | |
| 328 | |
| 329 | |
| 330 | ## Quick Reference |
| 331 | |
| 332 | |
| 333 | # Prioritization |
| 334 | python scripts/rice_prioritizer.py features.csv --capacity 15 |
| 335 | |
| 336 | # Interview Analysis |
| 337 | python scripts/customer_interview_analyzer.py interview.txt |
| 338 | |
| 339 | # Generate sample data |
| 340 | python scripts/rice_prioritizer.py sample |
| 341 | |
| 342 | # JSON outputs |
| 343 | python scripts/rice_prioritizer.py features.csv --output json |
| 344 | python scripts/customer_interview_analyzer.py interview.txt json |
| 345 | |
| 346 | |
| 347 | |
| 348 | |
| 349 | ## Reference Documents |
| 350 | |
| 351 | `references/prd_templates.md` - PRD templates for different contexts |
| 352 | `references/frameworks.md` - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.) |
| 353 |
Discussion
Browse more free Claude skills or everything in Product.