product manager planning skill risk: low
New Product Risk Assumption Identifier
The prompt instructs the model to identify assumptions for a new product idea across eight risk categories, think from Product Manager, Designer, and Engineer perspectives, rate co…
SKILL 1 file
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)
INPUTS
- $ARGUMENTS REQUIRED
new product description
REQUIRED CONTEXT
- product concept
- target segment
- feature idea
OPTIONAL CONTEXT
- business plans
- research files
ROLES & RULES
- If the user provides files (business plans, research), read them first.
- Think step by step.
- Save as markdown.
EXPECTED OUTPUT
- Format
- markdown
- Schema
- markdown
- Constraints
- think step by step
- cover all 8 risk categories
- rate confidence and suggest a test for each assumption
- save as markdown
SUCCESS CRITERIA
- Identify assumptions across 8 risk categories
- For each assumption, rate confidence and suggest a test
CAVEATS
- Dependencies
- $ARGUMENTS
- files if provided
- Missing context
- Exact mechanism for passing $ARGUMENTS or product description
- Preferred output format or template for the 8 categories
- Ambiguities
- Does not specify desired output length or exact markdown structure.
- 'Save as markdown' is ambiguous about filename, headings, or formatting.
QUALITY
- OVERALL
- 0.76
- CLARITY
- 0.82
- SPECIFICITY
- 0.78
- REUSABILITY
- 0.72
- COMPLETENESS
- 0.75
IMPROVEMENT SUGGESTIONS
- Add an explicit markdown output template with one section per risk category.
- Clarify how files are ingested and referenced in the response.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR PRODUCT MANAGER
- Ideal Customer Profile Identifierproduct manageranalysis
- Product Strategy Canvas Generatorproduct managerproduct
- JTBD Value Proposition Designerproduct managerproduct
- Product Metrics Dashboard Designerproduct managerproduct
- Mom Test Customer Interview Script Generatorproduct managerresearch
- Product Vision Statement Brainstormerproduct managerproduct
- Product Growth Loops Analyzerproduct managermarketing
- Feature Request Theme Analyzer and Prioritizerproduct managerproduct
- Existing Product Experiment Designerproduct managerproduct
- Existing Product Feature Assumption Analyzerproduct managerproduct
- Lean Startup Pretotype Experiment Designerproduct managerproduct