pkking/identify-assumptions-new
dotfiles/dot_config/skillshare/skills/identify-assumptions-new/SKILL.md
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.
development
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add pkking/dotfiles identify-assumptions-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 9:47 AM19.7s2 files scanned
SKILL.md
- 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
- Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions
- What Is Product Discovery? The Ultimate Guide Step-by-Step
- Continuous Product Discovery Masterclass (CPDM) (video course)
Related Skills
pkking/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated Jun 9, 2026
pkking/grill-me
testing
VerifiedTrustedCommunity
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
SKILL.mdUpdated Jun 5, 2026
pkking/find-skills
data-ai
VerifiedTrustedCommunity
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
SKILL.mdUpdated Jun 4, 2026
pkking/lfg
development
VerifiedTrustedCommunity
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
SKILL.mdUpdated May 9, 2026