pol-probe

Coordinate fast, disposable validation experiments to surface harsh truths before committing engineering effort.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill pol-probe-locus-taxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/locus-taxy/locus-SD-toolkit/tree/main/skills/pol-probe
Command: npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill pol-probe-locus-taxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proof-of-Life (PoL) probes provide a lightweight, disposable way to surface harsh truths about risky product bets before investing heavily in development. They help teams avoid prototype theater by forcing a clearly scoped validation that is easy to delete after learning.

Core Features & Use Cases

  • Narrow, falsifiable hypothesis testing with a single risk focus to minimize scope and maximize learning.
  • Quick, days-long experiments that yield actionable signals to decide whether to proceed, pivot, or discard.
  • Clear disposal plans to ensure no ongoing maintenance or code debt after learning.

Quick Start

Define a single falsifiable hypothesis, select one of the five PoL probe flavors, and document a disposal plan before building.

Frequently Asked Questions about pol-probe

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

FAQPage Schema
What is a proof-of-life probe and how does it validate risky product hypotheses?

A proof-of-life probe is a fast, disposable validation experiment designed to surface harsh truths about risky product bets. It tests a single falsifiable hypothesis to decide whether to proceed, pivot, or discard before committing engineering effort.

How do I run a quick validation experiment to test feasibility without building a full prototype?

To run a quick validation experiment, define a single falsifiable hypothesis with one risk focus, select a probe flavor, and document a disposal plan. This minimizes scope and yields actionable signals in days without prototype theater.

When should I use disposable validation probes instead of full prototype development?

Use disposable validation probes when you need to eliminate risks across feasibility, usability, or stakeholder buy-in before heavy investment. They are ideal when you require actionable signals in days and want to avoid ongoing maintenance or code debt.

How do I prevent code debt when running temporary hypothesis testing experiments?

You prevent code debt by enforcing a strict disposal plan with explicit post-probe deletion policies. Defining a clear owner and success criteria ensures the validation experiment is completely deleted after learning, avoiding any ongoing maintenance.

What is the best way to define success criteria for a focused product risk validation?

The best way to define success criteria is to narrow your test to a single falsifiable hypothesis with a defined owner. This focused approach ensures the validation yields a clear actionable signal on whether to proceed, pivot, or discard the bet.