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
最近更新
2026-11-01
Stars
★ 3
Forks
1

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 资源文件 3

03 SKILL.md 正文

Product Manager Toolkit

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

Quick Start

For Feature Prioritization

python scripts/rice_prioritizer.py sample  # Create sample CSV
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 in sections based on discovery work
  3. Review with stakeholders
  4. Version control in your PM tool

Core Workflows

Feature Prioritization Process

  1. Gather Feature Requests

    • Customer feedback
    • Sales requests
    • Technical debt
    • Strategic initiatives
  2. Score with RICE

    # Create CSV with: name,reach,impact,confidence,effort
    python scripts/rice_prioritizer.py features.csv
    
    • Reach: Users affected per quarter
    • Impact: massive/high/medium/low/minimal
    • Confidence: high/medium/low
    • Effort: xl/l/m/s/xs (person-months)
  3. Analyze Portfolio

    • Review quick wins vs big bets
    • Check effort distribution
    • Validate against strategy
  4. Generate Roadmap

    • Quarterly capacity planning
    • Dependency mapping
    • Stakeholder alignment

Customer Discovery Process

  1. Conduct Interviews

    • Use semi-structured format
    • Focus on problems, not solutions
    • Record with permission
  2. Analyze Insights

    python scripts/customer_interview_analyzer.py transcript.txt
    

    Extracts:

    • Pain points with severity
    • Feature requests with priority
    • Jobs to be done
    • Sentiment analysis
    • Key themes and quotes
  3. Synthesize Findings

    • Group similar pain points
    • Identify patterns across interviews
    • Map to opportunity areas
  4. Validate Solutions

    • Create solution hypotheses
    • Test with prototypes
    • Measure actual vs expected behavior

PRD Development Process

  1. Choose Template

    • Standard PRD: Complex features (6-8 weeks)
    • One-Page PRD: Simple features (2-4 weeks)
    • Feature Brief: Exploration phase (1 week)
    • Agile Epic: Sprint-based delivery
  2. Structure Content

    • Problem → Solution → Success Metrics
    • Always include out-of-scope
    • Clear acceptance criteria
  3. Collaborate

    • Engineering for feasibility
    • Design for experience
    • Sales for market validation
    • Support for operational impact

Key Scripts

rice_prioritizer.py

Advanced RICE framework implementation with portfolio analysis.

Features:

  • RICE score calculation
  • Portfolio balance analysis (quick wins vs big bets)
  • Quarterly roadmap generation
  • Team capacity planning
  • Multiple output formats (text/json/csv)

Usage Examples:

# Basic prioritization
python scripts/rice_prioritizer.py features.csv

# With custom team capacity (person-months per quarter)
python scripts/rice_prioritizer.py features.csv --capacity 20

# Output as JSON for integration
python scripts/rice_prioritizer.py features.csv --output json

customer_interview_analyzer.py

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
  • Theme extraction
  • Competitor mentions
  • Key quotes identification

Usage Examples:

# Analyze single interview
python scripts/customer_interview_analyzer.py interview.txt

# Output as JSON for aggregation
python scripts/customer_interview_analyzer.py interview.txt json

Reference Documents

prd_templates.md

Multiple PRD formats for different contexts:

  1. Standard PRD Template

    • Comprehensive 11-section format
    • Best for major features
    • Includes technical specs
  2. One-Page PRD

    • Concise format for quick alignment
    • Focus on problem/solution/metrics
    • Good for smaller features
  3. Agile Epic Template

    • Sprint-based delivery
    • User story mapping
    • Acceptance criteria focus
  4. Feature Brief

    • Lightweight exploration
    • Hypothesis-driven
    • Pre-PRD phase

Prioritization Frameworks

RICE Framework

Score = (Reach × Impact × Confidence) / Effort

Reach: # of users/quarter
Impact: 
  - Massive = 3x
  - High = 2x
  - Medium = 1x
  - Low = 0.5x
  - Minimal = 0.25x
Confidence:
  - High = 100%
  - Medium = 80%
  - Low = 50%
Effort: Person-months

Value vs Effort Matrix

         Low Effort    High Effort
         
High     QUICK WINS    BIG BETS
Value    [Prioritize]   [Strategic]
         
Low      FILL-INS      TIME SINKS
Value    [Maybe]       [Avoid]

MoSCoW Method

  • Must Have: Critical for launch
  • Should Have: Important but not critical
  • Could Have: Nice to have
  • Won't Have: Out of scope

Discovery Frameworks

Customer Interview Guide

1. Context Questions (5 min)
   - Role and responsibilities
   - Current workflow
   - Tools used

2. Problem Exploration (15 min)
   - Pain points
   - Frequency and impact
   - Current workarounds

3. Solution Validation (10 min)
   - Reaction to concepts
   - Value perception
   - Willingness to pay

4. Wrap-up (5 min)
   - Other thoughts
   - Referrals
   - Follow-up permission

Hypothesis Template

