omeragaakbas/brainstorm-experiments-existing
.claude/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.
testing
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add omeragaakbas/zoyare 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 30, 2026, 3:30 PM27.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
omeragaakbas/product-sense-interview-answer
development
VerifiedTrustedCommunity
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/product-name
data-ai
VerifiedTrustedCommunity
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/product-marketing-context
development
VerifiedTrustedCommunity
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/problem-statement
documentation
VerifiedTrustedCommunity
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.
SKILL.mdUpdated Apr 17, 2026