plugins/nw/skills/nw-opportunity-mapping/SKILL.md
Opportunity Solution Trees, opportunity scoring, Lean Canvas, JTBD job mapping, and technique selection guide
npx skillsauth add nwave-ai/nwave nw-opportunity-mappingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Connects desired outcomes to opportunities to solution ideas:
Desired Outcome
|
+-- Opportunity 1 (score)
| +-- Solution Idea A
| +-- Solution Idea B
|
+-- Opportunity 2 (score)
| +-- Solution Idea C
|
+-- Opportunity 3 (score)
+-- Solution Idea D
+-- Solution Idea E
Formula: Score = Importance + Max(0, Importance - Satisfaction) Importance: 1-10 | Satisfaction: 1-10 | Max score: 20
| Score | Meaning | Action | |-------|---------|--------| | >8 | High importance, satisfaction gap -- underserved | Pursue | | 5-8 | Moderate importance or partially served | Evaluate | | <5 | Low importance or well-served | Deprioritize |
Process: gather importance + satisfaction from 5+ interviews, calculate per opportunity, rank, select top 2-3.
| Step | Goal | Outcome Format | |------|------|---------------| | Define | Determine what needs doing | Minimize time to identify [object] | | Locate | Find inputs/information | Minimize time to gather [resources] | | Prepare | Ready inputs for use | Minimize likelihood of missing [requirements] | | Confirm | Verify readiness | Minimize likelihood of incorrect [categorization] | | Execute | Perform core task | Minimize time from [start] to [completion] | | Monitor | Track progress | Minimize uncertainty about [status] | | Modify | Adjust if needed | Minimize effort to correct [issues] | | Conclude | Complete the job | Minimize time from [completion] to [result] |
Outcome statement format: [Direction] + [Metric] + [Object] + [Clarifier] Example: "Minimize the time it takes to identify which project budget a new expense should be allocated to"
One-page business model for Phase 4 viability validation.
| Risk | Question | Validation | |------|----------|-----------| | Value | Will customers want this? | Interviews, fake doors | | Usability | Can customers use this? | Prototype testing, task completion | | Feasibility | Can we build this? | Spikes, expert review | | Viability | Business model works? | Lean Canvas, stakeholder review |
| Goal | Techniques | |------|-----------| | Validate problem | Mom Test, Job Mapping | | Understand needs | Outcome Statements, Opportunity Mapping | | Prioritize opportunities | OST, Opportunity Algorithm | | Generate solutions | Ideation with OST constraints | | Validate solution value | Hypothesis Testing, Prototypes | | Test usability | Prototype testing, Task completion | | Assess feasibility | 4 Risks, Spikes | | Structure business model | Lean Canvas | | Continuous learning | Weekly customer touchpoints |
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
development
Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
development
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.