Skip to content

nWave-ai/nWave / nWave/skills/nw-discovery-workflow

nw-discovery-workflow

Verified

4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking

Discovery Workflow

4-Phase Overview

PHASE 1              PHASE 2              PHASE 3              PHASE 4
Problem Validation   Opportunity Mapping  Solution Testing     Market Viability
      |                    |                    |                    |
      v                    v                    v                    v
"Is this real?"      "Which matters?"     "Does it work?"      "Viable business?"

Phase Details

Phase 1: Problem Validation

Duration: 1-2 weeks | Min interviews: 5 | Techniques: Mom Test, Job Mapping Core question: Is this a real problem worth solving?

Phase 2: Opportunity Mapping

Duration: 1-2 weeks | Min interviews: 10 cumulative | Techniques: OST, Opportunity Algorithm Core question: Which problems matter most?

Phase 3: Solution Testing

Duration: 2-4 weeks | Min interviews: 5 per iteration | Techniques: hypothesis testing, prototypes Core question: Does our solution actually work?

Phase 4: Market Viability

Duration: 2-4 weeks | Min interviews: 5 + stakeholders | Techniques: Lean Canvas, 4 Big Risks Core question: Can we build a viable business?

Decision Gates

G1: Problem to Opportunity

Proceed: 5+ interviews, 5+ participants confirm pain, >60% confirmation across all Phase 1 interviews, willingness to pay supported by past spending or observed commitment | Pivot: problem differs from expected | Kill: <20% confirm

G2: Opportunity to Solution

Proceed: top 2-3 score >8 (max 20) | Pivot: new opportunities discovered | Kill: all low-value Scoring: Score = Importance + Max(0, Importance - Satisfaction). Each 1-10. >8 is the G2 selection threshold, not the JTBD underserved classification; use the canonical bands in nw-jtbd-opportunity-scoring.

G3: Solution to Viability

Proceed: >80% task completion, usability validated | Pivot: needs refinement | Kill: fundamental blocks

G4: Viability to Build

Proceed: all 4 risks addressed, model validated | Pivot: model needs adjustment | Kill: no viable model

Success Metrics

Phase 1: Problem Validation

MetricTarget
Problem confirmation5+ confirming participants AND >60% of all Phase 1 interviews
FrequencyWeekly+
Willingness to payPast spending on workarounds or observed commitment; retain the actual evidence, not hypothetical intent
Emotional intensityFrustration evident

Done when: 5+ interviews, 5+ participants confirm pain, >60% confirmation, willingness to pay evidenced by past spending or observed commitment, articulated in customer words, 3+ examples. Both the confirmation count and strict percentage must pass: 3/5 is exactly 60% and fails; 4/5 passes the percentage but fails the count; 5/8 passes both. Preserve actual interview counts, participant sources and negative evidence; never infer missing interviews or commitments.

Phase 2: Opportunity Mapping

MetricTarget
Opportunities identified5+ distinct
Top scores>8 / max 20
Job step coverage80%+
Strategic alignmentStakeholder confirmed

Done when: OST complete, top 2-3 prioritized, team aligned.

Phase 3: Solution Testing

MetricTarget
Task completion>80%
Value perception>70% "would use/buy"
Comprehension<10 sec to understand
Key assumptions validated>80% proven

Done when: 5+ users per iteration, core flow usable, value + feasibility confirmed.

Phase 4: Market Viability

MetricTarget
Four big risksAll green/yellow
Channel validated1+ viable
Unit economicsLTV > 3x CAC (estimated)
Stakeholder signoffLegal, finance, ops

Done when: Lean Canvas complete, all risks acceptable, go/no-go documented.

State Tracking Schema

current_phase: "1|2|3|4"
phase_started: "ISO timestamp"
interviews_completed: "count by phase"
assumptions_tracked: "list with risk scores"
opportunities_identified: "list with scores"
decision_gates_evaluated: "G1|G2|G3|G4 status"
artifacts_created: "list of file paths"

Phase Transition Requirements

TransitionGateRequirements
1 to 2G15+ interviews, 5+ participants confirm pain, >60% confirmation across all interviews, evidenced willingness to pay, customer words, 3+ examples
2 to 3G2OST complete, top 2-3 identified, scores >8, team alignment
3 to 4G35+ users tested, >80% task completion, core flow usable, validated
4 to handoffG4Lean Canvas complete, 4 risks acceptable, go/no-go, stakeholder sign-off
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall