Define and document disposable Proof of Life probes with hypotheses and disposal plans.
npx skills add https://github.com/tabooes/pm_skills --skill pol-probe-tabooes
Please help me install this Agent Skill. Skill: pol-probe Source: https://github.com/tabooes/pm_skills/tree/main/skills/pol-probe Command: npx skills add https://github.com/tabooes/pm_skills --skill pol-probe-tabooes
Define and document a Proof of Life (PoL) probe—a lightweight, disposable validation artifact designed to surface harsh truths before expensive development. Use this when you need to eliminate a specific risk or test a narrow hypothesis without building production-quality software. PoL probes are reconnaissance missions, not MVPs—they're meant to be deleted, not scaled.
The PoL probe framework provides five prototype flavors to match learning goals:
Fill in the PoL Probe Template to create a disposable, hypothesis-driven validation probe.
High-intent search queries and answers about installing and using this skill.
A disposable prototype for validating project feasibility is a Proof of Life (PoL) probe, a lightweight artifact designed to surface harsh truths before expensive development by testing narrow hypotheses within a few days.
To test a narrow hypothesis before building production software, define a Proof of Life (PoL) probe with a clearly stated hypothesis, a disposal plan, and a defined success or failure threshold to ensure falsifiability and actionable learnings.
The best way to run a risk validation check without an MVP is using a PoL probe, applying the golden rule of choosing the cheapest prototype that reveals the harsh truth while keeping the probe disposable and timeboxed.
Types of disposable prototypes for feasibility checks include five PoL probe flavors: feasibility checks, task-focused tests, narrative prototypes, synthetic data simulations, and vibe-coded probes, each matched to specific learning goals.
You should not use a PoL probe for risk validation when you need to build production-quality software or scale a solution, because PoL probes are reconnaissance missions meant to be deleted, not scaled.
Yes, you need a disposal plan to create a lightweight validation artifact, as the PoL probe framework requires documenting a clear disposal plan before starting to ensure the probe remains disposable and timeboxed.
omeragaakbasCreate falsifiable hypotheses and disposal plans for PoL probes.
i3ringitRun iterative UI refinement cycles on targeted components with screenshots and CSS changes.
deanpetersCreate disposable PoL probes to validate product hypotheses.
yuyuxinliValidate falsifiable hypotheses with disposable PoL probes before production development.
