plugins/nw/skills/nw-pdr-review-criteria/SKILL.md
Evidence quality validation and decision gate criteria for product discovery reviews
npx skillsauth add nwave-ai/nwave nw-pdr-review-criteriaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
"Tell me about the last time..." | "When did you last..." | "What happened when..." | "Walk me through how you..." | "What did you try..." | "How much have you spent on..." Specific dates, dollar amounts, named tools, concrete examples, emotional frustration language
"Would you use/pay/like..." | "Do you think..." | "Imagine if..." | "What if we..." Flag and reject if >20% of evidence is future-intent.
| Phase | Minimum | High Confidence | Notes | |-------|---------|-----------------|-------| | 1: Problem | 5 | 10 | Interviews required | | 2: Opportunity | 10 | 20 | Quantitative supplements, not replaces | | 3: Solution | 5 per iteration | 3 iterations max | Before decision | | 4: Viability | 5 | -- | Stakeholder review required |
Pivot decision rule: min 5 consistent signals. Block decisions on fewer.
Proceed: 5+ confirm pain + willingness to pay | Pivot: differs from expected | Kill: <20% confirm Checks: 5+ interviews, >60% confirmation, customer words, 3+ examples
Proceed: top 2-3 score >8 (0-20) | Pivot: new opportunities | Kill: all low-value Checks: OST complete with 5+, scores correct (Importance + Max(0, Importance - Satisfaction)), top >8/20
Proceed: >80% task completion, usability validated | Pivot: needs refinement | Kill: fundamental blocks Checks: 5+ users/iteration, >80% completion, core flow usable, value validated
Proceed: 4 risks addressed, model validated | Pivot: adjustment needed | Kill: no viable model Checks: Lean Canvas complete, all risks green/yellow, stakeholder sign-off
Signals: only positive quotes | skeptics not interviewed | disconfirming evidence dismissed | same questions for "right" answers Fix: include skeptics, actively seek disconfirming evidence
Signals: all existing customers | no churned/non-adopters | lacks diversity | single-enthusiast referral chain Fix: random/diverse selection, include skeptics and non-users
Signals: conclusion decided before research | findings match hypothesis perfectly | no surprises | idea-in = idea-shipped Fix: track idea evolution, expect 50%+ ideas to change
Signals: major decisions on 2-3 interviews | single quote as "validation" | pivot on one signal Fix: min 5 interviews per segment, 5+ signals for decisions
| Pattern | Detection | Bad | Good | Severity | |---------|-----------|-----|------|----------| | Leading questions | Suggests desired answer | "Don't you think this would save time?" | "Tell me about the last time you tried to save time on this" | high | | Future-intent | Hypothetical behavior | "Would you use this feature?" | "What have you tried to solve this problem?" | critical | | Compliments as validation | Accepting "that's cool" | "They loved the idea!" | "They committed to follow-up and referral" | high | | Talking > listening | >30% interviewer talk | Long questions, short responses | Open questions, extended answers | medium |
| Pattern | Detection | Severity | |---------|-----------|----------| | Skipping to solutions | Solution before problem validated | critical | | Demographic segmentation | Segments by demographics not jobs | medium | | Building before testing | Code before Phase 3 | critical |
| Pattern | Detection | Severity | |---------|-----------|----------| | Premature pivoting | Direction change on 1-2 signals (need 5+) | high | | Solution love | Defending despite evidence, dismissing critics | high | | Sole source of truth | Only quant OR qual, not both | medium |
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
development
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)