Identify Assumptions Existing

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.

27,559 stars 2,851 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add phuryn/pm-skills --skill identify-assumptions-existing
Manual install
git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-discovery/skills/identify-assumptions-existing ~/.claude/skills/identify-assumptions-existing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## 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:

1. **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

2. **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?

3. **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
Read the full skill on GitHub

Details

Skill name
identify-assumptions-existing
Path
pm-product-discovery/skills/identify-assumptions-existing/SKILL.md
License
MIT
Repo updated
29 October 2026

FAQ

What does the Identify Assumptions Existing skill do?

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.

How do I install the Identify Assumptions Existing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add phuryn/pm-skills --skill identify-assumptions-existing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Identify Assumptions Existing popular?

It lives in phuryn/pm-skills, which has 27,559 GitHub stars and 2,851 forks, and is included in 3 curated skill lists.

Related skills

Ab Test Analysis

28k

phuryn/pm-skills

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

Testing & QAIn 3 lists2.9k

Analyze Feature Requests

28k

phuryn/pm-skills

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.

Frontend & DesignIn 3 lists2.9k

Ansoff Matrix

28k

phuryn/pm-skills

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

Marketing, Sales & BusinessIn 3 lists2.9k

Interview Script

28k

phuryn/pm-skills

Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.

Testing & QAIn 3 lists2.9k

Dummy Dataset

28k

phuryn/pm-skills

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.

Testing & QAIn 3 lists2.9k

Pre Mortem

28k

phuryn/pm-skills

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Testing & QAIn 3 lists2.9k

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.