brainstorm-experiments-existing skill

by phuryn·phuryn/pm-skills·27k stars·MIT

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.

A100/100content scan

Is the brainstorm-experiments-existing skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the brainstorm-experiments-existing skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-discovery/skills/brainstorm-experiments-existing ~/.claude/skills/brainstorm-experiments-existing

available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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.

More skills from phuryn/pm-skills

Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Abrainstorm-experiments-newDesign 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.
Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Acompetitive-battlecardCreate sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'

All agent skills → · MCP servers