Automated summary
Maps the risky assumptions behind a new product idea across eight risk categories, giving each assumption a confidence rating and a suggested test.
Strengths
- Covers eight risk categories, adding Ethics, Go-to-Market, Strategy and Team on top of the four classic product risks from Teresa Torres
- Examines the concept from three angles: product manager, designer and engineer
- Requires a confidence rating and a proposed test per assumption, making the output directly actionable
- Produces a markdown artifact that is easy to share with the team
Limitations
- No numeric prioritization of assumptions; the method points to an external canvas for that ranking
- Output quality depends entirely on the product context, segment and files the user supplies
- Runs no market research or data collection: these remain assumptions, not evidence
Use it when kicking off a new product or preparing a launch and you need to enumerate and qualify the assumptions worth validating first.
Skip it for a product already live in production, where usage metrics and findings from real data matter more than an assumption map.
Security analysis
SafeThis is a purely instructional product-management prompt. It declares no tools, performs no execution, accesses no secrets, and contains no destructive, exfiltrating, or obfuscated behavior.
No concerns found
How this analysis is madeExamples
Notre idée : une app mobile de suivi nutritionnel pour sportifs amateurs, avec scan de code-barres et coaching par IA. Liste les hypothèses risquées dans les 8 catégories, avec un niveau de confiance et un test proposé pour chacune.Lis le business plan ci-joint pour notre nouveau produit B2B et identifie les hypothèses les plus risquées en go-to-market, stratégie et équipe, puis propose un test pour chacune.Évalue ce concept de marketplace de services à domicile du point de vue du product manager, du designer et de l'ingénieur, puis cartographie les hypothèses de valeur, utilisabilité et faisabilité avec leur niveau de confiance.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:
-
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/identify-assumptions-new-product-mrwakcab' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/identify-assumptions-new-product-mrwakcab/download' --output '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md.part' && mv '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md.part' '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md' && test -s '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/identify-assumptions-new' && cp -R '.skill-downloads/identify-assumptions-new-product-mrwakcab' '.claude/skills/identify-assumptions-new'Cursor
test -f '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md' && test -s '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/identify-assumptions-new' && cp -R '.skill-downloads/identify-assumptions-new-product-mrwakcab' '.cursor/skills/identify-assumptions-new'Codex
test -f '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md' && test -s '.skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/identify-assumptions-new' && cp -R '.skill-downloads/identify-assumptions-new-product-mrwakcab' '.agents/skills/identify-assumptions-new'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/identify-assumptions-new-product-mrwakcab'openskills read 'identify-assumptions-new-product-mrwakcab'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/identify-assumptions-new-product-mrwakcab/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
PDF Reader
Productivity
Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.
Discord Messaging Workflows
Productivity
Use the message tool to send, edit, and moderate Discord messages with interactive components.
Interactive Verdict Preview
Productivity
Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.