omeragaakbas/prioritize-features
.claude/skills/prioritize-features/SKILL.md
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.
testing
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add omeragaakbas/zoyare prioritize-featuresInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 3:33 PM20.5s1 file scanned
SKILL.md
- name:
- prioritize-features
- description:
- 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.
Prioritize Feature Backlog
Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
Context
You are helping prioritize features for $ARGUMENTS.
If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
Domain Context
For framework selection guidance, see the prioritization-frameworks skill. Key recommendations:
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.
ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.
Instructions
The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:
-
Understand priorities: Confirm the product objective and success metrics.
-
Evaluate each feature against:
- Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.
- Effort: How much development, design, and coordination is required?
- Risk: How much uncertainty exists? What assumptions need testing?
- Strategic alignment: How well does it fit the product vision and current goals?
-
Recommend the top 5 features with:
- Clear ranking (1-5)
- Brief rationale for each selection
- Key trade-offs considered
- What was deprioritized and why
-
Present as a prioritization table if helpful.
Think step by step. Save as markdown if the output is substantial.
Further Reading
- Kano Model: How to Delight Your Customers Without Becoming a Feature Factory
- The Product Management Frameworks Compendium + Templates
- Continuous Product Discovery Masterclass (CPDM) (video course)
Related Skills
omeragaakbas/product-sense-interview-answer
development
VerifiedTrustedCommunity
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/product-name
data-ai
VerifiedTrustedCommunity
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/product-marketing-context
development
VerifiedTrustedCommunity
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/problem-statement
documentation
VerifiedTrustedCommunity
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.
SKILL.mdUpdated Apr 17, 2026