Opportunity Framework
Rank design and product improvements with impact-effort, RICE, Kano, and value-vs-complexity so you pick a roadmap instead of random feature work.
Overview
Opportunity Framework is a journey-wide agent skill that evaluates and prioritizes design opportunities with impact-effort, RICE, Kano, and value-complexity frameworks—usable whenever a solo builder needs to choose roadm
Install
npx skills add https://github.com/owl-listener/designer-skills --skill opportunity-frameworkWhat is this skill?
- Triangulates prioritization with impact-effort 2x2, RICE, Kano, and value-vs-complexity scoring
- Ingests opportunity sources: research, analytics, competitive gaps, tech, stakeholders, support
- Produces ranked list with rationale, theme groupings, dependencies, and confidence levels
- Documents the why behind each deprioritization or quick-win call
- Encourages multiple frameworks and diverse perspectives before locking the roadmap
- 4 evaluation frameworks: impact-effort matrix, RICE, Kano model, value vs complexity
Adoption & trust: 560 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have too many improvement ideas from research, support, and stakeholders but no shared way to rank impact, effort, and confidence.
Who is it for?
Indie SaaS founders and agent-assisted PMs balancing research findings, analytics, and support noise into one prioritization narrative.
Skip if: A single tiny bugfix with obvious urgency, or teams that already have a frozen quarterly roadmap with no reprioritization window.
When should I use this skill?
When you need to identify, evaluate, and prioritize design or product opportunities from multiple sources into a ranked roadmap.
What do I get? / Deliverables
You get a ranked opportunity list with themes, dependencies, documented rationale, and confidence levels ready for sprint or spec work.
- Ranked opportunity list with rationale
- Theme groupings and dependency notes
- Confidence levels and deprioritization record
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
MVP scope ballooned; you RICE-score ten ideas to keep only three for the first release.
Sprint planning needs quick wins vs strategic bets on a 2x2 before the agent writes tasks.
Funnel drop-off and support themes become scored opportunities for the next growth iteration.
Early competitive gaps are grouped and ranked before you validate with a landing page.
Recurring support pain points get value-vs-complexity scores for a maintenance roadmap.
How it compares
Strategic prioritization frameworks in one skill—not a backlog ticket generator or a UX research synthesis-only pass.
Common Questions / FAQ
Who is opportunity-framework for?
Solo builders, designer-founders, and small teams who own roadmap decisions without a dedicated product org.
When should I use opportunity-framework?
At validate when scoping MVP; at build when choosing the next feature slice; at grow when analytics surface retention gaps; at operate when support themes reveal systemic fixes; whenever opportunity sources need ranking.
Is opportunity-framework safe to install?
It is planning methodology with no required shell or network access; review the Security Audits panel on this page before adding any skill to your agent environment.
SKILL.md
READMESKILL.md - Opportunity Framework
# Opportunity Framework You are an expert in identifying, evaluating, and prioritizing design opportunities. ## What You Do You help teams move from possible improvements to a prioritized roadmap. ## Opportunity Sources Research findings, analytics, competitive gaps, technology, stakeholder requests, support channels. ## Evaluation Frameworks ### Impact-Effort Matrix 2x2 grid: quick wins, strategic bets, fill-ins, deprioritize. ### RICE Scoring Reach, Impact (1-3), Confidence (%), Effort (person-weeks). ### Kano Model Must-be, one-dimensional, attractive, indifferent, reverse. ### Value vs Complexity Score user value (1-10) and complexity (1-10). ## Output Ranked list with rationale, theme groupings, dependencies, confidence levels. ## Best Practices - Use multiple frameworks to triangulate - Include diverse perspectives - Revisit as you learn - Document the 'why' behind every decision