pol-probe

Creates a documented, disposable plan for testing risky hypotheses before building software.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill pol-probe-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pol-probe
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/pol-probe
Command: npx skills add https://github.com/ch-m-n/dotfile --skill pol-probe-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams too often build expensive prototypes that are polished like MVPs yet never answer the falsifiable question blocking the next decision, so they end up ignoring the harsh truth and wasting engineering time. This Skill forces you to stop building and formally define a disposable Proof of Life probe that tests one risk cheaply before launching real products.

Core Features & Use Cases

  • PoL criteria checklist: Verifies that every probe is lightweight, disposable, narrow, brutally honest, and tiny so that it surfaces a specific failure signal instead of vanity metrics.
  • Prototype flavor guidance: Maps hypotheses to the correct flavor (Feasibility, Task-Focused, Narrative, Synthetic Data, or Vibe-Coded) and keeps you honest about the tools and timeline each style demands.
  • Template-driven documentation: Capture the hypothesis, risk, success and failure criteria, tools, timeline, and disposal plan in a single PoL Probe template—ideal for validating a new workflow automation idea before inviting engineers.

Quick Start

Describe your hypothesis, risk, prototype type, audience, success criteria, tools, timeline, and disposal plan in the PoL probe template to capture everything in one place.

Frequently Asked Questions about pol-probe

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

FAQPage Schema
What is hypothesis testing in pre-MVP product validation?

A Proof of Life probe is a lightweight, disposable test that validates one risky hypothesis cheaply before building production software. It forces teams to define narrow success criteria and avoid prototype theater by focusing on falsifiable questions.

How do I run a disposable prototype test for risk validation?

Run risk validation by documenting your narrow hypothesis, risk, success criteria, tools, timeline, and disposal plan in a Proof of Life template. Select a prototype flavor like Feasibility or Synthetic Data to test the assumption cheaply and capture a clear failure signal before building.

When should I use a Proof of Life probe instead of building an MVP?

Use a Proof of Life probe when you face technical, user, or stakeholder uncertainties before a production build. It applies when you need fast reconnaissance to answer a blocking decision cheaply, preventing the trap of building polished prototypes that ignore the harsh truth.

What is the difference between prototype theater and a feasibility probe?

Prototype theater creates polished MVP-like builds that ignore the harsh truth and waste engineering time, while a feasibility probe is a lightweight, disposable test designed to surface a specific failure signal from a narrow hypothesis cheaply before real product development begins.

What types of prototype flavors can I use for product research probes?

Product research probes can use prototype flavors including Feasibility, Task-Focused, Narrative, Synthetic Data, and Vibe-Coded. Each flavor maps to specific hypotheses and demands honest evaluation of the corresponding tools and timeline required for proper risk validation.