pol-probe

Define a disposable Proof of Life probe with hypothesis, risks, and success criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams define and document a Proof of Life (PoL) probe to cheaply surface harsh truths about a risky hypothesis before investing in production-quality development. It prevents prototype theater by forcing a narrow, falsifiable experiment with a clear disposal plan and measurable success criteria.

Core Features & Use Cases

  • Concise probe template: A one-page structure that captures hypothesis, risk, prototype type, target users, success criteria, tools, timeline, disposal plan, owner, and status checklist.
  • Five probe flavors: Guidance for feasibility checks, task-focused tests, narrative prototypes, synthetic data simulations, and vibe-coded probes so you pick the cheapest method that answers the question.
  • Quality checklist and pitfalls: Pre-launch checklist and common failure modes to keep experiments lightweight, disposable, and brutally honest.
  • Use case: Validate technical feasibility, confirm a critical task flow, test stakeholder buy-in, or simulate data without building an MVP.

Quick Start

Define a single falsifiable hypothesis, fill the PoL probe template with success criteria and a disposal date, recruit a small set of participants, run the 1–3 day test, and document learnings for decision-making.

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 when do I need to run one?

A proof of life probe is a lightweight, disposable experiment used to validate a narrow hypothesis before building production software. You need it to cheaply surface harsh truths about risky feasibility, usability, or data assumptions before investing in a full MVP.

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

To validate a risky hypothesis without an MVP, define a single falsifiable assumption, fill a probe template with success criteria and a disposal date, recruit a few participants, run a 1-3 day test, and document learnings for decision-making.

Can I use a disposable probe for usability testing and data simulation?

Yes, disposable probes support task-focused usability tests, synthetic data simulations, feasibility checks, narrative prototypes, and vibe-coded experiments, letting you pick the cheapest method that answers your specific question.

What is the best way to prevent prototype theater during early validation?

The best way to prevent prototype theater is by forcing a narrow, falsifiable experiment with a clear disposal plan and measurable success criteria, ensuring your probe remains brutally honest and lightweight within a 1-5 day execution timeline.

What should be included in a proof of life probe plan?

A proof of life probe plan must include the hypothesis, risk, prototype type, target users, success criteria, tools, timeline, owner, and a disposal plan, providing a compact one-page structure for rapid reconnaissance.

Does a proof of life probe work for technical feasibility checks in a few days?

Yes, proof of life probes are designed for 1-5 day execution, making them highly effective for rapid technical feasibility checks and vibe-coded experiments that surface critical risks early without production overhead.