identify-assumptions-existing

Identify risky assumptions for feature ideas across Value, Usability, Viability, and Feasibility.

25.0k|2.7k|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-existing-phuryn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: identify-assumptions-existing
Source: https://github.com/phuryn/pm-skills/tree/main/pm-product-discovery/skills/identify-assumptions-existing
Command: npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-existing-phuryn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify potential risks and unvalidated assumptions associated with a new feature idea for an existing product, preventing costly mistakes and improving the chances of success.

Core Features & Use Cases

  • Assumption Identification: Surfaces critical assumptions across value, usability, viability, and feasibility.
  • Risk Assessment: Evaluates the confidence level for each identified assumption.
  • Test Case Generation: Suggests methods for testing each assumption.
  • Use Case: Before investing heavily in developing a new feature, use this Skill to rigorously challenge the underlying assumptions from product, design, and engineering perspectives.

Quick Start

Use the identify-assumptions-existing skill to identify risky assumptions for a new mobile payment feature.

Frequently Asked Questions about identify-assumptions-existing

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

FAQPage Schema
How do I identify risky assumptions for a new feature in an existing product?▼

To identify risky assumptions for a new feature, evaluate the idea across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking to surface unvalidated risks before development.

What is the best way to perform a risk assessment for feature validation?▼

The best way to perform a risk assessment for feature validation is to stress-test feature assumptions from product, design, and engineering perspectives, evaluating the confidence level of each identified risk.

How does devil's advocate thinking work for product discovery?▼

Devil's advocate thinking in product discovery works by rigorously challenging a feature idea from multiple perspectives to expose critical assumptions across value, usability, viability, and feasibility before investing heavily.

Can I use assumption mapping to test mobile payment feature viability?▼

Yes, you can prepare for assumption mapping exercises by identifying and stress-testing the specific value, usability, viability, and feasibility assumptions associated with your mobile payment feature.

What do I need to provide for a thorough feature stress-test?▼

For a thorough feature stress-test, you need to provide detailed user input on product context and feature specifics so the multi-perspective analysis can accurately identify and evaluate risky assumptions.

When should I not use assumption identification for feature evaluation?▼

You should not use assumption identification when you lack detailed product context or feature specifics, as the devil's advocate analysis requires comprehensive user input to accurately evaluate risks.