phuryn/brainstorm-experiments-existing
pm-product-discovery/skills/brainstorm-experiments-existing/SKILL.md
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills brainstorm-experiments-existingInstall 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, 1:54 PM32.3s1 file scanned
SKILL.md
- name:
- brainstorm-experiments-existing
- description:
- Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design Experiments (Existing Product)
Design low-effort experiments to test product assumptions before committing to full implementation.
Context
You are helping a product team design experiments for $ARGUMENTS. The team has a feature idea and assumptions that need validation.
If the user provides files (PRDs, assumption lists, designs), read them first.
Instructions
The user will describe their idea and assumptions. Work through these steps:
-
Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
-
Suggest experiments for each assumption. Consider methods like:
- First-click testing or task completion with a prototype
- Feature stubs or fake door tests
- Technical spikes
- A/B tests on production (with risk mitigation)
- Wizard of Oz approaches
- Survey-based validation (behavioral, not opinion-based)
-
Key principles to follow:
- Measure actual behavior, not users' opinions
- Test responsibly — don't put users or the business at risk
- For production tests (e.g., A/B tests), explain risk mitigation strategies
- Aim for maximum validated learning with minimal effort
-
For each experiment, specify:
- Assumption: What do we believe?
- Experiment: What exactly will we do to validate it?
- Metric: What will be measured?
- Success threshold: The expected value if we are right
Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.
Further Reading
- Testing Product Ideas: The Ultimate Validation Experiments Library
- 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
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