pol-probe

Define and document disposable Proof of Life probes for testing hypotheses.

24|3|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill pol-probe-prorise-cool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/Prorise-cool/prorise-claude-skills/tree/main/.claude/skills/product-specialist/references/domains/product-management/pol-probe
Command: npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill pol-probe-prorise-cool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you define and document lightweight, disposable validation experiments (Proof of Life probes) to test risky hypotheses cheaply before committing to expensive development.

Core Features & Use Cases

  • Define PoL Probes: Create targeted experiments to surface harsh truths about product ideas.
  • De-risk Decisions: Reduce uncertainty around technical feasibility, user task completion, or stakeholder buy-in.
  • Use Case: Before building a complex new feature, use this Skill to define a "Vibe-Coded PoL Probe" to quickly test user interest with a simple interactive mock-up, ensuring you don't waste development time on an unwanted product.

Quick Start

Use the pol-probe skill to define a Proof of Life probe for a new workflow automation idea.

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 in lean startup product development?

A Proof of Life probe is a lightweight, disposable validation artifact used to test risky hypotheses cheaply before building production software, ensuring you surface harsh truths early to reduce development risk.

How do I test risky product hypotheses cheaply before committing to development?

To test risky hypotheses cheaply, define a targeted validation experiment using a PoL probe. This approach emphasizes narrow scope and disposability to avoid prototype theater and prevents wasting expensive development time.

What types of prototypes can I use for hypothesis testing and risk reduction?

For hypothesis testing, you can use five prototype flavors: Feasibility Checks, Task-Focused Tests, Narrative Prototypes, Synthetic Data Simulations, and Vibe-Coded PoL Probes to validate technical feasibility or user task completion.

When should I use a Vibe-Coded PoL Probe instead of building production software?

Use a Vibe-Coded PoL Probe before building a complex new feature to quickly test user interest with a simple interactive mock-up, ensuring you do not waste development time on an unwanted product or unvalidated workflow automation.

How do I document a validation experiment to avoid prototype theater?

Document a validation experiment by using a structured template to define the PoL probe, emphasizing brutal honesty, narrow scope, and disposability to surface stakeholder buy-in and harsh truths without falling into prototype theater.