identify-assumptions-existing
GitHub针对现有产品功能创意进行压力测试,从PM、设计、工程三视角识别价值、可用性、可行性及生存力方面的风险假设。用于风险评估和假设映射准备。
Trigger Scenarios
Install
npx skills add phuryn/pm-skills --skill identify-assumptions-existing -g -y
SKILL.md
Frontmatter
{
"name": "identify-assumptions-existing",
"description": "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."
}
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
Version History
- 18468a9 Current 2026-07-25 10:32


