identify-assumptions-new
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.
- License 许可
- MIT
- 最近更新
- 2026-11-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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.
03 SKILL.md 正文
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:
-
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
-
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?
-
For each assumption, rate confidence and suggest a test.
Think step by step. Save as markdown.
Further Reading
04 同仓库更多 Skills
taste-design
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
stitch-loop
Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern
site-md
Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
design-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
stitch::upload-to-stitch
Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.