Identify Assumptions Existing
- 1.9k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
identify-assumptions-existing surfaces risky assumptions for live-product features across four discovery risks.
About
The identify-assumptions-existing skill devil's advocates feature proposals on live products across four Teresa Torres risk areas: value, usability, viability, and feasibility. Agents read PRDs or designs when supplied, think from PM, designer, and engineer failure perspectives, list specific assumptions with confidence levels, and suggest cheap tests. Tone is constructive strengthening not idea killing. Output captures what could go wrong, confidence high medium low, and validation approaches step by step in markdown. Differs from the new-product variant by focusing on incremental features within an existing user base and shipped context. Use when stress-testing feature ideas, risk assessment, or preparing assumption mapping workshops.
- Four risk areas for existing-product feature ideas.
- PM, designer, and engineer devil's advocate perspectives.
- Confidence ratings and suggested tests per assumption.
- Reads PRDs and design files when provided.
- Constructive tone aimed at strengthening proposals.
Identify Assumptions Existing by the numbers
- 1,922 all-time installs (skills.sh)
- +80 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #257 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
identify-assumptions-existing capabilities & compatibility
- Capabilities
- multi perspective risk scan · assumption listing · test suggestions
- Use cases
- planning · research
What identify-assumptions-existing says it does
Devil's advocate analysis to surface risky assumptions across four risk areas.
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-existingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.9k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
What could make this feature fail on our existing product?
Stress-test existing-product feature ideas across value, usability, viability, and feasibility using multi-perspective devil's advocate analysis.
Who is it for?
Feature proposals on shipped products needing risk visibility.
Skip if: Greenfield startup concepts (use identify-assumptions-new).
When should I use this skill?
User stress-tests feature ideas, risk assessment, or assumption mapping.
What you get
Assumption inventory with perspectives, confidence, and test ideas in markdown.
- risky assumptions list
- assumption mapping input
Files
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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Use for structured four-area assumption surfacing rather than writing PRDs or running user interviews.
FAQ
Which four risks are covered?
Value, usability, viability, and feasibility for the feature idea.
How is tone handled?
Constructive devil's advocate to strengthen the idea, not dismiss it.
What files can be ingested?
PRDs, designs, and research documents supplied by the user.
Is Identify Assumptions Existing safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.