pol-probe

Validate falsifiable hypotheses with disposable PoL probes before production development.

1|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/yuyuxinli/moodcoco --skill pol-probe-yuyuxinli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/yuyuxinli/moodcoco/tree/main/.claude/skills/pol-probe
Command: npx skills add https://github.com/yuyuxinli/moodcoco --skill pol-probe-yuyuxinli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PoL probes provide a lightweight, disposable method to surface harsh truths about risky ideas before investing in production development. They help teams decouple learning from code, enabling quick, low-cost validation of critical assumptions. This approach enforces clear hypotheses, measurement criteria, and a disposal plan to prevent scope creep and wasted effort.

Core Features & Use Cases

  • Narrow, falsifiable hypotheses tested quickly (2-5 days) to surface risks early.
  • Five probe flavors (Feasibility Check, Task-Focused Test, Narrative Prototype, Synthetic Data Simulation, Vibe-Coded PoL Probe) matched to different uncertainties.
  • Includes a defined disposal plan to ensure experiments are deleted after learnings, preventing technical debt and vanity metrics.
  • Useful for product, design, and strategy teams to inform go/no-go decisions before building MVPs.

Quick Start

Define a single falsifiable hypothesis, select a PoL flavor, and run a short, outcome-focused probe with a clear 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 before building an MVP?

To validate a risky product hypothesis before an MVP, use a disposable PoL probe to test a single falsifiable assumption quickly. This lightweight method surfaces harsh truths early, using a narrow scope, explicit success criteria, and a disposal plan to prevent technical debt.

What is a disposable PoL probe and how does it decouple learning from code?

A disposable PoL probe is a lightweight validation method that decouples learning from code by testing assumptions without production development. It enforces a defined disposal plan, ensuring the experimental artifact is deleted immediately after extracting insights to prevent scope creep.

When should I use synthetic data simulations versus narrative prototypes for validation?

Use synthetic data simulations to validate uncertainties around data behavior or system responses, and use narrative prototypes to test storytelling or user journey assumptions. Both are PoL probe flavors matched to specific risks, running quickly with a planned disposal.

What's the best way to prevent scope creep during early idea validation?

The best way to prevent scope creep during early idea validation is to enforce a strict disposal plan within a PoL probe. By defining a narrow scope, explicit success criteria, and deleting the artifact after learning, teams avoid vanity metrics and wasted effort.

Does a feasibility check work for testing a single falsifiable hypothesis in product strategy?

Yes, a feasibility check works for testing a single falsifiable hypothesis in product strategy. As one of the five PoL probe flavors, it allows teams to run a short, outcome-focused probe within 2-5 days to inform go/no-go decisions before investing in an MVP.

What are the limitations of using vibe-coded probes for product validation?

The limitation of using vibe-coded probes is that they are strictly disposable and cannot transition into production code. They require a defined disposal plan to delete the artifact after learning, ensuring they surface harsh truths without accumulating technical debt.