identify-assumptions-existing

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify potential risks and hidden assumptions associated with a new feature idea for an existing product, preventing costly mistakes and ensuring a more robust product strategy.

Core Features & Use Cases

  • Assumption Identification: Surfaces risky assumptions across Value, Usability, Viability, and Feasibility.
  • Multi-Perspective Analysis: Employs Product Manager, Designer, and Engineer viewpoints to uncover blind spots.
  • Risk Assessment: Helps in understanding what could go wrong and the confidence level in each assumption.
  • Use Case: Before investing heavily in developing a new mobile app feature, use this Skill to rigorously challenge the underlying assumptions about user adoption, technical feasibility, and business value.

Quick Start

Use the identify-assumptions-existing skill to identify risky assumptions for a new feature that allows users to share progress updates directly within the app.

Frequently Asked Questions about identify-assumptions-existing

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

FAQPage Schema
How do I stress-test feature ideas for an existing product?▼

To stress-test feature ideas, you identify risky assumptions across Value, Usability, Viability, and Feasibility. This process uncovers hidden risks using multi-perspective devil's advocate thinking from Product Manager, Designer, and Engineer viewpoints.

What is assumption mapping in product discovery?▼

Assumption mapping in product discovery is a risk assessment technique that identifies and evaluates risky assumptions. It categorizes assumptions by confidence level and impact to prevent costly development mistakes and ensure robust product strategy.

How do I identify risky assumptions before developing a new mobile app feature?▼

You identify risky assumptions by challenging the feature idea across four dimensions: Value, Usability, Viability, and Feasibility. Employing devil's advocate thinking helps uncover blind spots regarding user adoption, technical feasibility, and business value.

Does this risk assessment approach work for any existing product feature?▼

Yes, this risk assessment approach works for any existing product feature. It applies multi-perspective analysis from Product Manager, Designer, and Engineer viewpoints to rigorously challenge underlying assumptions about business value and technical feasibility.

Why use devil's advocate thinking for feature validation?▼

Use devil's advocate thinking for feature validation to surface blind spots that a single perspective might miss. Analyzing from Product Manager, Designer, and Engineer viewpoints ensures a comprehensive understanding of what could go wrong before investment.

What are the limitations of using devil's advocate analysis for product strategy?▼

The limitation of devil's advocate analysis is that it only identifies risky assumptions and potential issues without directly building the feature. It is a preparatory step for product discovery and must be followed by actual assumption testing and development.