pm-experiment

Generate assumption validation workflows from PMContext with pretotype experiments.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-experiment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-experiment
Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-experiment
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-experiment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams avoid building on untested beliefs by turning PMContext into a structured assumption-validation workflow. It identifies the riskiest unknowns, prioritizes them, and designs low-cost experiments before significant time or money is spent.

Core Features & Use Cases

  • 8-category risk discovery: Surfaces assumptions across Value, Usability, Viability, Feasibility, Ethics, Go-to-Market, Strategy, and Team.
  • Priority-focused validation: Uses an Impact × Risk matrix to highlight the highest-impact, highest-risk assumptions that should be tested first.
  • Experiment design with real stakes: Converts top assumptions into XYZ hypotheses and pretotype experiments with observable metrics, success thresholds, kill criteria, and skin-in-the-game.
  • Traceable product discovery: Links each assumption back to PMContext so validation work is grounded in documented user scenarios, metrics, constraints, and market inputs.
  • Use case: Ideal when a team wants to validate a new product idea, de-risk an MVP, pressure-test a feature concept, or prepare a lean experiment plan before implementation.

Quick Start

Ask the agent to run pm-experiment on the current PMContext to identify the top risky assumptions and produce XYZ hypotheses with pretotype experiments.

Frequently Asked Questions about pm-experiment

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

FAQPage Schema
How do I design pretotype experiments to validate risky product assumptions?

Assumption testing categorizes unknowns across value, usability, feasibility, viability, and ethics risks. It then applies an Impact and Risk matrix to prioritize the highest-impact, highest-risk beliefs so teams can validate what matters most before building.

How do I format an XYZ hypothesis for MVP validation?

MVP validation requires traceability to PMContext, meaning every XYZ hypothesis must link back to documented user scenarios and constraints. If source context is missing, the validation workflow triggers stop conditions to prevent ungrounded testing.

What is the best way to prioritize product discovery risks before building an MVP?

Pretotyping differs from MVP validation by focusing on low-cost, falsifiable experiments designed to kill ideas early. It uses observable success metrics and stop conditions rather than building functional product features for market release.

What happens to assumption testing if my product context is missing?

Yes, assumption testing covers ethics risks alongside value, usability, and viability. It surfaces ethical assumptions during discovery and evaluates them through the same Impact and Risk matrix to ensure responsible product decisions.