Product Skills
Coordinates a set of product-management sub-skills — prioritization, discovery, UX research, competitive teardown, analytics, roadmapping.
Before & after
Same prompt, same agent — the only difference is the skill.
RICE is a solid prioritization framework—it looks at Reach, Impact, Confidence, and Effort. You'd score each feature on those dimensions, then divide impact by effort weighted by reach and confidence. It's pretty straightforward conceptually, but getting consistent scoring across your team takes some work. The challenge is getting people to actually agree on what the numbers mean. You'd probably want to do a workshop with your product team and maybe some key stakeholders.
PRODUCT PRIORITIZATION: RICE SCORING MATRIX FRAMEWORK BREAKDOWN RICE = (Reach × Impact × Confidence) / Effort Scoring scale: Reach (users/month), Impact (1-3 scale), Confidence (%, 0-100), Effort (person-weeks) FEATURE SCORECARD 1. NATIVE DARK MODE Reach: 3,200 monthly active users Impact: 2 (nice-to-have, improves UX) Confidence: 95% (low uncertainty) Effort: 6 weeks RICE Score: (3200 × 2 × 0.95) / 6 = 1,013 2. BULK EXPORT TO CSV Reach: 800 users Impact: 3 (high value for enterprise) Confidence: 85% (some UX questions) Effort: 3 weeks RICE Score: (800 × 3 × 0.85) / 3 = 680 3. MOBILE APP LAUNCH Reach: 12,000 users (all users on mobile) Impact: 2 (incremental, not core feature) Confidence: 70% (mobile adoption unknown) Effort: 22 weeks RICE Score: (12000 × 2 × 0.70) / 22 = 764 4. REAL-TIME NOTIFICATIONS Reach: 5,600 users Impact: 3 (critical for power users) Confidence: 80% (requires new infrastructure) Effort: 12 weeks RICE Score: (5600 × 3 × 0.80) / 12 = 1,120 5. API ACCESS FOR INTEGRATIONS Reach: 2,100 users Impact: 3 (unlocks integrations) Confidence: 90% Effort: 10 weeks RICE Score: (2100 × 3 × 0.90) / 10 = 567 6. CUSTOM REPORTING TEMPLATES Reach: 4,200 users Impact: 2 (good-to-have) Confidence: 85% Effort: 8 weeks RICE Score: (4200 × 2 × 0.85) / 8 = 893 RANKED BY RICE SCORE 1. Real-time notifications (1,120) → PRIORITY 1 2. Native dark mode (1,013) → PRIORITY 2 3. Custom reporting templates (893) → PRIORITY 3 4. Mobile app launch (764) → PRIORITY 4 (reconsider scope) 5. Bulk CSV export (680) → PRIORITY 5 6. API access (567) → PRIORITY 6 QUARTERLY ROADMAP (Q3 capacity: 28 weeks) Q3 Sprint 1 (weeks 1-12): • Real-time notifications (12 weeks) → COMPLETE Q3 Sprint 2 (weeks 13-28): • Dark mode (6 weeks) → COMPLETE • Custom reporting (8 weeks) → COMPLETE • Buffer (6 weeks) → Reserve for bugs + scope creep OPPORTUNITY COST ANALYSIS Mobile app scores lower than 4 individual features. Recommend: Descope to mobile web responsive instead (2 weeks, score 720). Full native app → backlog for Q4. KEY INSIGHTS → Real-time notifications and dark mode both essential → Mobile app is effort-heavy; web-responsive is better ROI → API access enables customer integrations (consider bundling with #1) → Revisit mobile reach assumption (may be underestimated)
About this skill
name: product-skills description: Use when Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo,...
Product Skills
Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the product-skills skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Product Skills; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: product-skills
description: Use when coordinating product work across a set of bundled product sub-skills — prioritization, discovery, research, and delivery — routing each request to the right one.
version: 1.0.0
category: Business & Ops / Product
author: AgentVolt
license: proprietary
tags:
- business-ops
- product
---
# Product Skills
Coordinates a set of product-management sub-skills — prioritization, discovery, UX research, competitive teardown, analytics, roadmapping — by routing each request to the right one and returning a compact digest.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Manager Toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies.
Experiment Designer
Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
UX Researcher & Designer
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis.
Product Discovery
Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.