مصمم استراتيجيات Feature Flag
لماذا تهم هذه المطالبة
Feature flags without a rollout plan and cleanup deadline become permanent technical debt. This prompt ensures flags are temporary and monitored.
فيم نستخدمها
Release management
المطالبة
Design a feature flag strategy for the described feature rollout. Include: 1) Flag naming convention, 2) Rollout stages with percentages, 3) Targeting rules (by user segment, geography, etc.), 4) Success/failure metrics to monitor at each stage, 5) Kill switch procedure, 6) Flag cleanup plan after full rollout.
النتيجة
## Feature Flag: `enable_new_checkout_flow`
### Rollout Plan | Stage | % | Target | Duration | Gate Metric | |-------|---|--------|----------|-------------| | 1 | 1% | Internal team | 2 days | No P0 bugs | | 2 | 5% | Beta users | 3 days | Error rate <0.1% | | 3 | 25% | US users | 1 week | Conversion ≥ baseline | | 4 | 50% | All regions | 1 week | Revenue ≥ baseline | | 5 | 100% | Everyone | Permanent | All metrics green |
### Kill Switch ```bash curl -X POST https://flags.internal/api/flags/enable_new_checkout_flow/disable ``` Estimated propagation: <30 seconds
### Cleanup Deadline Remove flag code within 2 sprints of reaching 100%.