pol-probe-advisor

Match a validation probe to a product assumption with a pre-registered kill criterion.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill pol-probe-advisor-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pol-probe-advisor
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/pol-probe-advisor
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill pol-probe-advisor-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often pick a validation method based on the tools they already have, then reverse-engineer a threshold the probe can pass, producing evidence that cannot change the roadmap. This Skill forces the kill criterion to be written before any probe is chosen, so the cheapest test that could actually stop the build gets selected. ## Core Features & Use Cases - Risk classification and probe matching: Classifies an assumption as value, usability, feasibility, or viability risk, then matches it against a matrix of nine probe types (fake door, painted door, concierge, Wizard of Oz, pre-sale, and more) with each probe's signature false positive. - Pre-registered kill criterion: Produces a four-part contract (signal, threshold, sample floor, alternative) agreed in writing before the probe runs, with the result record keeping the threshold beside the observed number. - Blast radius review: Checks who sees the probe, whether they are in a vulnerable moment, what is fabricated, and regulatory exposure before anything touches real customers. - Use Case: A team finishing a Lean UX Canvas takes its Box 7 riskiest assumption and receives three candidate probes with a comparison table, one disqualified with a reason, and a checkpoint where the humans pick the probe. ## Quick Start Ask the assistant to use the pol-probe-advisor skill to choose a Proof of Life probe for the riskiest assumption from your Lean UX Canvas Box 7.

Frequently Asked Questions about pol-probe-advisor

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

FAQPage Schema
How do I choose the right validation probe for a product assumption?▼

Classify the assumption by risk type (value, usability, feasibility, viability), write the kill criterion first, then pick the cheapest probe that could still return a failing result. Evidence strength ranks money or signature highest, then behaviour in context, behaviour in a lab, and stated intent last.

What is a kill criterion in a Proof of Life probe?▼

A kill criterion is a pre-registered contract with four parts: the signal measured, the threshold separating go from stop, a sample floor and timebox, and the alternative action if the probe fails. It must be written before the probe method is chosen.

When should I use a fake door test versus a concierge test?▼

Use a fake door to test whether a cold audience reacts to a proposition at low cost, and a concierge test to prove the outcome is valuable when delivered by hand. Fake doors risk curiosity clicks; concierge tests risk the human operator carrying the value.

Can I run multiple validation probes on one assumption at the same time?▼

No. The skill enforces one assumption and one probe, because batching probes produces multiple signals with no decision. A secondary method like an interview can run as instrumentation only, with no threshold of its own.

What are the limitations of probe-scale validation testing?▼

Probes give direction at small sample sizes, not statistical significance, so p-values and confidence intervals must never be reported. A probe needing a sprint of engineering is treated as a v1 build, and results below the sample floor are inconclusive, not a pass.