identify-assumptions-existing

Identify risky assumptions in feature ideas for existing products.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify risky assumptions for feature ideas in existing products, ensuring a thorough risk assessment and informed decision-making.

Core Features & Use Cases

  • Multi-Perspective Analysis: Analyze from Product Manager, Designer, and Engineer perspectives.
  • Risk Area Assessment: Evaluate assumptions across Value, Usability, Viability, and Feasibility.
  • Assumption Testing: Suggest ways to test assumptions and mitigate risks.
  • Use Case: When stress-testing a feature idea for a product, this Skill can help identify potential pitfalls and improve the feature's design.

Quick Start

Analyze assumptions for a feature idea in your existing product by providing details about the product, objective, market segment, and feature idea.

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

To identify risky assumptions, analyze your feature idea across multiple perspectives and risk areas. Provide your product details, objective, market segment, and feature concept to surface potential pitfalls and receive targeted testing suggestions.

What is assumption testing in product analysis and when do I need it?

Assumption testing in product analysis evaluates the underlying hypotheses of a feature idea across value, usability, viability, and feasibility. You need it before development to ensure informed decision-making and mitigate risks for existing products.

Can I assess feature risks from different team perspectives like designer and engineer?

Yes, you can assess feature risks from Product Manager, Designer, and Engineer perspectives. This multi-perspective analysis evaluates assumptions across value, usability, viability, and feasibility to provide comprehensive risk mitigation strategies.

What details do I need to provide to start evaluating feature idea risks?

You need to provide details about your existing product, the objective, the target market segment, and the specific feature idea. This input allows the analysis to accurately surface risky assumptions and suggest ways to test them.

What's the best way to stress test a feature idea before development?

The best way to stress-test a feature idea is to evaluate its underlying assumptions across value, usability, viability, and feasibility risk areas. This process identifies potential pitfalls and suggests targeted tests to improve the feature's design.