nw-discovery-methodology

nw-discovery-methodology is a skill for Claude Code from nWave-ai/nWave. It costs 30 tokens per session (1,076 once invoked), scanned A, original, MIT.

A question-first method for mapping a user's journey before designing screens or sketches. It turns early answers into a rough flow that can be revised as understanding improves.

In plain words
What is it for?
Use it to discover user goals, map journey steps, and create early sketches with clearly marked unknowns.
Why use it?
It reduces the risk of designing the wrong experience because important goals, triggers, and success measures are made explicit first.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to discover user goals, map journey steps, and create early sketches with clearly marked unknowns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nwave-ai/nwave/nw-discovery-methodology
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nWave-ai/nWave --skill nw-discovery-methodology
Clone the repo
git clone --depth 1 https://github.com/nWave-ai/nWave

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for nw-discovery-methodology

README.md
[![agentmods](https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-discovery-methodology/github.svg)](https://agentmods.dev/skills/nwave-ai/nwave/nw-discovery-methodology)
Your own site
<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-discovery-methodology"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-discovery-methodology/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for nw-discovery-methodology

Your own site · 80×15
<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-discovery-methodology"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-discovery-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,076 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01076
Opus 5.5 $0.00012 $0.00430
Sonnet 5.5 $0.00006 $0.00215
Haiku 4.5 $0.00003 $0.00108

Measured 1mo ago against content hash 9fbc2a5174c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nw-discovery-methodology scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

nWave/skills/nw-discovery-methodology/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Discovery Methodology

Discover journeys through deep questioning before any sketching. The sketch is proof of understanding, not the starting point.

Session Flow

Phase 1: Goal Discovery (First 5-10 minutes)

Focus: What is the user trying to accomplish?

Questions:

  • "What's the ultimate goal you're trying to achieve?"
  • "What triggers this journey? When does a user start this?"
  • "How will you know when you've succeeded?"
  • "What's the happy path in your mind?"
Draft Sketch (after first 3 answers)

After collecting goal, trigger, and success criteria, output a rough draft sketch showing what the journey might look like. Mark unknowns with ???. Purpose: make value visible immediately so the user sees progress, not just questions.

[Trigger: ???] → [Step 1: ???] → [Step 2: ???] → [Goal: {stated goal}]
  Feels: ???       Sees: ???       Sees: ???       Feels: {success criteria}
  Artifacts: ???   Artifacts: ???  Artifacts: ???

This is a working hypothesis, not a commitment. Update it after each phase as understanding deepens. The sketch gives the user something concrete to react to — "no, step 2 happens before step 1" is more productive than abstract discussion.

Phase 2: Mental Model (10-20 minutes)

Focus: What does the user EXPECT to see?

Questions:

  • "Walk me through step by step -- what do you type, what do you see?"
  • "At this step, what information appears on screen?"
  • "What would you need to see to feel confident?"
  • "Where do you think this data comes from?"
  • "What's your mental model of how this works?"

Phase 3: Emotional Journey (5-10 minutes)

Focus: How should the user FEEL?

Questions:

  • "How should you feel at the start? Anxious? Curious? Confident?"
  • "What's the emotional arc -- where's the peak tension?"
  • "How should you feel when it's done?"
  • "Where might you feel frustrated or lost?"
  • "What would make this feel satisfying vs frustrating?"

Phase 4: Shared Artifacts (5-10 minutes)

Focus: What data is shared across steps?

Read the full file on GitHub · 138 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 138 lines · 30 tokens per session scan A 9fbc2a5174c6

Subscribe to this mod's changes

nw-discovery-methodology is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,076 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

tdd

Use this skill to practice test-driven development — writing tests before implementation, using tests to drive design, and validating implementation against pre-written tests. Activates when implementing new functionality, refactoring code, or fixing bugs where regression coverage is needed.

karthikrshet/aiskills · 53 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens

moai-domain-frontend

Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.

modu-ai/moai-adk · 54 tokens

craft-studio

Router for the ArtCraft craft apps (PhotoCraft, VectorCraft, FilmCraft, LightCraft, PdfCraft, EffectCraft, DesignCraft, FigCraft, WordCraft, SoundCraft, DeckCraft, CADCraft, GridCraft) driven headless via pi-craft. Use to choose which app fits a job and run the discover-execute-save-verify loop - "which craft app…

BlackBeltTechnology/pi-agent-dashboard · 103 tokens

accessibility-a11y

Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.

BlackBeltTechnology/pi-agent-dashboard · 44 tokens

tailwind-shadcn

Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.

BlackBeltTechnology/pi-agent-dashboard · 50 tokens