/discover
Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit.
> /plugin marketplace add nWave-ai/nWave > /plugin install nw@nwave-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/discover
Context preview
What this command does when you run it.
Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit.
Command definition
discover.mddescription: "Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit."
argument-hint: "[product-concept] - Optional: --interview-depth=[overview|comprehensive] --output-format=[md|yaml]"
NW-DISCOVER: Evidence-Based Product Discovery
**Wave**: DISCOVER | **Agent**: Scout (nw-product-discoverer)
Overview
Execute evidence-based product discovery through assumption testing and market validation. First wave in nWave (DISCOVER > DISCUSS > SPIKE > DESIGN > DEVOPS > DISTILL > DELIVER).
Scout establishes product-market fit through rigorous customer development using Mom Test interviewing principles and continuous discovery practices.
Context Files Required
- docs/project-brief.md — Initial product vision (if available)
- docs/market-context.md — Market research and competitive landscape (if available)
Previous Artifacts
None (DISCOVER is the first wave).
Wave Decisions Summary
Before completing DISCOVER, produce `docs/feature/{feature-id}/discover/wave-decisions.md`:
# DISCOVER Decisions — {feature-id}
## Key Decisions
- [D1] {decision}: {rationale} (see: {source-file})
## Constraints Established
- {constraint from evidence}
## Validated Assumptions
- {assumption validated by evidence, with confidence level}
## Invalidated Assumptions
- {assumption disproved, with evidence reference}This summary enables downstream waves to quickly assess DISCOVER outcomes without reading all artifacts.
Document Update (Back-Propagation)
Not applicable (DISCOVER is the first wave — no prior documents to update).
Agent Invocation
@nw-product-discoverer
Execute \*discover for {product-concept-name}.
**Context Files:** docs/project-brief.md (if available) | docs/market-context.md (if available)
**Configuration:**
- interactive: high | output_format: markdown
- interview_depth: comprehensive | evidence_standard: past_behavior
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
Success Criteria
Refer to Scout's quality gates in ~/.claude/agents/nw/nw-product-discoverer.md.
- [ ] All 4 decision gates passed (G1-G4)
- [ ] Minimum interview thresholds met per phase
- [ ] Evidence quality standards met (past behavior, not future intent)
- [ ] Handoff accepted by product-owner (DISCUSS wave)
Next Wave
**Handoff To**: nw-product-owner (DISCUSS wave) **Deliverables**: See Scout's handoff package specification in agent file
Examples
Example 1: New SaaS product discovery
/nw-discover invoice-automation
Scout conducts customer development interviews, validates problem-solution fit through Mom Test questioning, and produces a lean canvas with evidence-backed assumptions.
Expected Outputs
docs/feature/{feature-id}/discover/
problem-validation.md
opportunity-tree.md
solution-testing.md
lean-canvas.md
interview-log.md
wave-decisions.mdRead more
description: "Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit." argument-hint: "[product-concept] - Optional: --interview-depth=[overview|comprehensive] --output-format=[md|yaml]"
NW-DISCOVER: Evidence-Based Product Discovery
**Wave**: DISCOVER | **Agent**: Scout (nw-product-discoverer)
Overview
Execute evidence-based product discovery through assumption testing and market validation. First wave in nWave (DISCOVER > DISCUSS > SPIKE > DESIGN > DEVOPS > DISTILL > DELIVER).
Scout establishes product-market fit through rigorous customer development using Mom Test interviewing principles and continuous discovery practices.
Context Files Required
- docs/project-brief.md — Initial product vision (if available)
- docs/market-context.md — Market research and competitive landscape (if available)
Previous Artifacts
None (DISCOVER is the first wave).
Wave Decisions Summary
Before completing DISCOVER, produce `docs/feature/{feature-id}/discover/wave-decisions.md`:
# DISCOVER Decisions — {feature-id}
## Key Decisions
- [D1] {decision}: {rationale} (see: {source-file})
## Constraints Established
- {constraint from evidence}
## Validated Assumptions
- {assumption validated by evidence, with confidence level}
## Invalidated Assumptions
- {assumption disproved, with evidence reference}This summary enables downstream waves to quickly assess DISCOVER outcomes without reading all artifacts.
Document Update (Back-Propagation)
Not applicable (DISCOVER is the first wave — no prior documents to update).
Agent Invocation
@nw-product-discoverer
Execute \*discover for {product-concept-name}.
**Context Files:** docs/project-brief.md (if available) | docs/market-context.md (if available)
**Configuration:**
- interactive: high | output_format: markdown
- interview_depth: comprehensive | evidence_standard: past_behavior
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
Success Criteria
Refer to Scout's quality gates in ~/.claude/agents/nw/nw-product-discoverer.md.
- [ ] All 4 decision gates passed (G1-G4)
- [ ] Minimum interview thresholds met per phase
- [ ] Evidence quality standards met (past behavior, not future intent)
- [ ] Handoff accepted by product-owner (DISCUSS wave)
Next Wave
**Handoff To**: nw-product-owner (DISCUSS wave) **Deliverables**: See Scout's handoff package specification in agent file
Examples
Example 1: New SaaS product discovery
/nw-discover invoice-automation
Scout conducts customer development interviews, validates problem-solution fit through Mom Test questioning, and produces a lean canvas with evidence-backed assumptions.
Expected Outputs
docs/feature/{feature-id}/discover/
problem-validation.md
opportunity-tree.md
solution-testing.md
lean-canvas.md
interview-log.md
wave-decisions.mdAI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).
Repo: nWave-ai/nWave
Other commands on nwave.
- /buddy
nWave concierge — ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers.
Open command - /bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD
Open command - /continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
Open command - /deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
Open command - /design
Designs system architecture with C4 diagrams and technology selection. Use when defining component boundaries, choosing tech stacks, or creating architecture documents.
Open command - /devops
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.
Open command