We believe that [building this feature]
For [these users]
Will [achieve this outcome]
We'll know we're right when [metric]

Opportunity Solution Tree

Outcome
├── Opportunity 1
│   ├── Solution A
│   └── Solution B
└── Opportunity 2
    ├── Solution C
    └── Solution D

Metrics & Analytics

North Star Metric Framework

  1. Identify Core Value: What's the #1 value to users?
  2. Make it Measurable: Quantifiable and trackable
  3. Ensure It's Actionable: Teams can influence it
  4. Check Leading Indicator: Predicts business success

Funnel Analysis Template

Acquisition → Activation → Retention → Revenue → Referral

Key Metrics:
- Conversion rate at each step
- Drop-off points
- Time between steps
- Cohort variations

Feature Success Metrics

  • Adoption: % of users using feature
  • Frequency: Usage per user per time period
  • Depth: % of feature capability used
  • Retention: Continued usage over time
  • Satisfaction: NPS/CSAT for feature

Best Practices

Writing Great PRDs

  1. Start with the problem, not solution
  2. Include clear success metrics upfront
  3. Explicitly state what's out of scope
  4. Use visuals (wireframes, flows)
  5. Keep technical details in appendix
  6. Version control changes

Effective Prioritization

  1. Mix quick wins with strategic bets
  2. Consider opportunity cost
  3. Account for dependencies
  4. Buffer for unexpected work (20%)
  5. Revisit quarterly
  6. Communicate decisions clearly

Customer Discovery Tips

  1. Ask "why" 5 times
  2. Focus on past behavior, not future intentions
  3. Avoid leading questions
  4. Interview in their environment
  5. Look for emotional reactions
  6. Validate with data

Stakeholder Management

  1. Identify RACI for decisions
  2. Regular async updates
  3. Demo over documentation
  4. Address concerns early
  5. Celebrate wins publicly
  6. Learn from failures openly

Common Pitfalls to Avoid

  1. Solution-First Thinking: Jumping to features before understanding problems
  2. Analysis Paralysis: Over-researching without shipping
  3. Feature Factory: Shipping features without measuring impact
  4. Ignoring Technical Debt: Not allocating time for platform health
  5. Stakeholder Surprise: Not communicating early and often
  6. Metric Theater: Optimizing vanity metrics over real value

Integration Points

This toolkit integrates with:

  • Analytics: Amplitude, Mixpanel, Google Analytics
  • Roadmapping: ProductBoard, Aha!, Roadmunk
  • Design: Figma, Sketch, Miro
  • Development: Jira, Linear, GitHub
  • Research: Dovetail, UserVoice, Pendo
  • Communication: Slack, Notion, Confluence

Quick Commands Cheat Sheet

# Prioritization
python scripts/rice_prioritizer.py features.csv --capacity 15

# Interview Analysis
python scripts/customer_interview_analyzer.py interview.txt

# Create sample data
python scripts/rice_prioritizer.py sample

# JSON outputs for integration
python scripts/rice_prioritizer.py features.csv --output json
python scripts/customer_interview_analyzer.py interview.txt json

04 同仓库更多 Skills

shengdabai
shengdabai/Tony-Claude-Code-Skills

xiaolai-methodology

以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 "李笑来"、"笑来"、"笑来老师"、"扮演李笑来"、"找笑来聊聊"、"笑来怎么看"、"xiaolai"、"把时间当作朋友"、"通往财富自由之路"、"定投改变命运"、"韭菜的自我修养"、"自学是门手艺"、"让时间陪你慢慢变富"、"七年就是一辈子"、"元认知"、"活在未来"、"复利/长期主义"、"践行"、"痴迷改进"、"个人商业模式/出售时间"、"睡后收入"、"定投"、"财富自由"、"操作系统升级"、"最少必要知识"、"北极星提示词"、"用 AI 该怎么学/思考" 等任一触发词,或当用户带着关于创业/赚钱/投资/学习/职业/重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。

写作与文案
★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

zread

Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `./.zread/wiki/`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module/package explanations, or "what does this repo do"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread / zread.ai directly. Also use it proactively before diving into a large unknown repo — if `./.zread/wiki/current` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word "zread".

开发工程师Skill与智能体开发
★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

youtube

Launch the YouTube Creator Agent to auto-generate videos. Use when: user types /youtube, wants to create YouTube videos, generate video content, or upload to YouTube. Keywords: youtube, video, 视频, 创作视频, 发布视频

内容创作者Skill与智能体开发
★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

youtube-script-sync

Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新/同步/优化 Youtube视频逐字稿知识库”, or says “更新/同步/优化该知识库” while this knowledge base is the active context.

Skill与智能体开发
★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

writing-skills

How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.

开发工程师内容创作者写作与文案Skill与智能体开发
★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

writing-rules

How to write .claude/rules/ files that Claude actually follows. Use when creating, improving, or reviewing project rules.

内容创作者写作与文案
★ 3