# Plan a feature flag rollout and rollback

Designs a staged release behind a feature flag, with audience steps, metrics to watch, kill criteria, and flag cleanup.

- Topic: Software Development
- Framework: Few-Shot
- Level: Standard
- Tags: Data & Analytics, Plan, Code, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/plan-a-feature-flag-rollout-and-rollback

## Prompt

```text
Help me plan the rollout of a feature behind a feature flag.

**Feature:** [WHAT CHANGES FOR USERS OR SYSTEMS]
**Flag tooling:** [e.g. "LaunchDarkly", "Unleash", "homegrown config table", "env variable"]
**Blast radius if it breaks:** [e.g. "checkout fails", "slower search", "cosmetic only"]
**Who must be told:** [SUPPORT, SALES, OTHER TEAMS, CUSTOMERS]
**Metrics I can watch:** [ERROR RATES, LATENCY, CONVERSION, BUSINESS KPIs - or "not sure"]

Build the plan:
1. Flag design: flag name, default value, what the "off" path does, and whether old and new code paths can safely flip back and forth (call out data written by the new path that the old path can't read).
2. Rollout stages, e.g. internal staff, 1%, 10%, 50%, 100%, with how long to hold at each and how users are bucketed (sticky by user, account, or region).
3. Go/no-go criteria per stage: the specific metrics and thresholds to check. Use [SET THRESHOLD] where I haven't given baselines.
4. Kill switch: who can turn it off, how fast it takes effect, and what happens to in-flight requests.
5. Communication: who to notify at each stage, plus a 2-line message for support.
6. Cleanup: when to remove the flag and the old code path, with a reminder ticket.

Return the plan as a table of stages, followed by the risks list and the cleanup checklist.
```

## What to fill in

- WHAT CHANGES FOR USERS OR SYSTEMS
- e.g. "checkout fails", "slower search", "cosmetic only"
- SUPPORT, SALES, OTHER TEAMS, CUSTOMERS
- SET THRESHOLD

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.