Nw Opportunity MappingSAFE
AI agents that guide you from idea to working code, with you in control at every step.
Overview
AI agents that guide you from idea to working code, with you in control at every step.
1a864ec81cdeOBSERVED · 2026-10-14What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: nw-opportunity-mapping
description: Opportunity Solution Trees, opportunity scoring, Lean Canvas, JTBD job mapping, and technique selection guide
user-invocable: false
disable-model-invocation: true
---
# Opportunity Mapping
## Opportunity Solution Tree (OST)
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
```
### Building the OST
1. Define desired outcome from customer research
2. Map opportunities from interview insights (min 5 distinct)
3. Score each using Opportunity Algorithm
4. Generate solution ideas for top 2-3
5. Seek real diversity in solutions (avoid variations of same idea)
## Opportunity Scoring Algorithm
**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.
## Job Mapping (JTBD)
### Universal Job Map Steps
| 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"
## Lean Canvas
One-page business model for Phase 4 viability validation.
1. **Problem**: Top 3 problems (Phase 1 validated) | 2. **Customer Segments**: by JTBD
3. **UVP**: single clear message | 4. **Solution**: top 3 features for top problems
5. **Channels**: path to customers (Phase 4 validated) | 6. **Revenue Streams**: monetization
7. **Cost Structure**: key costs | 8. **Key Metrics**: activity metrics
9. **Unfair Advantage**: not easily copied
### 4 Big Risks
| 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 |
## Technique Selection Guide
| 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 |Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
1a864ec81cdefull audit observations/trust-audit/skill/nwave-ai__nw-opportunity-mapping.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | 1a864ec81cde | SAFE | B | 89 | first audit |
Questions
What does the Nw Opportunity Mapping skill do?
AI agents that guide you from idea to working code, with you in control at every step.
Is Nw Opportunity Mapping safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Nw Opportunity Mapping access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (1a864ec81cde), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.