pol-probe

Define disposable Proof of Life probes with falsifiable success criteria.

358|11|Updated May 15, 2026
One-click install
npx skills add https://github.com/getcrew44/crew44 --skill pol-probe-getcrew44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/product/pol-probe
Command: npx skills add https://github.com/getcrew44/crew44 --skill pol-probe-getcrew44

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

pol-probe helps you avoid prototype theater by forcing a narrow, disposable test that reveals harsh truths about a specific hypothesis before you invest in building.

Core Features & Use Cases

  • Define a Proof of Life probe: Turn one falsifiable question into a lightweight validation artifact with an explicit risk and success criteria.
  • Choose the right prototype flavor: Map your hypothesis type (feasibility, task friction, narrative buy-in, synthetic simulation, or vibe-coded workflow) to the cheapest validation method.
  • Plan disposal and learning capture: Ensure the probe has a timeboxed run, measurable harsh-truth outcomes, and an intentional deletion plan.

Quick Start

Use pol-probe to document a Proof of Life probe for your hypothesis by filling in the hypothesis, risk being eliminated, prototype type, success criteria, tools/stack, timeline, and disposal plan.

Frequently Asked Questions about pol-probe

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

FAQPage Schema
How do I validate a risky product hypothesis without building a full MVP?

A Proof of Life probe is a lightweight, disposable experiment designed to validate a narrow hypothesis and reveal harsh truths before building production software. It uses falsifiable success criteria to quickly determine if an idea is viable.

What is the best way to run disposable experiments for pre-MVP product discovery?

To choose the right prototype flavor for validation, map your hypothesis type to the cheapest test method, such as using task friction tests for usability or synthetic data simulations for feasibility. This ensures you validate assumptions without unnecessary development overhead.

How do I set falsifiable success criteria for a prototype validation test?

To document a validation probe using this framework, fill in the hypothesis, the risk being eliminated, prototype type, success criteria, tools or stack, timeline, and disposal plan. This structure ensures all critical validation parameters are explicitly defined before testing begins.

Does this validation method work for stakeholder narrative buy-in and vibe-coded workflows?

This validation approach is suitable for pre-MVP decision making where you need to test feasibility, task friction, narrative stakeholder buy-in, synthetic data simulations, or vibe-coded workflows. It is not intended for building production-grade software features.

When should I not use a Proof of Life probe for product risk reduction?

You should not use a Proof of Life probe when you need to build production-grade software or long-term features, as it is designed as a lightweight, disposable experiment with an intentional deletion plan. It is strictly for pre-MVP decision making and risk reduction.