identify-assumptions-existing

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KoryakinYurij/Self-Sustain-System --skill identify-assumptions-existing-koryakinyurij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: identify-assumptions-existing
Source: https://github.com/KoryakinYurij/Self-Sustain-System/tree/main/Skill%20Creation/research/pm-skills/pm-product-discovery/skills/identify-assumptions-existing
Command: npx skills add https://github.com/KoryakinYurij/Self-Sustain-System --skill identify-assumptions-existing-koryakinyurij

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 improving the chances of success.

Core Features & Use Cases

  • Assumption Identification: Surfaces critical assumptions across Value, Usability, Viability, and Feasibility.
  • Devil's Advocate Analysis: Simulates Product Manager, Designer, and Engineer perspectives to uncover blind spots.
  • Risk Assessment: Helps in evaluating the potential downsides and challenges of a feature.
  • Use Case: Before investing heavily in developing a new feature, use this Skill to rigorously challenge the underlying assumptions and identify areas that need further validation or de-risking.

Quick Start

Use the identify-assumptions-existing skill to identify risky assumptions for a new feature that allows users to share their progress directly to social media.

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 before developing a new feature?

To identify risky assumptions for feature validation, you need to stress-test the idea across Value, Usability, Viability, and Feasibility. This process surfaces hidden risks by simulating devil's advocate perspectives from Product Manager, Designer, and Engineer viewpoints.

What is devil's advocate analysis in product discovery?

Devil's advocate analysis in product discovery is a risk assessment method that challenges feature assumptions by simulating multiple team perspectives. It uncovers blind spots across value, usability, viability, and feasibility to prevent costly development mistakes.

How do I perform a risk assessment for an existing product feature?

Performing a risk assessment for an existing product feature requires evaluating the new functionality against user value and technical feasibility. By mapping assumptions across four key dimensions, you can highlight areas needing further validation before committing resources.

Can I use assumption mapping for feature validation in an existing market segment?

Yes, you can use assumption mapping for feature validation by providing the existing product context, market segment, and feature idea. This generates actionable insights by challenging the underlying assumptions specific to your target audience and technical constraints.

What are the limitations of using devil's advocate thinking for feature stress-testing?

The limitation of devil's advocate thinking for feature stress-testing is that it requires complete user input regarding the product, objective, market segment, and feature idea. Without accurate foundational context, the simulated perspectives cannot effectively uncover actionable blind spots.