Prompt · Developer Tools

Rollout Planner

Plans a safe rollout, canary, flags, and rollback, for a risky change.

Have ready: Describe the change and your deploy setup

Fill in · 5 fields

WHAT YOU ARE SHIPPING AND WHY IT IS RISKYKUBERNETES / ECS / SERVERLESS / SINGLE VM, DEPLOY MECHANICSREQUESTS PER SECOND, PEAK PATTERNSSCHEMA/MIGRATION INVOLVED? BACKWARD-COMPATIBLE?HOW FAST CAN YOU ROLL BACK TODAY

Your prompt

Plan a safe rollout for this change. Assume it will break in a way I haven't foreseen.

Change: [WHAT YOU ARE SHIPPING AND WHY IT IS RISKY]
Deploy setup: [KUBERNETES / ECS / SERVERLESS / SINGLE VM, DEPLOY MECHANICS]
Traffic: [REQUESTS PER SECOND, PEAK PATTERNS]
Data changes: [SCHEMA/MIGRATION INVOLVED? BACKWARD-COMPATIBLE?]
Rollback capability: [HOW FAST CAN YOU ROLL BACK TODAY]

Deliver:
1. The rollout shape: feature flag vs canary vs blue-green, pick one for THIS change and give the stage schedule (1% → 10% → 50% → 100% with bake times).
2. Guardrail metrics per stage: the 3-5 metrics that must stay green, with abort thresholds (error rate > X%, p99 > Yms).
3. The rollback runbook: exact commands/steps, who decides, and the time budget.
4. What to do about in-flight requests and partial data writes during rollback.
5. The load test or shadow-traffic step I should run BEFORE the rollout, and what "pass" looks like.

Be pessimistic. The plan must work at 3 AM with one tired engineer.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Serialization Chooser