SkillAgentSearch skills...

nw-jtbd-opportunity-scoring

JTBD opportunity scoring and prioritization - outcome statement format, opportunity algorithm, scoring interpretation, feature prioritization, and opportunity matrix template

Install / Use

npx skills add nWave-ai/nWave --skill nw-jtbd-opportunity-scoring

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Tags

Our assessment of nw-jtbd-opportunity-scoring

nw-jtbd-opportunity-scoring scores 89/100 on our quality scale, 1727th of 4,702 Development & Engineering skills we index (top 37%).

Its SKILL.md is 7.5 KB long, well organised into 24 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

It has 617 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so nw-jtbd-opportunity-scoring is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nw-jtbd-opportunity-scoring compared with similar skills

All 4 of these similar skills score higher than nw-jtbd-opportunity-scoring; compare them before choosing.

SkillScoreStarsUpdatedFormat
nw-jtbd-opportunity-scoring (this skill)by nWave-ai896172mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install nw-jtbd-opportunity-scoring?
Run npx skills add nWave-ai/nWave --skill nw-jtbd-opportunity-scoring. The install tabs above show the steps for each supported agent.
Which AI agents does nw-jtbd-opportunity-scoring work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is nw-jtbd-opportunity-scoring safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nw-jtbd-opportunity-scoring still maintained?
The repository was last updated about 2 months ago, so nw-jtbd-opportunity-scoring is actively maintained.

name: nw-jtbd-opportunity-scoring description: JTBD opportunity scoring and prioritization - outcome statement format, opportunity algorithm, scoring interpretation, feature prioritization, and opportunity matrix template user-invocable: false disable-model-invocation: true

JTBD Opportunity Scoring

