PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.6)
Token size
2,766
Example input
[FEATURE_FLAG_DEFINITIONS_AND_CONFIGURATION]: checkout_v2_enabled: boolean, temporary release flag Default: false Owner: Payments Team Environments: staging + production [FLAG_USAGE_ACROSS_CODEBASE]: Web checkout uses checkout_v2_enabled Payment API also checks the flag Order creation depends on Checkout V2 Database writes use the new order schema when enabled [ROLLOUT_AND_TARGETING_RULES]: Internal users: 100% Production: 10% initially Targeting: users in India and Singapore Exclusion: users with legacy_payment_issue=true [MONITORING_METRICS_AND_INCIDENT_HISTORY]: Checkout error rate Payment failure rate Checkout latency Order creation failures Conversion rate No feature-specific alert currently configured [FEATURE_LIFECYCLE_OWNERSHIP_AND_BUSINESS_CONSTRAINTS]: Feature is intended to replace legacy checkout No confirmed retirement date Payments Team owns the feature Incorrect orders or duplicate payments are considered critical incidents
Example output
PHASE 1 - Feature Flag Inventory Observed evidence: Field Finding Flag checkout_v2_enabled Type Boolean release flag Purpose Enable new checkout Owner Payments Team Production state 10% rollout Default OFF Consumers Web + Payment API + Order creation Cache Up to 5 minutes Retirement Not defined Classification: 🟑 Transitional Reason: Feature is actively rolling out. It affects payment and order creation. It has multiple service consumers. Retirement criteria are not yet defined. Test verdict: PASS for active usage classification. --- PHASE 2 - Code Path Analysis Trace: checkout_v2_enabled β†’ Web checkout β†’ Payment API β†’ Order creation β†’ New database schema Critical Finding The flag controls both payment behavior and database behavior. That makes this a high-risk feature flag. If Web evaluates the flag as ON while Payment API evaluates it as OFF: Web ↓ Checkout V2 ↓ Payment API ↓ Legacy payment path This can create incompatible behavior. Risk: πŸ”΄ High Test verdict: FAIL pending cross-service consistency validation. --- PHASE 3 - Stale / Orphaned Detection The flag is actively used by three components. There is no evidence that the feature has been permanently enabled or abandoned. Therefore: Classification: NOT STALE Cleanup should not be recommended yet. Test verdict: PASS --- PHASE 4 - Flag Conflict Analysis Potential state: Web: checkout_v2_enabled = ON Payment API: checkout_v2_enabled = OFF Because each service refreshes independently, this mixed state is possible for up to the cache/propagation window. Risk The system could process one checkout using different feature versions across services. Finding: checkout_v2_enabled has a cross-service consistency risk. Severity: πŸ”΄ Critical Recommended control Use one of: Centralized evaluation Versioned feature configuration Shared evaluation context Explicit checkout version passed between services Avoid allowing each service to independently make incompatible decisions. --- PHASE 5 - Default & Fallback Safety Current behavior: Flag service unavailable ↓ Default = OFF ↓ Legacy checkout This is generally safer than defaulting payment functionality to the new unproven path. However, there is an important question: Can the legacy checkout safely process orders created by users who started in Checkout V2? If NO, the OFF fallback is not actually safe during a mixed-state request. Result Default classification: 🟑 Acceptable with conditions Required validation: Payment compatibility Order schema compatibility Idempotency compatibility Session compatibility Retry behavior --- PHASE 6 - Kill-Switch Audit Checkout directly affects: Payments Orders Revenue Customer experience Therefore an emergency kill switch is mandatory. The existing flag can function as a kill switch only if: Evaluation is reliable Configuration propagates quickly All services honor it Emergency override is available Cached values cannot keep unsafe behavior active for too long Current cache duration: 5 minutes Finding A production payment feature may remain enabled for several minutes after an emergency disable. Severity: πŸ”΄ High Recommendation: Create an emergency override with a much shorter propagation path. Test verdict: FAIL --- PHASE 7 - Rollout Condition Audit Current targeting: India + Singapore ↓ 10% users ↓ Exclude legacy_payment_issue users Missing conditions The rollout does not explicitly account for: New vs returning users Platform Account type High-value customers Payment method Geographic edge cases Known high-risk cohorts Percentage rollout alone should not be treated as sufficient safety. Finding Risk: 🟠 Medium Before expanding to 25%, define a stable cohort strategy. --- PHASE 8 - Progressive Rollout Test Recommended progression: Stage 0 Internal users ↓ Stage 1 1% production ↓ Stage 2 5% ↓ Stage 3 10% ↓ Stage 4 25% ↓ Stage 5 50% ↓ Stage 6 100% Promotion requirement Do not promote based solely on time. Require: Error rate within baseline Payment failures within baseline No duplicate orders No abnormal refund/chargeback signals Latency within agreed threshold Conversion not materially degraded No critical incidents --- PHASE 9 - Monitoring Audit Existing metrics are useful but incomplete. Required rollout dashboard Checkout V2 β”œβ”€β”€ Checkout success rate β”œβ”€β”€ Payment authorization rate β”œβ”€β”€ Payment failure rate β”œβ”€β”€ Order creation success β”œβ”€β”€ Duplicate order rate β”œβ”€β”€ Duplicate payment rate β”œβ”€β”€ P95/P99 latency β”œβ”€β”€ 5xx rate β”œβ”€β”€ Conversion rate └── Support/incident signals Promotion Continue rollout when: Technical metrics remain within baseline Business metrics remain stable No critical incidents No cross-service inconsistency detected Pause Pause when: Error rate materially exceeds baseline Latency degradation appears Payment failures increase Conversion drops unexpectedly Kill switch Immediately disable when: Duplicate payments occur Incorrect order creation occurs Data corruption is detected Critical payment failures emerge --- PHASE 10 - Automated Test Matrix Scenario Expected Result Status Flag ON Checkout V2 used PASS Flag OFF Legacy checkout used PASS Missing flag Safe fallback NEEDS TEST Flag service outage Legacy checkout NEEDS TEST Evaluation timeout Safe fallback NEEDS TEST Web ON + API ON V2 flow NEEDS TEST Web ON + API OFF Prevent incompatible state FAIL Partial rollout Correct cohort only NEEDS TEST Excluded user Legacy flow NEEDS TEST Kill switch Immediate safe disable NEEDS TEST Cache expiration Consistent behavior NEEDS TEST Database migration mismatch Prevent unsafe write NEEDS TEST Overall test coverage: INSUFFICIENT --- PHASE 11 - Rollout Failure Test Scenario Payment API receives stale flag configuration. Web = ON Payment API = OFF DETECT Monitor: Version mismatch Payment failures Order creation failures Unexpected fallback rate STOP Immediately pause rollout at 10%. CONTAIN Disable Checkout V2 through emergency override. RECOVER Force configuration refresh across services. VERIFY Run: Payment test Order creation test Idempotency test Production smoke test Only then resume rollout. --- PHASE 12 - Cross-Service Consistency Test Test Create the following matrix: Web API Expected OFF OFF Legacy ON ON V2 ON OFF BLOCK / SAFE FALLBACK OFF ON BLOCK / SAFE FALLBACK The dangerous states are: ON + OFF OFF + ON These must not silently produce incompatible business behavior. Result: πŸ”΄ FAIL --- PHASE 13 - Cleanup Test Do not remove the flag yet. Before retirement: 1. Reach 100% rollout. 2. Monitor production stability. 3. Confirm business acceptance. 4. Confirm no rollback requirement. 5. Identify all remaining consumers. 6. Remove legacy branches. 7. Remove flag configuration. 8. Remove obsolete tests. 9. Remove rollout dashboards. 10. Verify production behavior. Cleanup confidence currently: LOW --- PHASE 14 - Governance Findings For this flag, governance should require: Named owner Documented business purpose Creation date Planned retirement condition Maximum rollout duration Explicit default behavior Kill-switch capability Cross-service compatibility ON/OFF automated tests Failure-mode tests Rollout monitoring Audit trail for configuration changes --- PHASE 15 - Prioritized Roadmap πŸ”₯ Immediate 1. Fix cross-service flag consistency Risk: Incompatible checkout behavior Impact: Prevent payment/order failures Owner: Payments Team Validation: ON/OFF compatibility matrix Recovery: Disable V2 2. Implement emergency kill switch Risk: Delayed emergency response Impact: Faster containment Owner: Payments Team Validation: Production-safe kill-switch drill Recovery: Return to legacy checkout 3. Test flag-service outage Risk: Unknown fallback behavior Impact: Validate resilience Owner: Platform Team Validation: Controlled failure test --- πŸš€ Short Term Add feature-specific alerts. Add partial-rollout integration tests. Add configuration propagation tests. Define measurable promotion criteria. Establish rollout dashboard. --- πŸ—οΈ Medium Term Simplify cross-service flag evaluation. Document dependencies. Define retirement criteria. Remove unnecessary legacy branches after 100% rollout. --- 🧹 Long Term Automate: Flag creation β†’ Ownership β†’ Expiration β†’ Usage detection β†’ Rollout monitoring β†’ Stale detection β†’ Retirement --- FINAL AUDIT RESULT Flag: checkout_v2_enabled Overall Risk: πŸ”΄ HIGH Current Classification: 🟑 Transitional Stale: No Orphaned: No Default: 🟑 Acceptable with compatibility validation Kill Switch: πŸ”΄ Insufficient Rollout: 🟠 Needs stronger safeguards Monitoring: 🟠 Incomplete Testing: πŸ”΄ Insufficient Cross-Service Consistency: πŸ”΄ Critical issue Recommended Action: DO NOT increase from 10% β†’ 25% yet. First resolve cross-service evaluation consistency, validate outage/fallback behavior, implement a reliable emergency kill switch, and complete the critical flag-state test matrix. After those controls pass, resume progressive rollout with measurable promotion and rollback criteria.
GPT

Feature Flag Rollout Safety Auditor

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Tested icon
Guide icon
4 examples icon
Free credits icon
Poorly managed feature flags can silently expose unfinished features, create conflicting behavior, and turn gradual releases into production risks. 🚩 Detect stale & abandoned flags βš”οΈ Find conflicting flag combinations πŸ›‘ Identify missing kill switches βš™οΈ Detect unsafe defaults & fallback behavior 🎯 Audit rollout conditions and targeting logic πŸ§ͺ Generate automated flag/rollout test scenarios πŸš€ Design safer progressive rollouts 🧹 Create a practical flag cleanup plan Turn feature-flag complex
...more
Added over 1 month ago
Report
Browse Marketplace