Identify assumptions existing

Skill ComeOnOliver/skillshub/skills/phuryn/pm-skills/identify-assumptions-existing

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.From the repository description

Install

npx -y skills add ComeOnOliver/skillshub --skill identify-assumptions-existing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.7 KB, 394 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.