JTBD opportunity scoring and prioritization - outcome statement format, opportunity algorithm, scoring interpretation, feature prioritization, and opportunity matrix template
SkillScore88Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Product Management pack
Last verified 8/16/2026
What it changes
Passed 22 of 25 test cases with the skill, and 13 of 25 without it.
Without skill52%
With skill88%
Checks it passed that the model alone missed
Assigns a High confidence rating.
Assigns a Medium confidence rating.
Classifies a score of 12.0 as Underserved.
and 9 more in the full report
9 fixed13 passed either way3 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+91%
Agent turns
0%
Response time
-24%
Model gemini-3.6-flashMeasured 8/16/2026v122 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
An outcome statement regarding secret rotation speed receives an opportunity score of exactly 12.0. Which priority tier applies to this score?
What was checked, without and with the skill
Checked
Without skill
With skill
Classifies a score of 12.0 as Underserved.
Missed
Passed
case-23 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md160 linessingle file
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]"