nw-discovery-workflow
4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking
Install / Use
npx skills add nWave-ai/nWave --skill nw-discovery-workflowInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of nw-discovery-workflow
nw-discovery-workflow scores 83/100 on our quality scale, 2232nd of 2,769 Automation skills we index.
Its SKILL.md is 4.0 KB long, well organised into 19 sections with 2 code examples: a solid amount of guidance for an agent.
It has 617 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-discovery-workflow is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-08. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-discovery-workflow compared with similar skills
All 4 of these similar skills score higher than nw-discovery-workflow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-discovery-workflow (this skill)by nWave-ai | 83 | 617 | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
Frequently asked questions
- How do I install nw-discovery-workflow?
- Run
npx skills add nWave-ai/nWave --skill nw-discovery-workflow. The install tabs above show the steps for each supported agent. - Which AI agents does nw-discovery-workflow work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nw-discovery-workflow safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nw-discovery-workflow still maintained?
- The repository was last updated about 2 months ago, so nw-discovery-workflow is actively maintained.
Skill content
View source on GitHubname: nw-discovery-workflow description: 4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking user-invocable: false disable-model-invocation: true
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+ confirm pain + willingness to pay | 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 = high importance with satisfaction gap.
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
| Metric | Target | |--------|--------| | Problem confirmation | >60% (3+ of 5) | | Frequency | Weekly+ | | Current spending | >$0 on workarounds | | Emotional intensity | Frustration evident |
Done when: 5+ interviews, >60% confirmation, articulated in customer words, 3+ examples. Threshold: 60% aligns with Mom Test -- 3/5 consistent signals = proceed, <20% = kill. Combined with qualitative markers.
Phase 2: Opportunity Mapping
| Metric | Target | |--------|--------| | Opportunities identified | 5+ distinct | | Top scores | >8 / max 20 | | Job step coverage | 80%+ | | Strategic alignment | Stakeholder confirmed |
Done when: OST complete, top 2-3 prioritized, team aligned.
Phase 3: Solution Testing
| Metric | Target | |--------|--------| | 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
| Metric | Target | |--------|--------| | Four big risks | All green/yellow | | Channel validated | 1+ viable | | Unit economics | LTV > 3x CAC (estimated) | | Stakeholder signoff | Legal, 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
| Transition | Gate | Requirements | |-----------|------|-------------| | 1 to 2 | G1 | 5+ interviews, >60% confirmation, customer words, 3+ examples | | 2 to 3 | G2 | OST complete, top 2-3 identified, scores >8, team alignment | | 3 to 4 | G3 | 5+ users tested, >80% task completion, core flow usable, validated | | 4 to handoff | G4 | Lean Canvas complete, 4 risks acceptable, go/no-go, stakeholder sign-off |
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
