discover-opportunities

Analyze outcomes and JTBD to generate scored opportunity statements with validation tests.

450|36|Updated Jan 3, 2026

Search Tags:#validation #ranking #product-strategy #jtbd #opportunity-discovery #frame-job

Ready to run

npx skills add https://github.com/kasperjunge/agent-resources --skill discover-opportunities

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discover-opportunities
Source: https://github.com/kasperjunge/agent-resources/tree/main/.opencode/skill/discover-opportunities
Command: npx skills add https://github.com/kasperjunge/agent-resources --skill discover-opportunities

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify real opportunities by reasoning from first principles and Jobs-To-Be-Done (JTBD). Focus on the user's job, context, and constraints before any solution ideas.

Core Features & Use Cases

Frame the jobs: define the core job as verb + outcome (not a solution) and map functional, emotional, and social jobs.
First-principles check: identify root frictions and separate real vs assumed constraints.
Generate opportunities: produce 5-10 opportunity statements using the template and capture frequency, severity, and workaround.
Score and rank: score 0-3 on impact, urgency, underservedness, feasibility, and willingness to pay; rank top 3-5.
Output and validation: present top opportunities with rationale; list assumptions and suggested validation tests.

Quick Start

Run the Opportunity Discovery workflow to frame the job, generate 5-10 opportunities, and prepare a ranked list with assumptions and validation tests.

Frequently Asked Questions about discover-opportunities

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify hidden market opportunities using Jobs-To-Be-Done insights?▼

Identify hidden market opportunities by defining core jobs as verbs plus outcomes, mapping functional and emotional constraints, and generating ranked opportunity statements. This process separates real frictions from assumed constraints to focus purely on user needs before solutioning.

What is the best way to score and prioritize product opportunities?▼

The best way to prioritize product opportunities is scoring them 0-3 across impact, urgency, underservedness, feasibility, and willingness to pay. This generates a ranked list of your top 3-5 opportunities, complete with rationale and outlined validation tests.

How do I generate opportunity statements from JTBD user research?▼

Generate opportunity statements from JTBD research by framing the core job, checking root frictions from first principles, and applying a standard template. This produces 5-10 structured statements capturing the frequency, severity, and existing workarounds for each opportunity.

Can I use JTBD opportunity discovery to validate product strategy assumptions?▼

Yes, you can validate product strategy assumptions using opportunity discovery by documenting them alongside your ranked opportunities. The process outlines fast validation tests in a structured format, ensuring your top opportunity statements are tested before committing to development.

When do I need to apply first-principles thinking during opportunity discovery?▼

You need to apply first-principles thinking during opportunity discovery right after framing the core job and before generating opportunity statements. This step identifies root frictions and separates real user constraints from assumed limitations to ensure accurate scoring.

Why should I separate assumed constraints from real frictions in product strategy?▼

You should separate assumed constraints from real frictions to ensure your opportunity discovery focuses on actual user limitations rather than perceived technical barriers. This first-principles check prevents teams from pursuing false opportunities and improves the accuracy of impact and feasibility scoring.