phuryn/pm-skills

brainstorm-experiments-existing

Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-experiments-existing

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

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:

  1. Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
  1. 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)
  1. 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
  1. 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

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
phuryn
Społeczność

strategy-red-team

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.

Instalacje / 1h
4
GitHub Stars
28,1 tys.
Aktualizacja
8 lis
phuryn
Społeczność

ansoff-matrix

Generate 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.

Instalacje / 1h
2
GitHub Stars
28 tys.
Aktualizacja
8 lis
phuryn
Społeczność

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Instalacje / 1h
2
GitHub Stars
28 tys.
Aktualizacja
8 lis
phuryn
Społeczność

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

Instalacje / 1h
2
GitHub Stars
28 tys.
Aktualizacja
8 lis