experiment-tracker · ccplugins — Claude Code plugin for experiment tracking
experiment-tracker is a Claude Code plugin for tracking A/B tests and feature experiments, documenting changes, and reviewing results before a launch decision.
Apache-2.0 ★ 1,013 updated 2026-08-12
/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install experiment-tracker@awesome-claude-code-pluginsWhat experiment-tracker does
The plugin includes a subagent for feature experiments, A/B tests, and iterative improvements. It can help document a test, set up tracking, and analyze results. Call on it when adding a feature flag, changing an experiment, or reviewing its outcomes.
It can also compile results after launch and at experiment milestones, helping inform a decision about whether to expand a test. Its workflow is framed around a six-day development cycle. The subagent needs experiment results and metrics to analyze; it does not replace the data collected by a test.
What it helps with
- document an A/B test and record changes to it
- track results after launching an experimental feature
- review test outcomes before expanding an experiment
- weigh metrics and user feedback before deciding what to do with a feature
Example prompts for the agent
- Document an A/B test for the new onboarding flow and help set up tracking.
- Review the results of the launched feature experiment and advise whether to expand the test.
- Compare the metrics and user feedback for this experimental feature before we decide whether to keep it.
How to install experiment-tracker
Plugin marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins/plugin install experiment-tracker@awesome-claude-code-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about experiment-tracker
How do I install experiment-tracker in Claude Code?
Run these commands in order: /plugin marketplace add ccplugins/awesome-claude-code-plugins, then /plugin install experiment-tracker@awesome-claude-code-plugins.
What does experiment-tracker do?
It adds a subagent that helps document feature experiments and A/B tests, track their results, and analyze experiment data.
When should I use experiment-tracker?
Use it when starting or changing an experiment, adding a feature flag, or reviewing results before deciding whether to expand a test.
Source text
experiment-tracker · Apache-2.0
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are introduced. Examples:\n\n<example>\nContext: When implementing feature flags or A/B test variants\nuser: "Add a feature flag to test the new onboarding flow"\nassistant: "I've implemented the feature flag for the onboarding flow A/B test. Let me use the experiment-tracker agent to properly document this experiment and set up tracking."\n<commentary>\nEvery feature flag represents an experiment that needs proper tracking and success metrics.\n</commentary>\n</example>\n\n<example>\nContext: After deploying experimental features\nuser: "The new viral sharing feature is now live for 10% of users"\nassistant: "Great! The viral sharing feature is deployed. I'll use the experiment-tracker agent to monitor its performance and document initial results."\n<commentary>\nLive experiments need immediate tracking setup to capture valuable data from the start.\n</commentary>\n</example>\n\n<example>\nContext: When reaching experiment milestones\nuser: "It's been a week since we launched the TikTok integration test"\nassistant: "Perfect timing for analysis. Let me use the experiment-tracker agent to compile the week-one results and determine if we should expand the test."\n<commentary>\nRegular experiment checkpoints ensure data-driven decisions about feature rollouts.\n</commentary>\n</example>\n\n<example>\nContext: Before making product decisions\nuser: "Should we keep the AI avatar feature or remove it?"\nassistant: "Let me analyze the experiment data to inform this decision. I'll use the experiment-tracker agent to review all metrics and user feedback for the AI avatar feature test."\n<commentary>\nProduct decisions should be backed by experiment data, not gut feelings.\n</commentary>\n</example>
© Michael Galpert · Apache-2.0 · ccplugins/awesome-claude-code-plugins
Similar plugins
All plugins for Testing and QA →experiment-tracker by other authors comes first.