Feature Flag Release Plan
Plan and document a progressive feature-flag rollout for shipping a change behind a flag — defining the flag and its default-off state, the staged ramp (internal → 1% → 10% → 50% → 100%) with the success and guardrail metrics that gate each step, the automatic rollback/kill-switch criteria, and the cleanup that removes the flag once fully rolled out. A planner scopes the flag, ramp stages, and metrics, a developer writes the rollout runbook with the exact flag changes and the kill-switch procedure, and a reviewer verifies each ramp step has a measurable gate and a safe abort. Use this for gradual rollouts, canary releases, dark launches, percentage-based ramps, and de-risking a risky change behind a toggle.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Scope the rollout | Planner | define the flag, ramp stages, and gating metrics |
| 2 | Write the rollout runbook | Developer | exact flag changes, gates, and kill-switch procedure |
| 3 | Review the rollout safety | Reviewer | verify each stage has a measurable gate and safe abort |
| 4 | Evaluate | Reviewer | Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap. |
| 5 | Finish | Developer | All acceptance criteria met. Stamp a short summary and report DONE. |
Say something like "feature flag rollout plan" or "gradual rollout" or "canary release plan" or "percentage ramp" or "dark launch behind a flag" in chat to start it.