# PM Frameworks Included in the pm-product-discovery Plugin Skills > Explore six PM frameworks like ICE, RICE, and HEART integrated into the pm-product-discovery plugin for efficient prioritization and metrics tracking. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: deep-dive - Published: 2026-06-27 --- **The pm-product-discovery plugin bundles six battle-tested product management frameworks—ICE, RICE, Opportunity Solution Tree, North Star, and Google HEART—directly into its skill files for immediate prioritization, discovery, and metrics tracking.** The **phuryn/pm-skills** repository hosts a curated collection of automation tools for product teams. Within the **pm-product-discovery** plugin, these frameworks are embedded as executable skills that transform abstract methodologies into concrete workflows. Understanding which PM frameworks are included in the pm-product-discovery plugin skills enables teams to rapidly apply industry-standard approaches to feature prioritization, opportunity discovery, and success metric definition. ## Prioritization Frameworks: ICE and RICE The plugin implements two quantitative scoring models in [`pm-product-discovery/skills/prioritize-features/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/prioritize-features/SKILL.md) and [`pm-product-discovery/skills/prioritize-assumptions/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/prioritize-assumptions/SKILL.md), alongside a meta-skill aggregation layer. ### ICE Scoring (Impact × Confidence × Ease) **ICE** ranks items by multiplying three factors: Impact, Confidence, and Ease. This lightweight framework appears in both feature and assumption prioritization skills, allowing product teams to surface high-impact items quickly without complex data requirements. ### RICE Scoring (Reach × Impact × Confidence ÷ Effort) **RICE** extends ICE by adding a **Reach** factor and replacing Ease with **Effort** as a divisor. According to the source files, this formula suits larger teams or scenarios requiring granular scoring: `(Reach × Impact × Confidence) / Effort`. The skill files automatically calculate and rank outputs based on user inputs for each variable. ### Prioritization-Frameworks Meta-Skill Both prioritization skills reference a **Prioritization-Frameworks** meta-skill that aggregates templates and scoring formulas, providing a unified interface for selecting between ICE, RICE, and additional approaches. ## Discovery Frameworks: Opportunity Solution Tree ### Opportunity Solution Tree (OST) Defined in [`pm-product-discovery/skills/opportunity-solution-tree/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/opportunity-solution-tree/SKILL.md), the **Opportunity Solution Tree** provides a visual mapping structure: **Outcome → Customer Opportunities → Possible Solutions → Experiments**. This framework guides continuous discovery by ensuring every solution links back to a desired outcome and validated customer opportunity. ## Metrics Frameworks: North Star and HEART The [`pm-product-discovery/skills/metrics-dashboard/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/metrics-dashboard/SKILL.md) file introduces two complementary measurement systems under the section "Identify the metrics framework." ### North Star Framework The **North Star Framework** helps teams define a single, high-level metric that reflects product-level value and drives organizational alignment. The skill prompts users to identify this anchor metric before layering secondary indicators. ### Google HEART Framework **HEART** (Happiness, Engagement, Adoption, Retention, Task Success) offers a user-centric measurement system for product analytics. The metrics-dashboard skill allows teams to select specific HEART dimensions to monitor alongside their North Star metric. ## How to Invoke PM Frameworks via Plugin Commands The plugin exposes these frameworks through slash commands documented in the `commands/` folder. ### Prioritization Commands Use `/triage-requests` to activate the ICE or RICE scoring engines: ```markdown /triage-requests ``` This command prompts for feature lists, then applies the **RICE** formula `(Reach × Impact × Confidence) / Effort` to output a ranked table. ### Discovery Commands Run the Opportunity Solution Tree workflow with: ```markdown /discover ``` This executes the OST framework, walking users through mapping outcomes to opportunities, solutions, and experiments. ### Metrics Commands Initialize the North Star or HEART frameworks using: ```markdown /setup-metrics ``` This guides framework selection—typically starting with **North Star** definition, then optionally adding **HEART** dimensions for comprehensive analytics. ## Summary - The **pm-product-discovery** plugin embeds **ICE**, **RICE**, **Opportunity Solution Tree**, **North Star**, and **Google HEART** frameworks as executable skills. - Prioritization logic resides in [`prioritize-features/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/prioritize-features/SKILL.md) and [`prioritize-assumptions/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/prioritize-assumptions/SKILL.md), offering both ICE and RICE formulas via a meta-skill aggregation. - Discovery workflows use the OST framework defined in [`opportunity-solution-tree/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/opportunity-solution-tree/SKILL.md). - Metrics configuration combines North Star and HEART approaches in [`metrics-dashboard/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/metrics-dashboard/SKILL.md). - Users trigger these frameworks via `/triage-requests`, `/discover`, and `/setup-metrics` commands. ## Frequently Asked Questions ### What is the difference between ICE and RICE in the pm-product-discovery plugin? **ICE** multiplies Impact, Confidence, and Ease to generate quick priority scores, while **RICE** adds a Reach factor and divides by Effort to account for the number of users affected and implementation cost. Both formulas are implemented in the prioritization skills and selectable based on data availability. ### How does the Opportunity Solution Tree skill structure product discovery? The skill implements the **OST** framework by enforcing a hierarchy: business outcomes feed customer opportunities, which generate solution ideas, which then require specific experiments to validate. This structure is defined in [`pm-product-discovery/skills/opportunity-solution-tree/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/opportunity-solution-tree/SKILL.md) and launched via the `/discover` command. ### Can I use both North Star and HEART frameworks simultaneously? Yes. According to [`metrics-dashboard/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/metrics-dashboard/SKILL.md), the **North Star** metric serves as the primary alignment tool, while **HEART** dimensions (Happiness, Engagement, Adoption, Retention, Task Success) provide user-centric analytics layers. The `/setup-metrics` command supports configuring both frameworks in tandem. ### Where are the framework formulas defined in the source code? The mathematical formulas for ICE and RICE appear in [`pm-product-discovery/skills/prioritize-features/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/prioritize-features/SKILL.md) and [`pm-product-discovery/skills/prioritize-assumptions/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/prioritize-assumptions/SKILL.md), while the North Star and HEART methodologies are documented in [`pm-product-discovery/skills/metrics-dashboard/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/metrics-dashboard/SKILL.md). The OST visual framework is specified in [`pm-product-discovery/skills/opportunity-solution-tree/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/opportunity-solution-tree/SKILL.md).