agentleFS
darkweb19darkweb19/skills/product-manager-toolkit/SKILL.md

product-manager-toolkit

Skill0 starsChanged 30 days agoApache-2.0View on GitHub

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.

23 other projects use a version of this, 15 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use csv-data-summarizer, data-storytelling and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • coffeefuelbumpSkill

    csv-data-summarizer

    Analyzes CSV files, generates summary stats, and plots quick visualizations using Python and pandas.

    Also in 3 projects that use this

  • xfstudioSkill

    data-storytelling

    Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

    Also in 3 projects that use this

  • chrisvoncsefalvaySkill

    d3-viz

    Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.

    Also in 3 projects that use this

  • ruvnetSkill

    github-workflow-automation

    Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

    Also in 4 projects that use this

  • JetBrainsSkill

    slack-gif-creator

    Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.

    Also in 3 projects that use this

  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 3 are common, 4 are distinctive, and 1 is very specific to this project.

  • 3

    Common

    Most of the 18 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update RICE inputs based on learnings

    line 97
  2. Very specific:

    Create interview script (see references/frameworks.md)

    line 110
  3. Common:

    Start with the problem, not the solution

    line 305
  4. Common:

    Use visuals (wireframes, flows, diagrams)

    line 308
  5. Common:

    Keep technical details in appendix

    line 309
  6. Distinctive:

    Consider opportunity cost of delays

    line 314
  7. Distinctive:

    Ask "why" five times to find root cause

    line 321
  8. Distinctive:

    Avoid leading questions ("Wouldn't you love...")

    line 323

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Manager Toolkit

Essential tools and frameworks for modern product management, from discovery to delivery.


Table of Contents

  • Quick Start
  • Core Workflows
    • Feature Prioritization
    • Customer Discovery
    • PRD Development
  • Tools Reference
    • RICE Prioritizer
    • Customer Interview Analyzer
  • Input/Output Examples
  • Integration Points
  • Common Pitfalls

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.)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.