pol-probe

Document narrow, disposable validation experiments for risky product hypotheses.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nv-minh/superpower-agent --skill pol-probe-nv-minh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/nv-minh/superpower-agent/tree/main/templates/base/Product-Manager-Skills/skills/pol-probe
Command: npx skills add https://github.com/nv-minh/superpower-agent --skill pol-probe-nv-minh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures product teams avoid prototype theater by documenting targeted Proof of Life probes that surface harsh truths before committing real development effort, keeping risky ideas cheap, narrow, and disposable.

Core Features & Use Cases

  • Hypothesis framing and risk definition: Capture one falsifiable question, the specific risk to eliminate, and the narrow scope that keeps the experiment focused.
  • Probe typology and execution plan: Match the scenario to one of five probe flavors, outline tools, timeline, success/failure criteria, and ownership, and commit to a disposal plan.
  • Use Case: Before investing in a new workflow automation, run the pol-probe process to define the Feasibility Check for a data integration risk, document how success looks, and plan the teardown once learnings are recorded.

Quick Start

Document the hypothesis, risk, prototype flavor, target users, tools, timeline, and disposal plan in the PoL Probe template to capture the reconnaissance mission.

Frequently Asked Questions about pol-probe

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

FAQPage Schema
What is a disposable probe for product hypothesis testing?

A Proof of Life probe is a narrow, disposable validation experiment used to test a risky product hypothesis before building production software. It ensures teams surface harsh truths early while keeping ideas cheap and scoped.

How do I document a validation experiment using a Proof of Life probe template?

To document a validation experiment, articulate a specific falsifiable hypothesis, the risk to eliminate, success criteria, timeline, tools, and a disposal plan within the PoL Probe template to capture the reconnaissance mission.

When should I use disposable probes instead of building production software?

Use disposable probes when product teams need to test a risky hypothesis before building production software. They apply to feasibility checks, task-focused tests, narrative prototypes, synthetic data simulations, or vibe-coded probes.

What types of prototype experiments can I run for product risk validation?

You can run five probe flavors for product risk validation: feasibility checks, task-focused tests, narrative prototypes, synthetic data simulations, or vibe-coded probes. Each matches specific scenarios to eliminate targeted risks.

How do I define success criteria and a disposal plan for a narrative prototype?

To frame a falsifiable hypothesis for a feasibility check, capture one narrow question and the specific risk to eliminate. This keeps the experiment focused on testing data integration risks before real development.

Why does prototype theater happen and how do I avoid it during experimentation?

Prototype theater happens when teams build elaborate prototypes without testing risky assumptions. Avoid it by documenting targeted Proof of Life probes that commit to a disposal plan and narrow scope to surface harsh truths cheaply.