产品实验设计指南：低成本验证假设的A/B测试与原型测试方法

brainstorm-experiments-existing by phuryn/pm-skills

221 周安装量

8,100 GitHub Stars

安装命令

npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-experiments-existing

🇨🇳中文介绍

在投入全面实施之前，设计低成本的实验来验证产品假设。

你正在帮助一个产品团队为 $ARGUMENTS 设计实验。该团队有一个功能想法和一些需要验证的假设。

如果用户提供了文件（PRD、假设列表、设计稿），请先阅读它们。

用户将描述他们的想法和假设。请按以下步骤进行：

 *   使用原型进行首次点击测试或任务完成度测试

 *   功能占位符或"假门"测试
 *   技术可行性探索
 *   生产环境下的 A/B 测试（需包含风险缓解措施）
 *   "绿野仙踪"方法
 *   基于调查的验证（基于行为，而非意见）

3. 遵循的关键原则：

 *   衡量实际行为，而非用户意见
 *   负责任地进行测试——不要将用户或业务置于风险之中
 *   对于生产环境测试（例如 A/B 测试），需说明风险缓解策略
 *   以最小的投入获得最大化的已验证认知

4. 对于每个实验，请明确：

 *   **假设**：我们相信什么？
 *   **实验**：我们将具体做什么来验证它？
 *   **指标**：将测量什么？
 *   **成功阈值**：如果我们是对的，预期的数值是多少？

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

Design low-effort experiments to test product assumptions before committing to full implementation.

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.

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.