identify-assumptions-existing

Identifies risky assumptions for existing product features across four areas.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface risky assumptions for an existing product feature across Value, Usability, Viability, and Feasibility. This skill uses a multi-perspective devil's advocate approach to stress-test ideas and surface hidden bets before commitment.

Core Features & Use Cases

  • Multi-perspective evaluation from product, design, and engineering viewpoints
  • Four-risk-area coverage: Value, Usability, Viability, Feasibility
  • Guided risk mapping with confidence levels and test suggestions

Quick Start

Provide your feature idea and current product context, and I will surface risky assumptions across Value, Usability, Viability, and Feasibility.

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 an existing product feature?

Stress-testing assumptions for a product feature requires evaluating across Value, Usability, Viability, and Feasibility. A guided devil's advocate review surfaces hidden bets, assigns confidence levels, and suggests validation tests before development commitment.

What is assumption stress-testing in product management?

Assumption stress-testing in product management is a structured devil's advocate review that evaluates feature ideas across Value, Usability, Viability, and Feasibility. It generates explicit assumption statements with confidence levels and suggested tests to surface hidden bets before committing resources.

How do I validate feature assumptions before risk mapping?

Validating feature assumptions before risk mapping involves providing your feature idea and current product context to generate a multi-perspective evaluation. This structured analysis outputs explicit assumption statements, confidence levels, and suggested tests across four risk areas: Value, Usability, Viability, and Feasibility.

Does this assumption validation approach work for existing product features?

Yes, this assumption validation approach is specifically designed for existing product features. It applies product, design, and engineering viewpoints to evaluate your feature context and surface risky assumptions across Value, Usability, Viability, and Feasibility.

What are the four risk areas for evaluating feature assumptions?

The four risk areas for evaluating feature assumptions are Value, Usability, Viability, and Feasibility. Assessing your feature across these dimensions provides a multi-perspective devil's advocate review that outputs explicit assumption statements, confidence levels, and suggested validation tests.