pol-probe-advisor

Select proof-of-life validation methods based on hypothesis type and risk focus.

Updated Apr 1, 2026

Search Tags:#validation #prototyping #product validation #user testing #product hypothesis #validation method

Ready to run

npx skills add https://github.com/nnplinggg/minerva_pathfinder --skill pol-probe-advisor-nnplinggg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pol-probe-advisor
Source: https://github.com/nnplinggg/minerva_pathfinder/tree/main/Product-Manager-Skills/skills/pol-probe-advisor
Command: npx skills add https://github.com/nnplinggg/minerva_pathfinder --skill pol-probe-advisor-nnplinggg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams identify the most appropriate Proof of Life (PoL) probe type to validate their hypotheses, reducing guesswork and overinvestment.

Core Features & Use Cases

Guided Validation Selection: Uses adaptive questioning to determine whether technical feasibility, user tasks, stakeholder buy-in, modeling without risk, or real user contact is the primary focus.
Scenario-Based Recommendations: Offers tailored PoL probe suggestions such as feasibility spikes, task tests, narrative prototypes, synthetic data simulations, or vibe-coded interfaces.
Use Case: When a product team doubts whether they can build a feature or whether users will adopt it, this Skill guides them to choose the right low-fidelity or high-fidelity validation method.

Quick Start

Answer the questions about your hypothesis, risks, timeframe, and resources, then select the core question that aligns with your validation goal to receive a tailored PoL probe recommendation.

Frequently Asked Questions about pol-probe-advisor

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

FAQPage Schema

What is the best way to choose a product validation method for a new hypothesis?▼

Choosing a product validation method requires evaluating your hypothesis type, risk focus, available resources, and timeline constraints to determine whether you need a low-cost or high-fidelity approach to elicit honest user insights.

How do I validate technical feasibility versus user adoption for a product feature?▼

Validating technical feasibility versus user adoption involves identifying your primary risk focus, which directs you toward either a feasibility spike to test build capability or a task test and narrative prototype to gauge real user interaction.

When should I use low-fidelity prototyping versus high-fidelity validation approaches?▼

You should use low-fidelity prototyping, such as narrative prototypes or synthetic data simulations, when resources are constrained and timeline is short, reserving high-fidelity validation for scenarios requiring deeper user interaction.

Do I need stakeholder buy-in before running a product hypothesis validation test?▼

Stakeholder buy-in is evaluated as a specific risk focus during validation selection, guiding you toward appropriate proof-of-life probes that align modeling and simulation efforts with stakeholder expectations and resource constraints.

Can I use synthetic data simulations for product validation without risking real user contact?▼

Synthetic data simulations are recommended for product validation when your focus is modeling without risk, allowing you to test hypotheses and validate assumptions efficiently before engaging in real user contact.