Brainstorm Experiments Existing
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
$ agentstack add skill-phuryn-pm-skills-brainstorm-experiments-existing ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-phuryn-pm-skills-brainstorm-experiments-existing) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: phuryn
- Source: phuryn/pm-skills
- License: MIT
- Homepage: https://www.productcompass.pm/p/pm-skills-2-red-team-ship
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.