product-validation

Diagnose evidence quality and route product decisions to the cheapest validation move.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/prepforeverything/prepkit-product --skill product-validation-prepforeverything
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-validation
Source: https://github.com/prepforeverything/prepkit-product/tree/main/skills/product-validation
Command: npx skills add https://github.com/prepforeverything/prepkit-product --skill product-validation-prepforeverything

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses validation gaps and guides teams to the cheapest evidence move to move product decisions forward, ensuring outputs are backed by appropriate evidence quality.

Core Features & Use Cases

  • Evidence quality diagnosis: identify gaps, grade evidence (anecdotal, pattern, quantified, or validated), and surface the strongest counter-arguments.
  • Advisory routing: output the cheapest next step among research, experiment, PRD, defer, or reject, with justification.
  • Alignment with framework: apply product-quality-gates and reference the validation decision tree to select methods and gate decisions.

Quick Start

Provide spec/product-context.md with current problem and existing evidence data, then run the skill to generate the recommended next step and cheapest evidence move.

Frequently Asked Questions about product-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the cheapest way to validate a product decision when evidence is thin?

Product validation involves grading existing evidence from anecdotal to validated, surfacing counter-arguments, and routing to the cheapest next step like research, experiment, PRD, defer, or reject to advance decisions.

How do I assess evidence quality for product management risk analysis?

Evidence quality assessment grades data as anecdotal, pattern, quantified, or validated, then surfaces the strongest counter-arguments to ensure product decisions meet quality-gates and momentum is backed by proof.

When should I defer or reject a product feature instead of running an experiment?

Defer or reject decisions apply when evidence quality diagnosis reveals validation gaps or misalignment with product-quality-gates, indicating that momentum exists without sufficient proof to justify further investment.

How do I use product quality gates to select a validation method?

Apply product-quality-gates by providing a product context file with existing evidence, then reference the validation decision tree to select the appropriate method and gate the decision for advisory routing.

What do I need to provide to start the product evidence diagnosis process?

You need to provide a spec or product-context markdown file containing the current problem and existing evidence data to generate the recommended next step and cheapest validation move.