Test Assumptions

Identify and prioritize leap-of-faith assumptions from product opportunities.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mjrtl/agentic_product_manager --skill test-assumptions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Test Assumptions
Source: https://github.com/mjrtl/agentic_product_manager/tree/main/skills/test-assumptions
Command: npx skills add https://github.com/mjrtl/agentic_product_manager --skill test-assumptions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and systematically test the riskiest assumptions underlying your product ideas, preventing wasted effort on unproven concepts.

Core Features & Use Cases

  • Assumption Identification: Extracts assumptions from opportunities and solutions, categorizing them by risk type.
  • Leap of Faith Prioritization: Pinpoints the most critical "leap of faith" assumptions that need immediate testing.
  • Test Card Design: Generates lightweight test cards to validate these high-risk assumptions.
  • Use Case: After defining a new feature opportunity, use this Skill to surface the core assumptions about user behavior and market need, then design quick experiments to validate them before building.

Quick Start

Use the test assumptions skill to identify and design tests for assumptions related to the 'checkout-flow' opportunity.

Frequently Asked Questions about Test Assumptions

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

FAQPage Schema
How do I test product assumptions before building a feature?

Test product assumptions by extracting them from opportunities, categorizing by risk, and designing lightweight test cards. This process prioritizes leap of faith assumptions to validate desirability, usability, feasibility, viability, and ethics.

What is a leap of faith assumption in lean startup product discovery?

A leap of faith assumption is the riskiest, most critical hypothesis underlying a product opportunity. It requires immediate validation through experimentation to reduce uncertainty before committing development effort.

How do I identify and categorize assumptions for risk assessment?

Identify assumptions by analyzing structured input on opportunities and solutions. Categorize them across desirability, usability, feasibility, viability, and ethical dimensions to generate a comprehensive assumption log.

What's the best way to design experiments for validating product viability?

Design experiments by creating lightweight test cards targeting high-risk assumptions. This method systematically reduces uncertainty across viability and other dimensions to prevent wasted effort.

Can I generate a test plan from a specific product opportunity description?

Yes, you can generate a test plan by providing structured input on a specific opportunity and proposed solutions. The system outputs an assumption log and targeted test cards for validation.

When should I not use assumption testing for product validation?

Assumption testing is not suitable when you lack structured input on opportunities and solutions. It requires defined product concepts to extract assumptions and generate meaningful test plans.