Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add phuryn/pm-skills --skill "identify-assumptions-new" -g -a claude-code -yOr manually — copy the SKILL.md below into:
~/.claude/skills/identify-assumptions-new/SKILL.md---
name: identify-assumptions-new
description: "Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture."
---
## 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
- [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas)
- [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session