identify-assumptions-existing

Identify risks and assumptions for existing product feature ideas.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Osirs/pm-skills-sc --skill identify-assumptions-existing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: identify-assumptions-existing
Source: https://github.com/Osirs/pm-skills-sc/tree/main/01-PM%E4%BA%A7%E5%93%81%E6%8E%A2%E7%B4%A2/skills/identify-assumptions-existing
Command: npx skills add https://github.com/Osirs/pm-skills-sc --skill identify-assumptions-existing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify potential risks and hidden assumptions in new feature ideas for existing products, preventing costly mistakes and ensuring better product-market fit.

Core Features & Use Cases

  • Assumption Identification: Uncovers assumptions across value, usability, feasibility, and technical viability.
  • Risk Assessment: Evaluates the likelihood and impact of identified assumptions failing.
  • Test Planning: Suggests methods to validate critical assumptions.
  • Use Case: Before investing heavily in developing a new feature, use this Skill to rigorously challenge the underlying beliefs about user needs, technical constraints, and business viability.

Quick Start

Use the identify-assumptions-existing skill to stress-test the feature idea for our new mobile payment integration.

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 hidden assumptions in a new product feature idea?

To identify hidden assumptions in a product feature idea, evaluate the concept across four dimensions: value, usability, feasibility, and technical viability. This structured risk assessment uncovers underlying beliefs about user needs and technical constraints before development begins.

What is feature validation and when do I need to stress-test product ideas?

Feature validation is the process of rigorously challenging the underlying beliefs of a new product concept to ensure product-market fit. You need to stress-test product ideas during pre-development risk assessment to prevent costly mistakes before investing heavily in engineering.

How do I assess technical viability and feasibility risks for existing products?

Assess technical viability and feasibility risks by mapping assumptions and evaluating the likelihood and impact of those assumptions failing. This multi-perspective challenge to new features ensures better product-market fit for existing products.

What's the best way to run a devil's advocate review for feature discovery?

The best way to run a devil's advocate review for feature discovery is to systematically challenge assumptions across value, usability, feasibility, and technical viability. This structured hypothesis mapping uncovers potential risks and suggests methods to validate critical assumptions.

Does this feature validation approach work for complex integrations like mobile payment systems?

Yes, this feature validation approach works for complex integrations like mobile payment systems by stress-testing the feature idea across technical viability and feasibility. It rigorously challenges the underlying beliefs about technical constraints and business viability before development.