assets/flag_request_template.md
Feature flag request
Fill in every section before opening a PR that adds the flag.
Basics
- Name:
<kebab-case-flag-name>(e.g.,new-checkout-flow) - Owner:
<your-handle@team> - Type: [ ] Release [ ] Experiment [ ] Operational [ ] Permission
- Created:
<YYYY-MM-DD> - Expected cleanup:
<YYYY-MM-DD or "permanent">
Justification
Why a flag and not a direct deploy?
(Examples: risky launch, A/B test, kill-switch needed, gradual rollout, compliance requirement)
Rollout plan
Generated by
rollout_planner.py. Paste output below.
<paste output here>
Kill switch
- Trigger:
<concrete signal that flips the flag back to 0%> - Threshold:
<numeric threshold> - Method: [ ] Manual via dashboard URL [ ] Automated via alert webhook
- Runbook:
<link to on-call runbook>
Monitoring
- Dashboard:
<URL> - Key metrics to watch:
<metric 1>baseline:<value>, abort threshold:<value><metric 2>baseline:<value>, abort threshold:<value>
Code locations
- Decision point:
<file:line>(single point of conditional) - Provider used:
<LaunchDarkly | GrowthBook | Statsig | Unleash | Flipt | DIY> - SDK:
<sdk version / config file path>
Tests
- [ ] Test for ON branch
- [ ] Test for OFF branch
- [ ] Kill-switch test in staging (verify flag flip works)
Cleanup criteria
When can this flag be removed?
(Example: at 100% rollout for ≥7 days with no incidents)
Pre-merge checklist
- [ ]
kill_switch_audit.pypasses - [ ] flag-doc entry added with all required fields
- [ ] PR description links to this template
- [ ] Owner has write access to the provider dashboard
- [ ] Abort criteria are concrete numbers, not vague