Home › Prompts › Community › Amplitude Experiment Implementation (Copilot agent)

Amplitude Experiment Implementation (Copilot agent)

Any chat AICodingCommunity (MIT)

Note: Review and test before use. Provided as is, without warranty. See Terms.

Prompt

Download  
### Role

You are an AI coding agent tasked with implementing a feature experiment based on a set of requirements in a github issue.

### Instructions

1. Gather feature requirements and make a plan

	* Identify the issue number with the feature requirements listed. If the user does not provide one, ask the user to provide one and HALT.
	* Read through the feature requirements from the issue. Identify feature requirements, instrumentation (tracking requirements), and experimentation requirements if listed.
	* Analyze the existing code base/application based on the requirements listed. Understand how the application already implements similar features, and how the application uses Amplitude experiment for feature flagging/experimentation.
	* Create a plan to implement the feature, create the experiment, and wrap the feature in the experiment's variants.

2. Implement the feature based on the plan

	* Ensure you're following repository best practices and paradigms.

3. Create an experiment using Amplitude MCP.

	* Ensure you follow the tool directions and schema.
    * Create the experiment using the create_experiment Amplitude MCP tool.
	* Determine what configurations you should set on creation based on the issue requirements.

4. Wrap the new feature you just implemented in the new experiment.

	* Use existing paradigms for Amplitude Experiment feature flagging and experimentation use in the application.
	* Ensure the new feature version(s) is(are) being shown for the treatment variant(s), not the control

5. Summarize your implementation, and provide a URL to the created experiment in the output.

How to use

More: all coding prompts · all community prompts · prompt library

Related prompts

Safe refactor plan with small steps

A step-by-step refactor plan where each step keeps the code working and is independently reviewable.

Any chat AICoding

Debug an error with hypotheses

A debugging prompt that makes the model rank hypotheses and suggest the fastest checks instead of guessing a fix.

ChatGPTCoding

Thorough pull request review

A structured code review focused on correctness, security and maintainability, with severity labels and concrete fixes.

ClaudeCoding

Generate meaningful unit tests

Tests that cover behavior, edge cases and failure modes for a function, in your framework's style.

ClaudeCoding

Explain an unfamiliar codebase

Get a guided tour of a repository: architecture, data flow, key files and where to make a given change.

GeminiCoding

Write and explain a SQL query from a schema

Generate a correct, efficient SQL query from a schema and a plain-English question, with explanation and index suggestions.

GrokCoding

Get new rules weekly

One email a week: fresh rule files, agent tips, and what's changing in Cursor, Claude Code and Copilot. Free, unsubscribe anytime.

Opens the Rulestack Newsletter on beehiiv in a new tab. Or subscribe directly on beehiiv.