identify-assumptions-new — Claude Code skill: product risk analysis
This skill maps risky assumptions behind a new product idea and suggests a test for each one. Use it when assessing a concept before moving ahead.
npx skills add phuryn/pm-skills --skill identify-assumptions-new -a claude-codeWhat identify-assumptions-new does
The skill examines a product concept from product management, design, and engineering perspectives. It sorts assumptions into eight risk categories: value, usability, viability, feasibility, ethics, go-to-market, strategy and objectives, and team. That brings questions about demand and willingness to pay alongside onboarding and technical constraints.
For each assumption, the skill asks for a confidence rating and a suggested test. If you provide a business plan or research files, read them first. The result is intended to be saved as Markdown, giving you a working list of assumptions to investigate.
Go-to-market and team risks get their own categories, which is a reason to check both explicitly. The analysis depends on a description of the product concept, target segment, and feature idea.
What it helps with
- surface assumptions that could derail a new product idea
- check whether customers will pay for the product
- spot onboarding and usability risks
- identify technical and ethical concerns before building
- turn risky assumptions into test ideas
Example prompts for the agent
- Assess this product concept for its target segment and feature idea; list risky assumptions and tests.
- Read the business plan and map its assumptions across the eight risk categories.
- Review this new product idea from product, design, and engineering perspectives, then save the analysis as Markdown.
How to install identify-assumptions-new
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill identify-assumptions-new -a claude-code2Manually: put the files in place
~/.claude/skills/identify-assumptions-new/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/identify-assumptions-new/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill identify-assumptions-new -a codex2Manually: put the files in place
.agents/skills/identify-assumptions-new/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill identify-assumptions-new -a cursor2Manually: put the files in place
.cursor/skills/identify-assumptions-new/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install phuryn/pm-skills identify-assumptions-new2Manually: put the files in place
.github/skills/identify-assumptions-new/SKILL.md1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill identify-assumptions-new -a gemini-cli2Platform CLI
gemini skills install https://github.com/phuryn/pm-skills --path pm-product-discovery/skills/identify-assumptions-newManually: put the files in place
.devin/skills/identify-assumptions-new/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill identify-assumptions-new -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about identify-assumptions-new
How do I install identify-assumptions-new in Claude Code?
Run npx skills add phuryn/pm-skills --skill identify-assumptions-new -a claude-code. The skill file is at ~/.claude/skills/identify-assumptions-new/SKILL.md.
What does identify-assumptions-new do?
It identifies risky assumptions about a new product across eight categories. For each one, it suggests rating confidence and choosing a test.
Which risk categories does the skill cover?
Value, usability, viability, feasibility, ethics, go-to-market, strategy and objectives, and team. It also examines the concept from product management, design, and engineering perspectives.
Source text
SKILL.md · MIT
--- 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: 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)
© phuryn · MIT · phuryn/pm-skills