identify-assumptions-existing

Name: identify-assumptions-existing
Author: phuryn

1.7kinstalls2.5kforks

How to install identify-assumptions-existing?

phuryn/pm-skills/identify-assumptions-existing

$npx -y skills add phuryn/pm-skills --skill identify-assumptions-existing

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	## Identify Assumptions (Existing Product)
2
3	Devil's advocate analysis to surface risky assumptions across four risk areas.
4
5	### Context
6
7	You are stress-testing a feature idea for $ARGUMENTS.
8
9	If the user provides files (designs, PRDs, research), read them first.
10
11	### Instructions
12
13	The user will describe their product, objective, market segment, and feature idea. Work through these steps:
14
15	1. Think from three perspectives about why this feature might fail:
16	- Product Manager perspective: Business viability, market fit, strategic alignment
17	- Designer perspective: Usability, user experience, adoption barriers
18	- Engineer perspective: Technical feasibility, performance, integration challenges
19
20	2. Identify assumptions across four risk areas:
21	- Value: Will it create value for customers? Does it solve a real problem?
22	- Usability: Will users figure out how to use it? Is the learning curve acceptable?
23	- Viability: Can marketing, sales, finance, and legal support it?
24	- Feasibility: Can it be built with existing technology? Are there integration risks?
25
26	3. For each assumption, note:
27	- What specifically could go wrong
28	- How confident you are (High/Medium/Low)
29	- Suggested way to test it
30
31	Think step by step. Be thorough but constructive — the goal is to strengthen the idea, not kill it.
32
33	---
34
35	### Further Reading
36
37	- [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas)
38	- [How to Manage Risks as a Product Manager](https://www.productcompass.pm/p/how-to-manage-risks-as-a-product-manager)
39	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

People who liked this also viewed

6 picks

Type

identify-assumptions-existing

1.7kinstalls2.5kforks

View on GitHub

How to install identify-assumptions-existing?

phuryn/pm-skills/identify-assumptions-existing

$npx -y skills add phuryn/pm-skills --skill identify-assumptions-existing

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Identify Assumptions (Existing Product)
2
3	Devil's advocate analysis to surface risky assumptions across four risk areas.
4
5	### Context
6
7	You are stress-testing a feature idea for $ARGUMENTS.
8
9	If the user provides files (designs, PRDs, research), read them first.
10
11	### Instructions
12
13	The user will describe their product, objective, market segment, and feature idea. Work through these steps:
14
15	1. Think from three perspectives about why this feature might fail:
16	- Product Manager perspective: Business viability, market fit, strategic alignment
17	- Designer perspective: Usability, user experience, adoption barriers
18	- Engineer perspective: Technical feasibility, performance, integration challenges
19
20	2. Identify assumptions across four risk areas:
21	- Value: Will it create value for customers? Does it solve a real problem?
22	- Usability: Will users figure out how to use it? Is the learning curve acceptable?
23	- Viability: Can marketing, sales, finance, and legal support it?
24	- Feasibility: Can it be built with existing technology? Are there integration risks?
25
26	3. For each assumption, note:
27	- What specifically could go wrong
28	- How confident you are (High/Medium/Low)
29	- Suggested way to test it
30
31	Think step by step. Be thorough but constructive — the goal is to strengthen the idea, not kill it.
32
33	---
34
35	### Further Reading
36
37	- [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas)
38	- [How to Manage Risks as a Product Manager](https://www.productcompass.pm/p/how-to-manage-risks-as-a-product-manager)
39	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

People who liked this also viewed

6 picks

Type