product-team/skills/product-manager-toolkit/SKILL.md
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.
npx skillsauth add alirezarezvani/claude-skills product-manager-toolkitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Essential tools and frameworks for modern product management, from discovery to delivery.
# 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
python scripts/customer_interview_analyzer.py interview_transcript.txt
references/prd_templates.mdGather → Score → Analyze → Plan → Validate → Execute
# Input: CSV with features
python scripts/rice_prioritizer.py features.csv --capacity 20
See references/frameworks.md for RICE formula and scoring guidelines.
Review the tool output for:
Before finalizing the roadmap:
Plan → Recruit → Interview → Analyze → Synthesize → Validate
references/frameworks.md)python scripts/customer_interview_analyzer.py transcript.txt
Extracts:
Before building:
references/frameworks.md)Scope → Draft → Review → Refine → Approve → Track
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 |
After launch:
Advanced RICE framework implementation with portfolio analysis.
Features:
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
NLP-based interview analysis for extracting actionable insights.
Capabilities:
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
→ See references/input-output-examples.md for details
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
| 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 |
Writing Great PRDs:
Effective Prioritization:
Customer Discovery:
# 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
references/prd_templates.md - PRD templates for different contextsreferences/frameworks.md - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.