Identify Assumptions New
Map risky assumptions across eight categories before you commit build time to a new product idea or venture.
Overview
identify-assumptions-new is an agent skill most often used in Validate (also Idea) that systematically lists risky assumptions for a new product across eight categories using PM, designer, and engineer failure perspectiv
Install
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-newWhat is this skill?
- Works through eight risk categories—Value, Usability, Viability, Feasibility plus Ethics, Go-to-Market, Strategy & Objec
- Applies Teresa Torres’s four core product risks from Continuous Discovery Habits and extends them for pre-launch gaps
- Surfaces failure modes from three lenses: Product Manager, Designer, and Engineer
- Starts from your product concept, segment, and feature idea and optional uploaded plans or research files
- Frames expectation that strong teams assume most ideas will underperform—useful for honest prioritization
- 8 risk categories for new products
- 4 core product risks from Continuous Discovery Habits (Teresa Torres)
- Assumes at least three-quarters of product ideas may underperform expectations
Adoption & trust: 1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a compelling new product idea but no structured list of what must be true—and which beliefs could sink the venture if they are wrong.
Who is it for?
Solo founders or indie builders at concept or pre-MVP stage who want a disciplined assumption map before writing code or hiring.
Skip if: Teams validating an existing shipped product with usage data—use a continuous-discovery or live-product assumption skill instead—or anyone who already has a signed-off spec and only needs implementation planning.
When should I use this skill?
evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture
What do I get? / Deliverables
You leave with assumptions grouped across eight risk categories and three professional viewpoints, ready to rank tests and tighten MVP scope before build.
- Categorized assumption list across eight risk types
- Failure-oriented notes from PM, designer, and engineer perspectives
- Prioritization-ready risk map for validation experiments
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
New-product risk mapping is the canonical validate step: you prove whether the concept is worth building by surfacing Value, Viability, and Go-to-Market assumptions before scope locks. Scope subphase is where solo builders decide what to build and what must be true; this skill turns a concept into an explicit assumption inventory for prioritization and tests.
Where it fits
Before cutting MVP scope, list Value and Feasibility assumptions so you only build features tied to testable beliefs.
Surface Viability and Go-to-Market assumptions about willingness to pay and channel fit before setting price experiments.
Compare two opportunity sketches by contrasting Strategy & Objectives and Team risks side by side.
Re-run Ethics and Feasibility categories when choosing build-vs-buy or third-party AI vendors mid-implementation.
How it compares
Use instead of unstructured brainstorming about “what could go wrong” without Teresa Torres–style risk categories or role-based lenses.
Common Questions / FAQ
Who is identify-assumptions-new for?
It is for solo builders, indie hackers, and small teams evaluating a new product concept who need a repeatable way to surface Value, Go-to-Market, Team, and other risks before committing to build.
When should I use identify-assumptions-new?
Use it in Validate when scoping an MVP or pricing tests; in Idea when comparing opportunities and documenting discovery risks; and again in Build if feasibility or ethics assumptions need a refresh before major technical bets.
Is identify-assumptions-new safe to install?
It is procedural guidance that may read user-supplied files you attach; review the Security Audits panel on this Prism page for the package’s install footprint and audit status before adding it to your agent.
SKILL.md
READMESKILL.md - Identify Assumptions New
## 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)