pm-assumption-rigor-audit

Audit product validation plans and experiments for assumption-testing rigor with severity-rated findings.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-assumption-rigor-audit-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-assumption-rigor-audit
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/audits/assumption-rigor
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-assumption-rigor-audit-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams routinely claim a product idea is "validated" based on weak evidence: testing the comfortable assumption instead of the riskiest one, trusting "would you use this?" survey answers, setting success criteria after results arrive, or generalizing from a handful of users. This Skill reviews any validation plan, experiment, discovery approach, or "we validated it" claim and produces a severity-rated issue list with concrete fixes. ## Core Features & Use Cases - Seven-principle rigor framework: Checks that the riskiest assumption was tested, hypotheses are falsifiable, method fidelity matches decision risk, behavior is trusted over stated intent, success criteria were pre-set, evidence is read without goalpost-moving, and disconfirming results actually change the plan. - Severity-rated output: Classifies each finding as Critical, Major, Minor, or Cosmetic based on decision damage, and always ends with a prioritized top-3 fix list. - Scope discipline and deferral: Reviews only validation rigor when invoked directly, deferring metric validity to pm-okr-metric-validity-audit and spec risk surfacing to pm-spec-quality-audit. - Use Case: A PM pastes a discovery plan that surveyed 10 users with "would you pay $20?" and declared the idea validated. The audit flags the untested leap-of-faith assumption, the hypothetical-intent evidence, and the missing pre-set success threshold, then recommends a painted-door test with a defined conversion bar. ## Quick Start Ask the assistant to run an assumption rigor audit on your validation plan or experiment results and list the severity-rated issues with fixes.

Frequently Asked Questions about pm-assumption-rigor-audit

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

FAQPage Schema
How do I audit whether a product assumption was properly validated?▼

Run the audit on the validation plan or claim. It checks whether the riskiest assumption was tested, the hypothesis was falsifiable, the method matched the decision's stakes, success criteria were pre-set, and the evidence was real behavior rather than stated intent.

How to test product assumptions before building a feature?▼

Map assumptions by importance and certainty, then test the high-importance, low-certainty ones first with the cheapest method that answers the question, such as a painted-door or landing-page test. Define a measurable success threshold before running the test.

What severity levels does the assumption rigor audit produce?▼

Findings are rated Critical, Major, Minor, or Cosmetic based on decision damage. Critical means a load-bearing assumption drives a major investment with no valid test; Minor covers hygiene issues like undocumented results.

Does the audit check whether success metrics are valid?▼

No. Whether a metric is vanity, gameable, or unfalsifiable is deferred to the pm-okr-metric-validity-audit skill. This audit only checks that the assumption was tested rigorously against pre-set criteria.

When is a lightweight test acceptable instead of a rigorous experiment?▼

Rigor scales to the decision's stakes. A small, cheap, reversible decision does not need a statistically significant experiment, and the audit only flags mismatches: heavy methods on trivial calls or flimsy evidence under costly, irreversible bets.