Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Product Manager Toolkit

  • 896 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

product-manager-toolkit is a planning skill that generates structured Product Requirements Documents turning vague ideas into clear, prioritized specifications for developers and agents who need executable product scope

About

product-manager-toolkit is a PRD generation skill from alirezarezvani/claude-skills that structures product discovery into agent-executable documents. The template includes document metadata fields for author, draft or approved status, created and updated dates, reviewers, and target release quarter. Core sections cover problem statement with user pain focus, affected user segments, evidence links from interviews, support tickets, analytics, or churn analysis, and quantified impact if the problem goes unsolved. Developers and product leads reach for product-manager-toolkit when an idea lacks clear requirements, priorities, or success criteria before agents or engineers write code. Output PRDs give coding agents concrete scope, acceptance framing, and review checkpoints instead of ambiguous feature requests.

  • Generates complete PRD templates with problem statement, user stories, solution overview, success metrics and technical
  • Enforces standardized sections including evidence-based validation and priority-ranked user stories
  • Produces artifacts that serve as hard-gate before implementation work begins
  • Includes success metrics and risk assessment fields for every project
  • Creates handoff-ready specs that feed directly into implementation planning

Product Manager Toolkit by the numbers

  • 896 all-time installs (skills.sh)
  • +12 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #528 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill product-manager-toolkit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs896
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you write a PRD agents can execute?

Generate structured Product Requirements Documents that turn vague ideas into clear, prioritized specs an agent can execute.

Who is it for?

Developers or tech leads scoping features who need a PRD template with problem, evidence, and priority sections before coding starts.

Skip if: Teams with an approved PRD already in place who only need implementation or code review without replanning scope.

When should I use this skill?

A feature idea is vague, lacks prioritized requirements, or the developer asks for a PRD before agent-driven implementation.

What you get

A structured Product Requirements Document with problem statement, user segments, evidence, priorities, and target release metadata.

  • Product Requirements Document
  • Prioritized requirement list

By the numbers

  • PRD template includes author, status, reviewers, and target release metadata fields

Files

SKILL.mdMarkdownGitHub ↗

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

1. Choose template from references/prd_templates.md 2. Fill sections based on discovery work 3. Review with engineering for feasibility 4. 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:

TemplateUse CaseTimeline
Standard PRDComplex features, cross-team6-8 weeks
One-Page PRDSimple features, single team2-4 weeks
Feature BriefExploration phase1 week
Agile EpicSprint-based deliveryOngoing
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:

CategoryPlatforms
AnalyticsAmplitude, Mixpanel, Google Analytics
RoadmappingProductBoard, Aha!, Roadmunk, Productplan
DesignFigma, Sketch, Miro
DevelopmentJira, Linear, GitHub, Asana
ResearchDovetail, UserVoice, Pendo, Maze
CommunicationSlack, 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

PitfallDescriptionPrevention
Solution-FirstJumping to features before understanding problemsStart every PRD with problem statement
Analysis ParalysisOver-researching without shippingSet time-boxes for research phases
Feature FactoryShipping features without measuring impactDefine success metrics before building
Ignoring Tech DebtNot allocating time for platform healthReserve 20% capacity for maintenance
Stakeholder SurpriseNot communicating early and oftenWeekly async updates, monthly demos
Metric TheaterOptimizing vanity metrics over real valueTie 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 contexts
  • references/frameworks.md - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)

Related skills

How it compares

Use product-manager-toolkit to scope and document requirements; switch to implementation skills once the PRD is approved.

FAQ

What sections does product-manager-toolkit include in a PRD?

product-manager-toolkit PRDs include document metadata, problem statement, affected user segments, evidence from interviews or analytics, impact if unsolved, and fields for reviewers and target release dates.

Who should use product-manager-toolkit?

product-manager-toolkit suits developers and leads with vague feature ideas who need clear, prioritized requirements documented before agents or engineers begin implementation work.

Is Product Manager Toolkit safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.