identify-assumptions-existing
SkillDev toolsLets your agent spot risky assumptions in a feature idea across value, usability, viability, and feasibility.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the identify-assumptions-existing skill
About this capability
Identify risky assumptions for a feature idea in an existing product across Value, Usability, Viability, and Feasibility. Uses multi-perspective devil's advocate thinking. Use when stress-testing a feature idea, doing risk assessment, or preparing for assumption mapping.
What this skill tells your AI
The instructions your AI receives, as published by phuryn/pm-skills in pm-product-discovery/skills/identify-assumptions-existing/SKILL.md and read by ahel’s review.
Identify Assumptions (Existing Product)
Devil's advocate analysis to surface risky assumptions across four risk areas.
Context
You are stress-testing a feature idea for $ARGUMENTS.
If the user provides files (designs, PRDs, research), read them first.
Instructions
The user will describe their product, objective, market segment, and feature idea. Work through these steps:
-
Think from three perspectives about why this feature might fail:
- Product Manager perspective: Business viability, market fit, strategic alignment
- Designer perspective: Usability, user experience, adoption barriers
- Engineer perspective: Technical feasibility, performance, integration challenges
-
Identify assumptions across four risk areas:
- Value: Will it create value for customers? Does it solve a real problem?
- Usability: Will users figure out how to use it? Is the learning curve acceptable?
- Viability: Can marketing, sales, finance, and legal support it?
- Feasibility: Can it be built with existing technology? Are there integration risks?
-
For each assumption, note:
- What specifically could go wrong
- How confident you are (High/Medium/Low)
- Suggested way to test it
Think step by step. Be thorough but constructive — the goal is to strengthen the idea, not kill it.
Further Reading
Signals
- GitHub stars
- 26k
- Forks
- 3k
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
identify-assumptions-existing- Source
- github.com/phuryn/pm-skills