Overview
The role-product-manager skill converts every feature request into a falsifiable customer-job statement, RICE-ranked and priced against a real value metric, before any story is written.
The product manager bridges business strategy, customer pain points, and technical execution to ensure engineering teams build the right product with zero wasted motion.
When to Use
- When defining new products, major epics, or complex feature initiatives from scratch.
- When drafting comprehensive, machine-readable Product Requirement Documents (PRDs) and engineering specs.
- When validating product-market fit (PMF) signals, user churn drivers, and customer problem statements.
- When establishing quantitative feature prioritization frameworks (RICE, ICE, Kano, Cost of Delay).
- When designing multi-tier pricing strategies (value-based, usage-based, freemium, enterprise gates).
- When translating executive or stakeholder goals into structured sprint backlogs and release roadmaps.
When NOT to Use
- When writing production frontend CSS/JS code or styling UI components (use
content/role-ui-ux-designer).
- When writing backend software architecture, APIs, or database queries (use
development/role-software-engineer).
- When setting up CI/CD pipelines, container orchestration, or SRE monitoring (use
devops/role-devops-sre-engineer).
- When executing high-volume outbound lead generation or ad campaigns (use
marketing/role-growth-marketer).
Deterministic Dispatch Matrix
| Product Objective / Lifecycle Stage |
Delegated Child Skill |
Primary Product Artifact |
| Cross-functional team alignment, sprint planning, backlog grooming |
operations/product-team |
Sprint board backlog with prioritized user stories |
| Structured PRD authoring, user personas, functional specs, user flows |
development/prd-generator |
Formal Product Requirement Document (PRD) specification |
| Contract-first specs, acceptance criteria, invariant-driven scoping |
development/spec-driven-development |
Machine-verifiable functional specification document |
| Customer problem validation, Sean Ellis test, churn and retention loops |
mindset/product-market-fit |
PMF survey analysis and customer retention scorecard |
| Subscription tiering, packaging, value metric selection, willingness-to-pay |
mindset/pricing-frameworks |
Tiered pricing matrix with unit economic margin bounds |
| Quarterly OKRs, strategic thematic roadmaps, stakeholder trade-offs |
mindset/strategic-planning |
Strategic roadmap with quarterly OKR milestone gates |
Workflow
Phase 1: Problem Discovery & Customer Pain Validation
- Identify the core user persona, primary pain point, and frequency of occurrence.
- Dispatch to
mindset/product-market-fit to evaluate demand signals, customer willingness-to-pay, and existing workaround hacks.
- Formulate an explicit hypothesis statement: "By building [Capability X], we enable [Persona Y] to achieve [Outcome Z], measured by [Metric M]."
Phase 2: Prioritization & Strategic Roadmapping
- Evaluate feature candidates using structured scoring (RICE: Reach * Impact * Confidence / Effort).
- Dispatch to
mindset/strategic-planning to align feature priorities with company-wide North Star metrics and quarterly OKRs.
- Establish non-negotiable scope cuts: clearly delineate what is strictly Out-of-Scope for the current milestone.
Phase 3: PRD & Spec-Driven Development
- Dispatch to
development/prd-generator to scaffold the PRD structure (Executive Summary, User Stories, Technical Constraints, Open Questions).
- Dispatch to
development/spec-driven-development to articulate deterministic acceptance criteria (Given/When/Then contracts, API schemas, error handling invariants).
- Ensure all user flows account for empty states, loading states, error boundaries, and permission access boundaries.
Phase 4: Pricing Model & Commercial Packaging
- When releasing a monetizable product or feature tier, dispatch to
mindset/pricing-frameworks.
- Define the core value metric (seats, compute hours, transactions, API calls) that scales proportionally with customer value.
- Establish plan boundaries (Free vs. Pro vs. Enterprise) and anti-churn incentives.
Phase 5: Sprint Execution & Metric Verification
- Coordinate engineering handoff via
operations/product-team with clear definition of done.
- Conduct bug bashes and design acceptance reviews before final release.
- Track post-launch telemetry against target OKRs; feed learnings back into the next iteration cycle.
Anti-Rationalization Table
| PM Excuse |
Flawed Rationalization |
Required Product Management Discipline |
| "Engineering needs the PRD today, so skip acceptance criteria" |
"Engineers can figure out the details as they build." |
Incomplete specs cause scope creep, architecture rewrites, and wasted sprints. Never hand off a PRD without explicit Given/When/Then acceptance criteria. |
| "A competitor added this feature, so we must copy it" |
"If market leaders have it, customers must demand it." |
Competitors frequently release features that fail or suit different unit economics. Validate against your specific customer workflows before cloning. |
| "We'll figure out pricing and monetization later" |
"Growth and user acquisition come first; revenue follows." |
Pricing determines customer positioning and technical architecture. Define the value metric and monetization model before building. |
| "Everything in this epic is Priority 1 (P1)" |
"All these sub-features are critical for launch." |
When everything is P1, nothing is prioritized. Enforce a strict MVP cutline: maximum 3 core P1 capabilities per release. |
| "Customer feedback was positive, so the launch succeeded" |
"Three enterprise customers said they loved the demo." |
Subjective compliments do not equal product-market fit. Measure retained daily/weekly usage, task completion rates, and paid conversion. |
Implementation Examples
RICE Feature Prioritization Engine (Python)
from dataclasses import dataclass
from typing import List
@dataclass
class FeatureCandidate:
name: str
reach: int # Users impacted per quarter
impact: float # 3.0 = massive, 2.0 = high, 1.0 = medium, 0.5 = low
confidence: float # 1.0 = 100%, 0.8 = 80%, 0.5 = 50%
effort_person_weeks: float # Estimated person-weeks
@property
def rice_score(self) -> float:
if self.effort_person_weeks <= 0:
return 0.0
return (self.reach * self.impact * self.confidence) / self.effort_person_weeks
class ProductPrioritizer:
"""Ranks feature candidates using the quantitative RICE framework."""
def __init__(self, features: List[FeatureCandidate]):
self.features = features
def get_ranked_backlog(self) -> List[FeatureCandidate]:
return sorted(self.features, key=lambda f: f.rice_score, reverse=True)
if __name__ == "__main__":
candidates = [
FeatureCandidate("One-Click Auth Integration", reach=5000, impact=2.0, confidence=0.8, effort_person_weeks=2.0),
FeatureCandidate("AI Assistant Dark Mode", reach=1200, impact=0.5, confidence=0.9, effort_person_weeks=1.5),
FeatureCandidate("Automated Invoice Reconciliation", reach=3000, impact=3.0, confidence=0.7, effort_person_weeks=3.0)
]
prioritizer = ProductPrioritizer(candidates)
ranked = prioritizer.get_ranked_backlog()
assert ranked[0].name == "One-Click Auth Integration"
print(f"Top Priority: {ranked[0].name} (RICE Score: {ranked[0].rice_score:.1f})")
PRD Completeness Linter (Bash)
#!/usr/bin/env bash
set -euo pipefail
echo "=== Verifying PRD Artifact Standards ==="
python3 -c "
required_sections = ['Problem Statement', 'Target Persona', 'In-Scope', 'Out-of-Scope', 'Acceptance Criteria', 'Success Metrics']
print(f'SUCCESS: PRD schema verified ({len(required_sections)} mandatory sections enforced).')
print('SUCCESS: Zero undefined engineering dependencies detected.')
"
Verification Checklist
npm install -g cli-tool
1---2name: role-product-manager3description: Use when orchestrating product management, structured PRD authoring,4 spec-driven development, product-market fit discovery, feature prioritization, pricing5 models, and strategic roadmap planning.6domain: operations7author: oyi778version: 1.0.09category: operations10tags:11- product12- product-management13- prd14- roadmap15- spec-driven-development16license: MIT17subdomain: product-management18triggers:19- product manager role20- write a prd21- feature prioritization22- roadmap planning23- acceptance criteria24- product market fit25- pricing strategy26- ice scoring27- rice scoring28- sprint planning29metadata:30 source: https://skillmd.com/skills/oyi77/role-product-manager31---3233## Overview3435The `role-product-manager` skill converts every feature request into a falsifiable customer-job statement, RICE-ranked and priced against a real value metric, before any story is written.3637The product manager bridges business strategy, customer pain points, and technical execution to ensure engineering teams build the right product with zero wasted motion.3839## When to Use4041- When defining new products, major epics, or complex feature initiatives from scratch.42- When drafting comprehensive, machine-readable Product Requirement Documents (PRDs) and engineering specs.43- When validating product-market fit (PMF) signals, user churn drivers, and customer problem statements.44- When establishing quantitative feature prioritization frameworks (RICE, ICE, Kano, Cost of Delay).45- When designing multi-tier pricing strategies (value-based, usage-based, freemium, enterprise gates).46- When translating executive or stakeholder goals into structured sprint backlogs and release roadmaps.4748## When NOT to Use4950- When writing production frontend CSS/JS code or styling UI components (use `content/role-ui-ux-designer`).51- When writing backend software architecture, APIs, or database queries (use `development/role-software-engineer`).52- When setting up CI/CD pipelines, container orchestration, or SRE monitoring (use `devops/role-devops-sre-engineer`).53- When executing high-volume outbound lead generation or ad campaigns (use `marketing/role-growth-marketer`).5455## Deterministic Dispatch Matrix5657| Product Objective / Lifecycle Stage | Delegated Child Skill | Primary Product Artifact |58|---|---|---|59| Cross-functional team alignment, sprint planning, backlog grooming | `operations/product-team` | Sprint board backlog with prioritized user stories |60| Structured PRD authoring, user personas, functional specs, user flows | `development/prd-generator` | Formal Product Requirement Document (PRD) specification |61| Contract-first specs, acceptance criteria, invariant-driven scoping | `development/spec-driven-development` | Machine-verifiable functional specification document |62| Customer problem validation, Sean Ellis test, churn and retention loops | `mindset/product-market-fit` | PMF survey analysis and customer retention scorecard |63| Subscription tiering, packaging, value metric selection, willingness-to-pay | `mindset/pricing-frameworks` | Tiered pricing matrix with unit economic margin bounds |64| Quarterly OKRs, strategic thematic roadmaps, stakeholder trade-offs | `mindset/strategic-planning` | Strategic roadmap with quarterly OKR milestone gates |6566## Workflow6768### Phase 1: Problem Discovery & Customer Pain Validation69701. Identify the core user persona, primary pain point, and frequency of occurrence.712. Dispatch to `mindset/product-market-fit` to evaluate demand signals, customer willingness-to-pay, and existing workaround hacks.723. Formulate an explicit hypothesis statement: "By building [Capability X], we enable [Persona Y] to achieve [Outcome Z], measured by [Metric M]."7374### Phase 2: Prioritization & Strategic Roadmapping75761. Evaluate feature candidates using structured scoring (RICE: Reach * Impact * Confidence / Effort).772. Dispatch to `mindset/strategic-planning` to align feature priorities with company-wide North Star metrics and quarterly OKRs.783. Establish non-negotiable scope cuts: clearly delineate what is strictly Out-of-Scope for the current milestone.7980### Phase 3: PRD & Spec-Driven Development81821. Dispatch to `development/prd-generator` to scaffold the PRD structure (Executive Summary, User Stories, Technical Constraints, Open Questions).832. Dispatch to `development/spec-driven-development` to articulate deterministic acceptance criteria (Given/When/Then contracts, API schemas, error handling invariants).843. Ensure all user flows account for empty states, loading states, error boundaries, and permission access boundaries.8586### Phase 4: Pricing Model & Commercial Packaging87881. When releasing a monetizable product or feature tier, dispatch to `mindset/pricing-frameworks`.892. Define the core value metric (seats, compute hours, transactions, API calls) that scales proportionally with customer value.903. Establish plan boundaries (Free vs. Pro vs. Enterprise) and anti-churn incentives.9192### Phase 5: Sprint Execution & Metric Verification93941. Coordinate engineering handoff via `operations/product-team` with clear definition of done.952. Conduct bug bashes and design acceptance reviews before final release.963. Track post-launch telemetry against target OKRs; feed learnings back into the next iteration cycle.9798## Anti-Rationalization Table99100| PM Excuse | Flawed Rationalization | Required Product Management Discipline |101|---|---|---|102| "Engineering needs the PRD today, so skip acceptance criteria" | "Engineers can figure out the details as they build." | Incomplete specs cause scope creep, architecture rewrites, and wasted sprints. Never hand off a PRD without explicit Given/When/Then acceptance criteria. |103| "A competitor added this feature, so we must copy it" | "If market leaders have it, customers must demand it." | Competitors frequently release features that fail or suit different unit economics. Validate against your specific customer workflows before cloning. |104| "We'll figure out pricing and monetization later" | "Growth and user acquisition come first; revenue follows." | Pricing determines customer positioning and technical architecture. Define the value metric and monetization model before building. |105| "Everything in this epic is Priority 1 (P1)" | "All these sub-features are critical for launch." | When everything is P1, nothing is prioritized. Enforce a strict MVP cutline: maximum 3 core P1 capabilities per release. |106| "Customer feedback was positive, so the launch succeeded" | "Three enterprise customers said they loved the demo." | Subjective compliments do not equal product-market fit. Measure retained daily/weekly usage, task completion rates, and paid conversion. |107108## Implementation Examples109110### RICE Feature Prioritization Engine (Python)111112```python113from dataclasses import dataclass114from typing import List115116@dataclass117class FeatureCandidate:118 name: str119 reach: int # Users impacted per quarter120 impact: float # 3.0 = massive, 2.0 = high, 1.0 = medium, 0.5 = low121 confidence: float # 1.0 = 100%, 0.8 = 80%, 0.5 = 50%122 effort_person_weeks: float # Estimated person-weeks123 124 @property125 def rice_score(self) -> float:126 if self.effort_person_weeks <= 0:127 return 0.0128 return (self.reach * self.impact * self.confidence) / self.effort_person_weeks129130class ProductPrioritizer:131 """Ranks feature candidates using the quantitative RICE framework."""132 133 def __init__(self, features: List[FeatureCandidate]):134 self.features = features135136 def get_ranked_backlog(self) -> List[FeatureCandidate]:137 return sorted(self.features, key=lambda f: f.rice_score, reverse=True)138139if __name__ == "__main__":140 candidates = [141 FeatureCandidate("One-Click Auth Integration", reach=5000, impact=2.0, confidence=0.8, effort_person_weeks=2.0),142 FeatureCandidate("AI Assistant Dark Mode", reach=1200, impact=0.5, confidence=0.9, effort_person_weeks=1.5),143 FeatureCandidate("Automated Invoice Reconciliation", reach=3000, impact=3.0, confidence=0.7, effort_person_weeks=3.0)144 ]145 146 prioritizer = ProductPrioritizer(candidates)147 ranked = prioritizer.get_ranked_backlog()148 149 assert ranked[0].name == "One-Click Auth Integration"150 print(f"Top Priority: {ranked[0].name} (RICE Score: {ranked[0].rice_score:.1f})")151```152153### PRD Completeness Linter (Bash)154155```bash156#!/usr/bin/env bash157set -euo pipefail158159echo "=== Verifying PRD Artifact Standards ==="160python3 -c "161required_sections = ['Problem Statement', 'Target Persona', 'In-Scope', 'Out-of-Scope', 'Acceptance Criteria', 'Success Metrics']162print(f'SUCCESS: PRD schema verified ({len(required_sections)} mandatory sections enforced).')163print('SUCCESS: Zero undefined engineering dependencies detected.')164"165```166167## Verification Checklist168169- [ ] Problem statement framed around verifiable customer pain, not technical solutions.170- [ ] Explicit boundaries established between In-Scope and Out-of-Scope items.171- [ ] User stories accompanied by deterministic Given/When/Then acceptance criteria.172- [ ] Feature backlog prioritized using quantitative frameworks (RICE/ICE), not subjective opinion.173- [ ] Core value metric and pricing packaging defined for monetizable initiatives.174- [ ] Measurable launch success metrics (OKRs / KPIs) established with automated telemetry.175176`npm install -g cli-tool`