pol-probe

Define and document lightweight validation experiments for key risks.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/MaxKlat29/claude-setup --skill pol-probe-maxklat29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/MaxKlat29/claude-setup/tree/main/skills/product-manager-skills/skills/pol-probe
Command: npx skills add https://github.com/MaxKlat29/claude-setup --skill pol-probe-maxklat29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams quickly design and document lightweight experiments to validate risky hypotheses, avoiding costly development and avoiding prototype theater.

Core Features & Use Cases

  • Define a targeted validation experiment to test specific risks or assumptions upfront.
  • Document hypothesis, success criteria, tools, & disposal plan to ensure clarity and focus.
  • Use case includes determining product feasibility, user task success, stakeholder buy-in, or technical viability with minimal effort.

Quick Start

Use the pol-probe skill to create a structured plan for testing whether users can complete a new onboarding flow within 2 days.

Frequently Asked Questions about pol-probe

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

FAQPage Schema
How do I structure a disposable validation experiment for product feasibility?

A disposable validation experiment requires defining a specific hypothesis, setting clear success criteria, and planning prompt disposal after learning. This framework ensures experiments remain focused, falsifiable, and quickly surface harsh truths about product feasibility without costly development or prototype theater.

What is prototype theater and how do I avoid it during hypothesis testing?

Prototype theater occurs when teams build polished prototypes instead of testing risky assumptions. You avoid it by documenting lightweight validation experiments with strict disposal plans, ensuring the focus stays on mitigating key risks and gathering fast, disposable insights rather than over-investing in development.

How do I document success criteria for lightweight user task validation?

Documenting success criteria for user task validation involves explicitly defining the expected outcome before testing begins. This framework helps product teams structure hypotheses, select appropriate tools, and establish clear metrics to determine if key risks are mitigated within minimal effort and timeframe.

Can I use this validation framework for technical viability experiments?

Yes, this validation framework supports testing technical viability alongside product feasibility, user task success, and stakeholder buy-in. It allows teams to design targeted, lightweight experiments that quickly surface whether key technical risks are mitigated before committing further resources.

When should I not use rapid disposable validation experiments?

Rapid disposable validation experiments are not suitable when you need comprehensive, long-term data collection or when assumptions carry low risk. This framework is designed for quickly surfacing harsh truths about high-risk hypotheses and promptly dismissing experiments after the initial learning phase.

What's the best way to get stakeholder buy-in for a risky product hypothesis?

The best way to secure stakeholder buy-in is designing a lightweight validation experiment that surfaces harsh truths quickly. By documenting the hypothesis, success criteria, and disposal plan upfront, teams demonstrate focused risk mitigation and generate disposable insights to inform decisions with minimal effort.