Use when prioritizing features, stories, or backlog items based on customer-defined outcomes. Opportunity scoring (Ulwick's ODI) replaces gut-feel prioritization with evidence-based ranking.

Outcome Statements

Every customer need expressed as a desired outcome following strict format:

[Direction] + the [metric] + [object of control] + [contextual clarifier]
  • Direction: "Minimize" or "Maximize"
  • Metric: time, likelihood, number, or frequency

Examples

  • "Minimize the time it takes to identify the root cause of a production issue"
  • "Minimize the likelihood of deploying untested code to production"
  • "Maximize the likelihood that acceptance criteria cover all relevant scenarios"
  • "Minimize the number of iterations needed to reach shared understanding"
  • "Minimize the frequency of false positive alerts during monitoring"

Quality Checks

Outcome statement must be: Solution-free (no specific technology) | Measurable (ratable on importance/satisfaction 1-5) | Controllable (customer can assess improvement) | Unambiguous (same interpretation by all stakeholders)

Deriving Outcome Statements

Walk the 8-step job map (see jtbd-core skill) and generate 2-3 per step. Produces 16-24 outcome statements per job -- comprehensive view of customer needs.

| Job Map Step | Outcome Statement Pattern | |-------------|--------------------------| | Define | "Minimize the time to determine [what is needed]" | | Locate | "Minimize the likelihood of missing [required input]" | | Prepare | "Minimize the time to set up [environment/context]" | | Confirm | "Minimize the likelihood of proceeding with [invalid state]" | | Execute | "Minimize the time to complete [core action]" | | Monitor | "Minimize the likelihood of [undetected failure]" | | Modify | "Minimize the time to recover from [exception]" | | Conclude | "Minimize the likelihood of [incomplete cleanup]" |

The Opportunity Algorithm

Opportunity Score = Importance + max(0, Importance - Satisfaction)

Where:

  • Importance = % of respondents rating outcome 4 or 5 on 1-5 scale
  • Satisfaction = % of respondents rating current satisfaction 4 or 5 on 1-5 scale
  • Score range: 0-20 (higher = greater opportunity)

How It Works

Rewards outcomes both important and unsatisfied. If satisfaction >= importance, second term is zero (appropriately served). If satisfaction < importance, gap amplifies score (underserved).

Score Interpretation

| Score Range | Category | Action | |-------------|----------|--------| | 15-20 | Extremely underserved | High-priority; invest heavily | | 12-15 | Underserved | Strong opportunity; plan for next iteration | | 10-12 | Appropriately served | Maintain; incremental improvement | | < 10 | Overserved | Simplification candidate; may be over-engineered |

Applying to Feature Prioritization

Step 1: Generate Outcome Statements

From job mapping and interview findings, compile 15-30 per major job.

Step 2: Rate Importance and Satisfaction

Gather ratings from users/stakeholders. For small teams:

  • Interview 5-10 users directly
  • Use internal team ratings as proxy (mark as "team estimate" vs "user data")
  • Leverage support tickets, feature requests, bug reports as signals

Step 3: Calculate and Rank

Compute scores, sort descending. Top scores = highest-priority features.

Step 4: Map to Stories

Each high-scoring outcome maps to one or more stories. Score 15+ should produce at least one story in current iteration.

Step 5: Identify Overserved Areas

Scores below 10 are simplification candidates. Resources on overserved outcomes are better redirected to underserved ones.

Opportunity Scoring Matrix Template

## Opportunity Scoring: [Product/Feature Area]

| # | Outcome Statement | Imp. (%) | Sat. (%) | Score | Priority |
|---|-------------------|----------|----------|-------|----------|
| 1 | Minimize the time to [outcome A] | | | | |
| 2 | Minimize the likelihood of [outcome B] | | | | |
| 3 | Maximize the [quality] when [context C] | | | | |

### Scoring Method
- Importance: % of respondents rating 4+ on 5-point scale
- Satisfaction: % of respondents rating 4+ on 5-point scale
- Score: Importance + max(0, Importance - Satisfaction)
- Priority: Extremely Underserved (15+), Underserved (12-15),
  Appropriately Served (10-12), Overserved (<10)

### Top Opportunities (Score >= 12)
1. [Outcome] -- Score: [X] -- Story: [link or title]
2. [Outcome] -- Score: [X] -- Story: [link or title]

### Overserved Areas (Score < 10)
1. [Outcome] -- Score: [X] -- Simplification opportunity: [description]

### Data Quality Notes
- Source: [user interviews / team estimates / support ticket analysis]
- Sample size: [N respondents]
- Confidence: [High if N >= 10 with user data, Medium if team estimates]

Worked Example

Context: CLI tool for deploying applications. 8 users surveyed.

| # | Outcome Statement | Imp. | Sat. | Score | Priority | |---|-------------------|------|------|-------|----------| | 1 | Minimize time to identify root cause of failed deployment | 92% | 35% | 14.9 | Extremely Underserved | | 2 | Minimize likelihood of deploying untested code | 88% | 72% | 10.4 | Appropriately Served | | 3 | Minimize time to roll back a bad deployment | 85% | 30% | 14.0 | Underserved | | 4 | Minimize time to onboard a new team member to deploy | 65% | 40% | 9.0 | Overserved | | 5 | Minimize likelihood of misconfiguring environment variables | 80% | 45% | 11.5 | Appropriately Served |

Prioritization result:

  1. Root cause identification (14.9) -- build better deployment diagnostics
  2. Rollback speed (14.0) -- invest in one-command rollback
  3. Environment misconfiguration (11.5) -- incremental improvements to validation
  4. Untested code prevention (10.4) -- maintain current pre-deploy checks
  5. Onboarding time (9.0) -- consider simplifying; current docs may be over-engineered

Small-Team Adaptations

Ulwick's methodology assumes large-scale surveys (100+ respondents). For small agile teams:

  • 5-10 interviews sufficient for directional signals. Treat scores as relative rankings, not absolute.
  • Support tickets as proxy data: High-frequency complaints = high importance + low satisfaction.
  • Team consensus estimation: When user access limited, rate collectively. Document as "team estimate."
  • Iterate: Re-score after each release as satisfaction shifts.

Integration with Other Prioritization Methods

| Method | Best For | Combine With Opportunity Scoring | |--------|----------|--------------------------------| | MoSCoW | Sprint-level scope decisions | Use opportunity scores to inform Must/Should/Could | | Value/Effort matrix | Quick relative ranking | Use opportunity scores as "value" axis | | RICE | Feature-level prioritization | Use opportunity score as "Impact" component | | Story mapping | Release planning | Use opportunity scores to prioritize rows (MVP vs later) |

Cross-References

  • For core JTBD theory and job map steps: load jtbd-core skill
  • For interview techniques to gather importance/satisfaction data: load jtbd-interviews skill
  • For translating high-priority outcomes to BDD scenarios: load jtbd-bdd-integration skill
  • For story-level prioritization (MoSCoW, Value/Effort): load leanux-methodology skill

Related Skills

View on GitHub
GitHub Stars617
CategoryDevelopment
Updated2mo ago
Forks63

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions