identify-assumptions-existing▌
phuryn/pm-skills · updated Apr 8, 2026
Devil's advocate analysis to surface risky assumptions across four risk areas.
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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★28 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
identify-assumptions-existing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Dec 24, 2024
Useful defaults in identify-assumptions-existing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Min Robinson· Dec 16, 2024
Keeps context tight: identify-assumptions-existing is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakshi Patil· Nov 19, 2024
Registry listing for identify-assumptions-existing matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Emma Shah· Nov 7, 2024
identify-assumptions-existing has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dev Abebe· Oct 26, 2024
Solid pick for teams standardizing on skills: identify-assumptions-existing is focused, and the summary matches what you get after install.
- ★★★★★Chaitanya Patil· Oct 10, 2024
identify-assumptions-existing reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chinedu White· Sep 17, 2024
We added identify-assumptions-existing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Soo Choi· Sep 1, 2024
Keeps context tight: identify-assumptions-existing is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Hana Martin· Aug 20, 2024
identify-assumptions-existing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 28