Skip to main content
skill CX Codex

opportunity-framework — Claude Code skill: score and rank ideas

Turns a pile of possible improvements into a ranked roadmap using impact-effort and RICE. Handy when ideas outnumber capacity.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill opportunity-framework -a claude-code
Open on GitHub

What opportunity-framework does

This skill takes candidate improvements and sorts them into a priority order. Sources it works from include research findings, analytics, competitive gaps, technology, stakeholder requests and support channels.

Four frameworks sit inside. The impact-effort matrix splits items into quick wins, strategic bets, fill-ins and deprioritize. RICE scores Reach, Impact, Confidence and Effort. The Kano model classifies features as must-be, one-dimensional, attractive, indifferent or reverse. Value vs complexity rates user value and complexity from 1 to 10. Output is a ranked list with rationale, theme groupings, dependencies and confidence levels.

The skill advises triangulating with more than one framework and writing down the reason behind each call. Once you have picked something, design-brief handles the framing.

What it helps with

  • sort ideas into impact-effort quadrants
  • run RICE scoring across a feature list
  • group opportunities by theme and dependency
  • drop ideas that cost more than they return
  • record why each priority was chosen

Example prompts for the agent

  • run these ideas through opportunity-framework and rank them by impact and effort
  • score the features with RICE and tell me what to build first
  • compare user value against complexity for these tasks

How to install opportunity-framework

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill opportunity-framework -a claude-code

2Manually: put the files in place

~/.claude/skills/opportunity-framework/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/opportunity-framework/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about opportunity-framework

How do I install opportunity-framework in Claude?

Run npx skills add Owl-Listener/designer-skills --skill opportunity-framework -a claude-code. The skill lands in ~/.claude/skills/opportunity-framework/SKILL.md.

What does opportunity-framework do?

It prioritises a list of ideas by scoring impact and effort, applying RICE, the Kano model and value vs complexity. You get a ranked list with rationale.

How is opportunity-framework different from design-brief?

Use the first to decide what to work on. Use the second to frame the idea you picked.

Source text

SKILL.md · MIT
---
name: opportunity-framework
description: Identify, score, and prioritise design opportunities against impact and effort. Use when there are more ideas than capacity. For framing the one you choose, use `design-brief`.
---
# 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

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

From the same set109

click-test-plan Turns a findability question into a test plan: where users click first and whether they locate items in your navigation. Useful when a design is ready but untested. CX Codex +1 2,000installs design-sprint-plan Plans structured design sprints to move from a challenge statement to a tested prototype in days. Ideal when you need to compress discovery work into a single week. CX Codex +1 2,000installs design-system-adoption Builds an adoption strategy and enablement materials when teams are bypassing an existing design system. It helps plan education, migration support and measurement. CX Codex +1 2,000installs team-workflow Designs an operating cadence for design teams, covering task tracking, regular rituals, and developer handoff. Helpful when day-to-day design collaboration lacks structure. CX Codex +1 2,000installs design-review-process A skill that sets four review gates for design work, from concept to implementation QA. Useful when things ship without a consistent review step. CX Codex +1 2,000installs north-star-vision Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction. CX Codex +1 2,000installs test-scenario Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,000installs stakeholder-alignment Builds alignment artifacts: a stakeholder map, RACI matrix, decision rights and a communication plan. Useful when unclear ownership stalls decisions. CX Codex +1 2,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor