phuryn/brainstorm-experiments-new
pm-product-discovery/skills/brainstorm-experiments-new/SKILL.md
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills brainstorm-experiments-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
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
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 2:07 PM30.9s1 file scanned
SKILL.md
- name:
- brainstorm-experiments-new
- description:
- Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Design Lean Startup Experiments (New Product)
Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.
Context
You are helping validate a new product concept: $ARGUMENTS using lean startup methodology.
If the user provides files (market research, landing page mockups), read them first.
Instructions
-
Create an XYZ Hypothesis in the form: "At least X% of Y will do Z"
- X%: The percentage of the target market expected to engage
- Y: The specific target market (e.g., "mid-size luxury sedan buyers")
- Z: How they will engage with the product
-
Suggest 2-3 pretotype experiments to test the hypothesis with minimal effort. Consider:
- Landing Page: Test interest by measuring sign-ups or clicks
- Explainer Video: Test understanding and appeal through engagement metrics
- Email Campaign: Test demand through response and click-through rates
- Pre-Order / Waitlist: Test willingness to pay through skin-in-the-game commitment
- Concierge / Manual MVP: Deliver the service manually to test value
-
Key principles (Alberto Savoia, The Right It):
- Skin-in-the-Game: Test willingness to pay — not just interest. Real commitment (time, money, reputation) is the only reliable signal.
- Your Own Data (YODA): Collect your own data through experiments rather than relying on Others' Data (ODP) like market reports or analogies. "The market for your idea does not care about the market for someone else's idea."
- Measure actual behavior, not users' opinions
-
For each experiment, specify the hypothesis being tested, the method, the metric, and the success threshold.
Think step by step. Save as markdown if substantial.
Further Reading
- How to Build the Right Product with Alberto Savoia (ex-Innovator at Google)
- Testing Product Ideas: The Ultimate Validation Experiments Library
- Continuous Product Discovery Masterclass (CPDM) (video course)
Related Skills
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026