pol-probe-advisor

pol-probe-advisor - PoL Probe Selection Advisor: Match Product Hypotheses with the Right Validation Method

Skill Overview

pol-probe-advisor is an interactive product manager validation framework. By probing your hypotheses, risks, and resources, it recommends the lowest-cost, highest-information validation method from five types of Proof of Life (PoL) probes.

Use Cases

High-risk idea, limited budget: You have a bold feature hypothesis (for example, whether AI-generated content can earn users’ trust) and need to choose the cheapest effective validation method within a few days, rather than selecting a prototype arbitrarily based on familiarity with a tool.

Uncertainty about what to test: You are facing multiple risks—whether the technology can be built, whether users can complete a task smoothly, whether leadership will approve—and cannot tell whether you should write code, make a video, or run a simulation. You need to eliminate the true risk one by one.

Preventing overbuilding: Your team tends to “build it first and figure it out later.” You need a decision framework to conduct reconnaissance before the MVP, using lightweight 1–5-day probes to uncover harsh truths and avoid discovering after weeks of development that you tested the wrong hypothesis.

Core Features

Interactive context gathering: Through 3–4 brief questions, understand your hypothesis, the specific risk to eliminate, the timeline (from a few hours to one week), and available resources (engineering capacity, design tools, and user-reach channels). Existing information can be carried over directly without asking repetitive questions.

Intelligent recommendation of five probe types: Based on the core question you need to answer, match you with one of five probes—Feasibility Check (can it be built?), Task-Focused Test (can users complete the task without friction?), Narrative Prototype (can the workflow win stakeholder alignment?), Synthetic Data Simulation (can it be modeled without production risk?), or Vibe-Coded Probe (can it withstand contact with real users?)—and provide the corresponding method, tools, and a 1–5-day timeline.

Success criteria and disposal plan: For each recommended probe, generate a PoL probe artifact containing three tiers of thresholds—pass, fail, and learn—along with a disposal plan. Once validation is complete, temporary code and data are deleted to prevent temporary prototypes from being mistaken for production assets.

Frequently Asked Questions

What is a PoL probe (Proof of Life probe)?

A PoL probe is a “proof of life” experiment: a low-cost prototype or test used to quickly validate whether a product hypothesis holds. Its purpose is not to create an impressive demo, but to eliminate a specific product risk within 1–5 days. This skill helps you choose the right one from five probe types.

What risks are the five PoL probe types suited to validating?

A Feasibility Check is suited to technical unknowns (such as whether an API returns the expected data). A Task-Focused Test is suited to measuring user completion rates for critical UI interactions. A Narrative Prototype is suited to explaining complex workflows to stakeholders and building consensus. A Synthetic Data Simulation is suited to testing edge cases and prompt logic without touching the production environment. A Vibe-Coded Probe is suited to situations where real users need to interact with a semifinished workflow to expose UX issues—it carries the highest risk and should be used only when other methods are insufficient.

How does a Vibe-Coded Probe differ from an MVP?

A Vibe-Coded Probe is an intentionally cobbled-together temporary stack (such as ChatGPT Canvas + Replit + Airtable), created only to capture workflow signals within 48 hours and then deleted after validation. An MVP is a product version intended for continuous use by real users. The biggest difference lies in the disposal plan: a probe ends in destruction, while an MVP begins with iteration. Treating a probe like an MVP leads to scope creep and technical debt.

What is “prototype theater,” and how can it be avoided?

Prototype theater refers to building a prototype to make a presentation look good without eliminating any real product risk. For example, if the actual hypothesis is “Will executives approve the budget?”, that is an organizational-political risk rather than a user risk; no matter how polished the prototype is, it does not constitute validation. To avoid this, first identify the risk to eliminate and the falsifiable success criteria, then choose the method. This skill proactively identifies such situations when you enter a hypothesis and provides alternative recommendations.