Analyze Feature Requests
- 1.9k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
analyze-feature-requests triages customer feature asks into themed, prioritized recommendations with test plans.
About
The analyze-feature-requests skill groups customer asks into themes, scores strategic alignment, and prioritizes top three features by impact, effort, risk, and vision fit. It rejects letting customers design solutions, prioritizing opportunities over feature lists, and uses Dan Olsen Opportunity Score concepts via related prioritization frameworks. For each top feature agents provide rationale, alternative solutions, risky assumptions, and cheap tests. Inputs may include spreadsheets or CSV exports read directly. Output is markdown or structured tables saved for stakeholder review. Use when triaging backlog requests, reviewing customer feedback lists, or making prioritization decisions against stated product goals.
- Themes and prioritizes feature requests against product goals.
- Uses impact, effort, risk, and strategic alignment scoring.
- Prioritizes opportunities over customer-designed solutions.
- Delivers rationale, alternatives, assumptions, and test ideas per top pick.
- Reads CSV or spreadsheet request exports when provided.
Analyze Feature Requests by the numbers
- 1,927 all-time installs (skills.sh)
- +77 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #256 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
analyze-feature-requests capabilities & compatibility
- Capabilities
- request theming · impact effort risk scoring · assumption test planning
- Use cases
- planning · project management
npx skills add https://github.com/phuryn/pm-skills --skill analyze-feature-requestsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.9k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
Which customer feature requests should we prioritize against our goals?
Categorize and prioritize customer feature requests by theme, strategic alignment, impact, effort, and risk using opportunity thinking.
Who is it for?
PMs reviewing inbound feature lists or support-driven requests.
Skip if: Greenfield product discovery without an existing request set.
When should I use this skill?
User reviews customer feature requests or backlog prioritization.
What you get
Themed analysis with top three features, rationale, risks, and validation experiments.
- Prioritized request table
- Theme-grouped roadmap summary
Files
Analyze Feature Requests
Categorize, evaluate, and prioritize customer feature requests against product goals.
Context
You are analyzing feature requests for $ARGUMENTS.
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.
Domain Context
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.
Instructions
The user will describe their product goal and provide feature requests. Work through these steps:
1. Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
2. Categorize requests into themes: Group related requests together and name each theme.
3. Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
4. Prioritize the top 3 features based on:
- Impact: Customer value and number of users affected
- Effort: Development and design resources required
- Risk: Technical and market uncertainty
- Strategic alignment: Fit with product vision and goals
5. For each top feature, provide:
- Rationale (customer needs, strategic alignment)
- Alternative solutions worth considering
- High-risk assumptions
- How to test those assumptions with minimal effort
Think step by step. Save as markdown or create a structured output document.
---
Further Reading
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Pick analyze-feature-requests over generic brainstorming skills when input is a concrete list of customer asks needing scored prioritization.
FAQ
Should we build what customers request literally?
No. Prioritize underlying opportunities and problems, not prescribed solutions.
What dimensions rank top features?
Impact, effort, risk, and strategic alignment with stated goals.
What does each top feature include?
Rationale, alternatives, high-risk assumptions, and minimal-effort tests.
Is Analyze Feature Requests safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.