/nw-discover

name: nw-discover
description: "Tests whether a product problem and opportunity are real, then updates the durable product evidence authorities without creating delivery state."
user-invocable: true
argument-hint: '[product-concept]'

NW-DISCOVER

Purpose

Reduce product uncertainty before requirements or architecture investment. Use customer evidence, assumption tests and counterexamples; never promote a founder belief to fact by repetition.

Workflow

1. State the opportunity, riskiest assumptions and falsification thresholds. 2. Gather evidence with source, sample size, date and confidence. Separate observation, inference and hypothesis. 3. Test problem severity, current workaround, triggering context and willingness to change. Seek disconfirming evidence. 4. Decide `VALIDATED`, `PIVOT`, `MORE_EVIDENCE` or `STOP`. 5. Update the existing durable product authority that owns the result: vision, jobs, journey evidence or KPI baseline. Preserve provenance and stable ids.

Return changed authority paths, evidence citations, confidence and the next unresolved question. Do not create a feature directory, manual handover, wave report, plan or progress artifact.

Human-readable authority

When discovery changes product facts, return those facts to the Product Owner; do not edit generated briefs. Use current full briefs and HTML when useful, with `nw-doc-as-artifact` for collaborative reading. Discovery evidence alone does not create delivery state, prove completion or require an HTML view.