AGENT SKILL

product-manager-toolkit

Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.

License 许可
MIT
所属仓库
msm47/Gitskil
最近更新
2026-06-22
Stars
★ 0
Forks
0

01 前言 Front Matter

name
product-manager-toolkit
description
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.

02 资源文件 7

03 SKILL.md 正文

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:

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 contexts
  • references/frameworks.md - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)

04 同仓库更多 Skills

msm47
msm47/Gitskil

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.

★ 0
msm47
msm47/Gitskil

research

Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.

★ 0
msm47
msm47/Gitskil

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

★ 0
msm47
msm47/Gitskil

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

★ 0
msm47
msm47/Gitskil

notebooklm

Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.

★ 0
msm47
msm47/Gitskil

litreview

Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.

★ 0