prioritize-features

Name: prioritize-features
Author: phuryn

1.8kinstalls2.5kforks

How to install prioritize-features?

phuryn/pm-skills/prioritize-features

$npx -y skills add phuryn/pm-skills --skill prioritize-features

Installs into the current project.

Summary

Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.

Files · 1

View on GitHub

SKILL.md

1	## Prioritize Feature Backlog
2
3	Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
4
5	### Context
6
7	You are helping prioritize features for $ARGUMENTS.
8
9	If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
10
11	### Domain Context
12
13	For framework selection guidance, see the `prioritization-frameworks` skill. Key recommendations:
14
15	Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.
16
17	ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.
18
19	### Instructions
20
21	The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:
22
23	1. Understand priorities: Confirm the product objective and success metrics.
24
25	2. Evaluate each feature against:
26	- Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.
27	- Effort: How much development, design, and coordination is required?
28	- Risk: How much uncertainty exists? What assumptions need testing?
29	- Strategic alignment: How well does it fit the product vision and current goals?
30
31	3. Recommend the top 5 features with:
32	- Clear ranking (1-5)
33	- Brief rationale for each selection
34	- Key trade-offs considered
35	- What was deprioritized and why
36
37	4. Present as a prioritization table if helpful.
38
39	Think step by step. Save as markdown if the output is substantial.
40
41	---
42
43	### Further Reading
44
45	- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
46	- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
47	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

People who liked this also viewed

6 picks

Type

prioritize-features

1.8kinstalls2.5kforks

View on GitHub

How to install prioritize-features?

phuryn/pm-skills/prioritize-features

$npx -y skills add phuryn/pm-skills --skill prioritize-features

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Prioritize Feature Backlog
2
3	Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
4
5	### Context
6
7	You are helping prioritize features for $ARGUMENTS.
8
9	If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
10
11	### Domain Context
12
13	For framework selection guidance, see the `prioritization-frameworks` skill. Key recommendations:
14
15	Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.
16
17	ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.
18
19	### Instructions
20
21	The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:
22
23	1. Understand priorities: Confirm the product objective and success metrics.
24
25	2. Evaluate each feature against:
26	- Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.
27	- Effort: How much development, design, and coordination is required?
28	- Risk: How much uncertainty exists? What assumptions need testing?
29	- Strategic alignment: How well does it fit the product vision and current goals?
30
31	3. Recommend the top 5 features with:
32	- Clear ranking (1-5)
33	- Brief rationale for each selection
34	- Key trade-offs considered
35	- What was deprioritized and why
36
37	4. Present as a prioritization table if helpful.
38
39	Think step by step. Save as markdown if the output is substantial.
40
41	---
42
43	### Further Reading
44
45	- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
46	- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
47	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

People who liked this also viewed

6 picks

Type