product-manager-toolkit
Skill12 starsChanged 14 days agoMITView on GitHub
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. In AKILI-SPECS projects, follow the AKILI-SPECS Integration section first.
26 other projects use a version of this, 21 of them edited.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillsedited, first seen Nov 16, 2026
- Ivan-propio/claude-skillsedited, first seen Nov 16, 2026
- JPeetz/agent-skillstheir own version, first seen Nov 15, 2026
- darkweb19/skillsedited, first seen Nov 8, 2026
- amanuelmamo7/Skillsedited, first seen Nov 7, 2026
- OpenxIntelligence/Coding-Agent-Skillsedited, first seen Nov 1, 2026
Used with
Projects with it also use marketing-demand-acquisition, csv-data-summarizer and 10 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.
harriswatSkillmarketing-demand-acquisition
Multi-channel demand generation, paid media optimization, SEO strategy, and partnership programs for Series A+ startups. Includes CAC calculator, channel playbooks, HubSpot integration, and international expansion tactics. Use when planning demand generation campaigns, optimizing paid media, building SEO strategies, establishing partnerships, or when user mentions demand gen, paid ads, LinkedIn ads, Google ads, CAC, acquisition, lead generation, or pipeline generation.
Also in 3 projects that use this
coffeefuelbumpSkillcsv-data-summarizer
Analyzes CSV files, generates summary stats, and plots quick visualizations using Python and pandas.
Also in 3 projects that use this
xfstudioSkilldata-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
chrisvoncsefalvaySkilld3-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
xfstudioSkillcontent-creator
Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.
Also in 3 projects that use this
ruvnetSkillgithub-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
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 21
- anbeime/skill★ 7.9k72% same
- Hassaan146/claude-skills★ 1820% same
- xfstudio/skills★ 999% same
- I-Onlabs/claude-code-skills★ 499% same
- nek1987/auto-agent-harness★ 499% same
- OpenxIntelligence/Coding-Agent-Skills★ 499% same
- ai4brands-design/claude-skills★ 299% same
- dycnnnb/skills★ 273% same
- Hussain-Elfalah/Agentic-Skills★ 221% same
- Oceanjackson1/Claude-Skill★ 297% same
11 more not listed
Wrote their own version · 5
- JPeetz/agent-skills★ 17same name
- skytiger6724/qwen-skills★ 2same name
- Gopyr/gopyr-skills-hub★ 0same name
- karim-bhalwani/agent-skills-collection★ 0same name
- viasrijan/crazy-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/skills/react-doctor/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-agent-developmentSkill
- angular-developerSkill
- api-design-principlesSkill
- aws-serverlessSkill
- brainstormingSkill
- cavemanSkill
- cognitive-doc-designSkill
- diagram-designSkill
- error-handling-patternsSkill
- frontend-designSkill
- golang-proSkill
- gsap-animationSkill
- impeccable-bridgeSkill
- impeccableSkill
- judgment-daySkill
- kaizenSkill
- nestjs-expertSkill
- pr-reviewSkill
- react-doctorSkill
- security-auditSkill
- seo-auditSkill
- shadcn-uiSkill
- social-marketingSkill
- software-architectSkill
- stitch-designSkill
- systematic-debuggingSkill
- tailwind-design-systemSkill
- tddSkill
- ui-ux-pro-maxSkill
- vercel-react-best-practicesSkill
- video-productionSkill
The file
We split this skill into the rules it gives an agent
7 rules. 6 are common, 0 are distinctive, and 1 is very specific to this project.
6
Common
Most of the 25 edited versions we read keep these.
0
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
- Very specific: line 20
When this skill is loaded inside the AKILI-SPECS methodology, this section takes precedence over the generic workflows below.
- Common: line 311
Start with the problem, not solution
- Common: line 314
Use visuals (wireframes, flows)
- Common: line 315
Keep technical details in appendix
- Common: line 331
Look for emotional reactions
- Common: line 347
Ignoring Technical Debt: Not allocating time for platform health
- Common: line 348
Stakeholder Surprise: Not communicating early and often
“Common” is measured: kept by at least 6 in 10 of the 25 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.
Files
Product Manager Toolkit
Essential tools and frameworks for modern product management, from discovery to delivery.
AKILI-SPECS Integration
When this skill is loaded inside the AKILI-SPECS methodology, this section takes precedence over the generic workflows below. Each tool has one precise moment in the flow:
| AKILI moment | Use from this toolkit |
/akili-constitution Step 2 (Clarify Missing Business Context) | The Customer Interview Guide and Hypothesis Template as the question script. If the user has interview transcripts or raw customer feedback, offer scripts/customer_interview_analyzer.py to extract pain points, jobs-to-be-done, and themes — they feed the PRD's Problem Statement and Target Personas. |
/akili-constitution Step 3 (PRD) | The AKILI 9-section PRD structure is canonical — never substitute this toolkit's PRD templates for it. Use the toolkit to fill those sections well: North Star Metric framework for "Goals & Success Metrics", jobs-to-be-done for "Target Personas", the Hypothesis Template for "Assumptions, Dependencies, & Constraints". |
/akili-propose / /akili-specify Scope Chunking | When an epic splits into multiple specs, score the chunks with RICE (or MoSCoW for a quick pass) to recommend the build order. Treat each candidate spec as a row: name,reach,impact,confidence,effort → scripts/rice_prioritizer.py. |
/akili-propose (Change track) | The Feature Brief mindset maps to proposal.md: problem → hypothesis → success criteria. Do not create a separate brief document. |
Rules inside AKILI-SPECS:
- The scripts are optional helpers (they need Python); never block a flow on them — the frameworks work as reasoning guides on their own.
- Skip the Go-to-Market and Stakeholder Management sections during constitution work; they are out of scope for
docs/prd.md. - Output always lands in AKILI artifacts (
docs/prd.md,proposal.md, spec folders) — never in standalone PM documents.
Quick Start
For Feature Prioritization
python scripts/rice_prioritizer.py sample # Create sample CSV
python scripts/rice_prioritizer.py sample_features.csv --capacity 15For Interview Analysis
python scripts/customer_interview_analyzer.py interview_transcript.txtFor PRD Creation
- Choose template from
references/prd_templates.md - Fill in sections based on discovery work
- Review with stakeholders
- Version control in your PM tool
Core Workflows
Feature Prioritization Process
- Gather Feature Requests
- Customer feedback
- Sales requests
- Technical debt
- Strategic initiatives
- 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)
- Analyze Portfolio
- Review quick wins vs big bets
- Check effort distribution
- Validate against strategy
- Generate Roadmap
- Quarterly capacity planning
- Dependency mapping
- Stakeholder alignment
Customer Discovery Process
- Conduct Interviews
- Use semi-structured format
- Focus on problems, not solutions
- Record with permission
- Analyze Insights
Extracts:python scripts/customer_interview_analyzer.py transcript.txt- Pain points with severity
- Feature requests with priority
- Jobs to be done
- Sentiment analysis
- Key themes and quotes
- Synthesize Findings
- Group similar pain points
- Identify patterns across interviews
- Map to opportunity areas
- Validate Solutions
- Create solution hypotheses
- Test with prototypes
- Measure actual vs expected behavior
PRD Development Process
- 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
- Structure Content
- Problem → Solution → Success Metrics
- Always include out-of-scope
- Clear acceptance criteria
- 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 jsoncustomer_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 jsonReference Documents
prd_templates.md
Multiple PRD formats for different contexts:
- Standard PRD Template
- Comprehensive 11-section format
- Best for major features
- Includes technical specs
- One-Page PRD
- Concise format for quick alignment
- Focus on problem/solution/metrics
- Good for smaller features
- Agile Epic Template
- Sprint-based delivery
- User story mapping
- Acceptance criteria focus
- 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-monthsValue 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 permissionHypothesis 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 DMetrics & Analytics
North Star Metric Framework
- Identify Core Value: What's the #1 value to users?
- Make it Measurable: Quantifiable and trackable
- Ensure It's Actionable: Teams can influence it
- 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 variationsFeature 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
- Start with the problem, not solution
- Include clear success metrics upfront
- Explicitly state what's out of scope
- Use visuals (wireframes, flows)
- Keep technical details in appendix
- Version control changes
Effective Prioritization
- Mix quick wins with strategic bets
- Consider opportunity cost
- Account for dependencies
- Buffer for unexpected work (20%)
- Revisit quarterly
- Communicate decisions clearly
Customer Discovery Tips
- Ask "why" 5 times
- Focus on past behavior, not future intentions
- Avoid leading questions
- Interview in their environment
- Look for emotional reactions
- Validate with data
Stakeholder Management
- Identify RACI for decisions
- Regular async updates
- Demo over documentation
- Address concerns early
- Celebrate wins publicly
- Learn from failures openly
Common Pitfalls to Avoid
- Solution-First Thinking: Jumping to features before understanding problems
- Analysis Paralysis: Over-researching without shipping
- Feature Factory: Shipping features without measuring impact
- Ignoring Technical Debt: Not allocating time for platform health
- Stakeholder Surprise: Not communicating early and often
- 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 jsonDoes 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
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.

