product manager product skill risk: low
Existing Product Feature Assumption Analyzer
Analyzes a feature idea for an existing product by thinking from Product Manager, Designer, and Engineer perspectives to identify risky assumptions across Value, Usability, Viabili…
SKILL 1 file
SKILL.md
--- name: identify-assumptions-existing description: "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." --- ## 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 - [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas) - [How to Manage Risks as a Product Manager](https://www.productcompass.pm/p/how-to-manage-risks-as-a-product-manager) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
INPUTS
- $ARGUMENTS REQUIRED
the feature idea or product context being stress-tested
e.g. a new dashboard widget for existing SaaS users
REQUIRED CONTEXT
- product description
- objective
- market segment
- feature idea
OPTIONAL CONTEXT
- design files
- PRDs
- research documents
ROLES & RULES
Role assignments
- You are stress-testing a feature idea for **$ARGUMENTS**.
- If the user provides files (designs, PRDs, research), read them first.
- Think step by step.
- Be thorough but constructive — the goal is to strengthen the idea, not kill it.
EXPECTED OUTPUT
- Format
- markdown
- Constraints
- structure output by the three perspectives and four risk areas
- for each assumption include what could go wrong, confidence level, and test method
SUCCESS CRITERIA
- Think from three perspectives about why the feature might fail
- Identify assumptions across Value, Usability, Viability, and Feasibility
- For each assumption note what could go wrong, confidence level, and suggested test
CAVEATS
- Dependencies
- User-provided files if any
- Missing context
- Output format (e.g., structured list, table, or sections)
- Number of assumptions expected per risk area
- Ambiguities
- Does not specify desired output format or structure.
- Connection between the three perspectives and four risk areas is not explicitly mapped.
QUALITY
- OVERALL
- 0.82
- CLARITY
- 0.85
- SPECIFICITY
- 0.80
- REUSABILITY
- 0.90
- COMPLETENESS
- 0.70
IMPROVEMENT SUGGESTIONS
- Add an explicit 'Output Format' section defining sections, bullet style, and confidence scale usage.
- Clarify whether perspectives should be applied within each risk area or handled separately.
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
- Product Strategy Canvas Generatorproduct managerproduct
- JTBD Value Proposition Designerproduct managerproduct
- Product Metrics Dashboard Designerproduct managerproduct
- Product Vision Statement Brainstormerproduct managerproduct
- Feature Request Theme Analyzer and Prioritizerproduct managerproduct
- Existing Product Experiment Designerproduct managerproduct
- Lean Startup Pretotype Experiment Designerproduct managerproduct
- Ideal Customer Profile Identifierproduct manageranalysis
- Mom Test Customer Interview Script Generatorproduct managerresearch
- Product Growth Loops Analyzerproduct managermarketing
- New Product Risk Assumption Identifierproduct managerplanning