ab-testing-platform-strategy
Plan A/B testing platform strategy, architecture, and build-vs-buy decisions for product engineering teams. Use when deciding whether to build or buy an experimentation platform, scoping feature flagging, targeting, assignment, exposure logging, metrics pipelines, dashboards, governance, or evolving a simple testing setup into a durable platform.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- ab-testing-platform-strategy
- license
- MIT
- metadata
- { "tags": "practical-ab-testing,ab-testing,experimentation,platform-engineering,product-analytics", "version": "0.1.0", "category": "Product Management", "displayName": "A/B Testing Platform Strategy" }
- description
- Plan A/B testing platform strategy, architecture, and build-vs-buy decisions for product engineering teams. Use when deciding whether to build or buy an experimentation platform, scoping feature flagging, targeting, assignment, exposure logging, metrics pipelines, dashboards, governance, or evolving a simple testing setup into a durable platform.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 5
- 参考文档guidelines.md1.4 KB
- 参考文档references/core/examples.md1.5 KB
- 参考文档references/core/knowledge.md2.2 KB
- 参考文档references/core/rules.md1.9 KB
- 参考文档workflows/decide-platform-strategy.md1.9 KB
03 SKILL.md 正文
A/B Testing Platform Strategy
Use this skill to decide how an organization should support A/B testing through platform choices, architecture, ownership, and incremental scope.
Source Traceability
Primary source: Practical A/B Testing by Leemay Nassery. Guidance is transformed and paraphrased from chapter 5 lines 3804-4443. Related startup and "start simple" context comes from preface lines 286-332 and chapter 2 lines 1622-1628.
Related Advanced Skills
experimentation-strategy-roadmap: use when deciding which platform capability to prioritize across rate, quality, cost, usability, and company strategy.experimentation-throughput-strategy: use when the platform needs capacity visibility, isolated versus overlapping test policies, or coordination tools.experiment-verification-monitoring: use when the platform needs QA tooling, canaries, A/A tests, active monitoring, leakage checks, or quality metrics.adaptive-experimentation-strategy: use when considering sequential testing, bandits, Thompson sampling, contextual bandits, or dynamic allocation support.
Reference Routing
| Need | Read |
|---|---|
| Platform concepts and components | references/core/knowledge.md |
| Build-vs-buy and scoping rules | references/core/rules.md |
| Scenario examples | references/core/examples.md |
| Decision workflow | workflows/decide-platform-strategy.md |
Workflow
- State the experimentation goals and current constraints.
- Inventory required platform components.
- Separate must-have launch capability from later platform maturity.
- Compare build, buy, and hybrid options against team capacity and risk.
- Plan data, assignment, exposure logging, metrics, and reporting ownership.
- Define the smallest useful platform and the triggers for expanding it.
Output Format
# A/B Testing Platform Strategy
## Recommendation
[Build | Buy | Hybrid | Start manually] because [reason].
## Current Context
- Team:
- Product surface:
- Experiment volume:
- Data maturity:
- Engineering capacity:
## Required Capabilities
| Capability | Need Now? | Build/Buy/Manual | Owner |
|------------|-----------|------------------|-------|
## Tradeoffs
- Build advantages:
- Build risks:
- Buy advantages:
- Buy risks:
- Hybrid notes:
## Incremental Roadmap
1. Minimum viable experimentation:
2. Reliability and governance:
3. Scale and self-service:
Quality Bar
- Do not recommend building a full platform before the team has proven demand.
- Do not recommend buying without checking integration, data, and governance fit.
- Keep data and exposure logging first-class; a platform without trustworthy measurement creates false confidence.
- Treat platform scope as evolutionary, not all-or-nothing.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.