identify-assumptions-existing

Identifies high-risk assumptions in existing product feature ideas across four risk dimensions.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill identify-assumptions-existing-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: identify-assumptions-existing
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-product-discovery/skills/identify-assumptions-existing
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill identify-assumptions-existing-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often commit to feature ideas without surfacing the hidden assumptions that could cause failure. This Skill stress-tests a feature idea for an existing product by systematically identifying high-risk assumptions across value, usability, viability, and feasibility dimensions. ## Core Features & Use Cases - Multi-Perspective Devil's Advocate Analysis: Examines the feature idea from product manager, designer, and engineer viewpoints to uncover blind spots. - Four-Dimension Risk Framework: Maps assumptions to value (does it solve a real problem), usability (can users figure it out), viability (can the business support it), and feasibility (can it be built with current technology). - Confidence-Rated Output: Each assumption includes where it might fail, a confidence level (high/medium/low), and a suggested validation method. - Use Case: Before committing engineering resources to a new checkout flow, run this analysis to surface assumptions like "users will trust the new payment step" and plan cheap experiments to validate them. ## Quick Start Ask the AI to stress-test your feature idea by describing your product, target segment, and the feature concept, optionally attaching a PRD or design file.

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

Describe your product, target market segment, and feature idea, then analyze it from product manager, designer, and engineer perspectives. Map each assumption to value, usability, viability, or feasibility risk areas with a confidence level and validation method.

What are the four risk dimensions in product discovery?

The four dimensions are value (does it solve a real customer problem), usability (can users figure out how to use it), viability (can the business, sales, legal, and finance support it), and feasibility (can it be built with existing technology).

Can I use assumption mapping with a PRD or design file?

Yes, you can attach supporting documents such as design mockups, PRDs, or research reports. The analysis reads these files first and grounds the identified assumptions in the documented feature details.

When should I stress-test a feature idea versus building an MVP?

Stress-test assumptions before committing engineering resources, especially when confidence in key assumptions is low. Assumption mapping is cheaper than an MVP and helps prioritize which risks to validate first with targeted experiments.

What is the difference between assumption mapping for new versus existing products?

Existing-product analysis focuses on how a new feature fits current users, technology, and business constraints, including integration risks. New-product analysis typically questions whether the entire market and problem premise is valid.