identify-assumptions-new

Solid

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.

Code & Development 11,758 stars 1390 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## 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 ...

Details

Author
phuryn
Repository
phuryn/pm-skills
Created
3 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

identify-assumptions-existing

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.

11,758 Updated 1 weeks ago
phuryn
AI & Automation Listed

assumption-mapper

Surfaces the assumptions a product or strategy depends on, classifies them by criticality and evidence quality, and produces a prioritized test plan. Use when: assumption mapping, identify assumptions, what could go wrong, leap-of-faith assumptions, riskiest assumption test, RAT, assumption inventory, validate before building.

1 Updated today
varunk130
Code & Development Solid

assumption-mapper

Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores, recommended validation methods, and critical assumption flags.

915 Updated 3 days ago
mohitagw15856
AI & Automation Solid

prioritize-assumptions

Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

11,758 Updated 1 weeks ago
phuryn
AI & Automation Solid

brainstorm-ideas-new

Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.

11,758 Updated 1 weeks ago
phuryn