Identify Assumptions New
- 1.9k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
identify-assumptions-new surfaces startup assumptions across eight risk categories with confidence ratings and tests.
About
The identify-assumptions-new skill extends Teresa Torres four core risks with ethics, go-to-market, strategy and objectives, and team categories for new venture evaluation. Agents read provided business plans, think from product manager, designer, and engineer perspectives about failure modes, list assumptions per category, rate confidence, and suggest tests. It assumes most ideas will not perform as hoped and outputs markdown assumption maps. Categories span value, usability, viability, feasibility, ethics, GTM channels and timing, strategic macro factors, and team composition risks. Use when evaluating startup risks, assessing new product concepts, or mapping assumptions before prioritization and experiments.
- Extends four core discovery risks to eight categories for new products.
- Uses PM, designer, and engineer devil's advocate perspectives.
- Rates confidence and proposes tests per assumption.
- Reads business plans and research files when provided.
- Outputs markdown assumption inventories for prioritization.
Identify Assumptions New by the numbers
- 1,942 all-time installs (skills.sh)
- +84 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #253 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-new capabilities & compatibility
- Capabilities
- eight category risk scan · multi perspective analysis · test suggestions
- Use cases
- research · planning
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-newAdd 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 kill this new product idea across market, team, and GTM risks?
Identify risky assumptions for new products across eight categories including GTM, strategy, ethics, and team risks beyond core product discovery.
Who is it for?
New venture concepts before prioritization or experiment design.
Skip if: Feature-level risk on an existing shipped product (use identify-assumptions-existing).
When should I use this skill?
User evaluates startup risks, new product concepts, or assumption mapping.
What you get
A categorized assumption list with confidence notes and suggested validation tests.
- Categorized assumption list
- Risk inventory across 8 categories
By the numbers
- Covers 8 risk categories for new product assumption mapping
- Extends 4 core Teresa Torres product risks with 4 additional categories
Files
Identify Assumptions (New Product)
Comprehensive risk identification across 8 categories — extending the 4 core product risks (Teresa Torres, Continuous Discovery Habits) with Ethics, Go-to-Market, Strategy & Objectives, and Team risks that are critical for new products.
Context
You are evaluating assumptions for a new product: $ARGUMENTS.
If the user provides files (business plans, research), read them first.
Domain Context
The 4 core product risks (Teresa Torres, Continuous Discovery Habits): Value, Usability, Viability, Feasibility.
For new products, extend to 8 risk categories. Good teams assume at least three-quarters of their ideas won't perform as they hope.
Instructions
The user will describe the product concept, target segment, and feature idea. Work through these steps:
1. Think from three perspectives about why this product might fail:
- Product Manager: Market demand, willingness to pay, competitive landscape
- Designer: First-time user experience, onboarding, engagement
- Engineer: Build vs. buy decisions, scalability, technical debt
2. Identify assumptions across 8 risk categories:
- Value: Will it create value for customers? Will they keep using it?
- Usability: Will people figure out how to use it? Can we onboard them fast enough? Will it increase cognitive load?
- Viability: Can we sell/monetize/finance it? Is it worth the cost? Can we support customers and help them succeed? Can we scale? Will it be compliant?
- Feasibility: Can we do it with the current technology? Is this integration possible? Can it be efficient? Can we scale it?
- Ethics: Should we do it at all? Are there any ethical considerations? Will it pose a risk for our customers?
- Go-to-Market (especially critical for new products): Can we market it? Do we have the required channels? Can we convince customers to try it? Is this the right messaging for this channel? Is this the right time? Is this the right way to launch it?
- Strategy & Objectives: What are our assumptions? Can others copy our strategy? Have we considered political, economic, legal, technological, and environmental factors? Are those the best problems to solve?
- Team: How well will the team work together? Do we have the right people? Do we have the right tools? Will the entire team stay with us long enough?
3. For each assumption, rate confidence and suggest a test.
Think step by step. Save as markdown.
---
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
Pick identify-assumptions-new over generic brainstorming when you need a structured, eight-category assumption framework tied to product-discovery practice.
FAQ
How is this different from four core risks?
It adds ethics, GTM, strategy, and team categories critical for new products.
What perspectives should agents use?
Product manager, designer, and engineer lenses on why the idea might fail.
What output format is expected?
Markdown listing assumptions with confidence ratings and test suggestions.
Is Identify Assumptions New safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.