analyze-feature-requests

Name: analyze-feature-requests
Author: phuryn

1.8kinstalls2.5kforks

How to install analyze-feature-requests?

phuryn/pm-skills/analyze-feature-requests

$npx -y skills add phuryn/pm-skills --skill analyze-feature-requests

Installs into the current project.

Summary

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.

Files · 1

View on GitHub

SKILL.md

1	## Analyze Feature Requests
2
3	Categorize, evaluate, and prioritize customer feature requests against product goals.
4
5	### Context
6
7	You are analyzing feature requests for $ARGUMENTS.
8
9	If the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.
10
11	### Domain Context
12
13	Never allow customers to design solutions. Prioritize opportunities (problems), not features. Use Opportunity Score (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the `prioritization-frameworks` skill for full details and templates.
14
15	### Instructions
16
17	The user will describe their product goal and provide feature requests. Work through these steps:
18
19	1. Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
20
21	2. Categorize requests into themes: Group related requests together and name each theme.
22
23	3. Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
24
25	4. Prioritize the top 3 features based on:
26	- Impact: Customer value and number of users affected
27	- Effort: Development and design resources required
28	- Risk: Technical and market uncertainty
29	- Strategic alignment: Fit with product vision and goals
30
31	5. For each top feature, provide:
32	- Rationale (customer needs, strategic alignment)
33	- Alternative solutions worth considering
34	- High-risk assumptions
35	- How to test those assumptions with minimal effort
36
37	Think step by step. Save as markdown or create a structured output document.
38
39	---
40
41	### Further Reading
42
43	- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
44	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

People who liked this also viewed

6 picks

Type

analyze-feature-requests

1.8kinstalls2.5kforks

View on GitHub

How to install analyze-feature-requests?

phuryn/pm-skills/analyze-feature-requests

$npx -y skills add phuryn/pm-skills --skill analyze-feature-requests

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Analyze Feature Requests
2
3	Categorize, evaluate, and prioritize customer feature requests against product goals.
4
5	### Context
6
7	You are analyzing feature requests for $ARGUMENTS.
8
9	If the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.
10
11	### Domain Context
12
13	Never allow customers to design solutions. Prioritize opportunities (problems), not features. Use Opportunity Score (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the `prioritization-frameworks` skill for full details and templates.
14
15	### Instructions
16
17	The user will describe their product goal and provide feature requests. Work through these steps:
18
19	1. Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
20
21	2. Categorize requests into themes: Group related requests together and name each theme.
22
23	3. Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
24
25	4. Prioritize the top 3 features based on:
26	- Impact: Customer value and number of users affected
27	- Effort: Development and design resources required
28	- Risk: Technical and market uncertainty
29	- Strategic alignment: Fit with product vision and goals
30
31	5. For each top feature, provide:
32	- Rationale (customer needs, strategic alignment)
33	- Alternative solutions worth considering
34	- High-risk assumptions
35	- How to test those assumptions with minimal effort
36
37	Think step by step. Save as markdown or create a structured output document.
38
39	---
40
41	### Further Reading
42
43	- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
44	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

People who liked this also viewed

6 picks

Type