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,810
Example input
[RELEASE_SCOPE_AND_CODE_CHANGES]: E-commerce API releasing v2.8.0. Changes: checkout service, order API, payment retry logic. Added idempotency handling for payment requests. Modified order status transitions. [TESTS_COVERAGE_AND_TEST_RESULTS]: Unit tests: 91% coverage. Integration tests: 84% passing. E2E checkout tests: 12/12 passing. No dedicated payment-provider timeout tests. No concurrent duplicate-payment test. [CONFIGURATION_AND_ENVIRONMENT_CHANGES]: New PAYMENT_RETRY_LIMIT environment variable. New feature flag: enable_payment_retry. Staging uses retry limit 3; production value is not yet confirmed. [ROLLBACK_RECOVERY_AND_DISASTER_PROCEDURES]: Previous application image is available. Application rollback procedure is documented. Database rollback procedure exists but has not been tested. Payment records created by the new version cannot be automatically reverted. [MONITORING_ALERTS_AND_KNOWN_TECHNICAL_RISKS]: Existing monitoring covers HTTP 5xx, latency and CPU. No dedicated payment retry alert. Known risk: payment provider may return delayed responses. No confirmed production baseline for duplicate-payment rate.
Example output
PHASE 1 β€” RELEASE SCOPE RECONSTRUCTION Observed Evidence The release modifies: Checkout service Order API Payment processing logic Order state transitions Payment SDK Database schema Production configuration Feature-flag behavior Blast Radius High. The release touches the payment path and order state management. A failure could affect: Checkout completion Payment authorization Duplicate charges Order creation Order status accuracy Customer refunds/support workload Unknowns Exact production value of PAYMENT_RETRY_LIMIT Production behavior of payment SDK 5.1 Actual duplicate-payment baseline Whether rollback has been tested against production-like data Phase 1 Assessment: 🟠 High Risk --- PHASE 2 β€” CODE CHANGE RISK ANALYSIS Change Risk Reason Payment retry logic πŸ”΄ Critical Can create duplicate payment attempts Idempotency handling πŸ”΄ Critical Directly affects transaction safety Order status transitions 🟠 High Incorrect state can create business/data inconsistencies Checkout API changes 🟠 High Customer-facing critical workflow Payment SDK upgrade 🟠 High External behavior may change General checkout changes 🟑 Medium Limited evidence of regression risk Highest-Risk Area Payment retry + delayed payment-provider responses. Example failure: 1. Payment request is sent. 2. Provider processes payment. 3. Response is delayed. 4. Application assumes timeout. 5. Retry starts. 6. Idempotency mechanism fails or is incorrectly configured. 7. Customer is charged twice. Phase 2 Assessment: πŸ”΄ Critical payment-path risk --- PHASE 3 β€” TEST COVERAGE GAP AUDIT The reported 91% unit coverage is not sufficient evidence of release safety. Existing Validation Unit coverage: 91% Integration: 84% E2E checkout: 12/12 passing Missing Critical Tests Payment-provider timeout Delayed payment response Duplicate payment request Concurrent retry Idempotency-key reuse Provider response arriving after retry Partial payment failure Payment succeeds but order update fails Application restart during payment processing Database migration + old application compatibility Critical Missing Scenario Request A ↓ Payment provider receives payment ↓ Response delayed ↓ Application timeout ↓ Retry Request B ↓ Provider receives B ↓ Duplicate charge? This scenario must be explicitly tested. Phase 3 Assessment: πŸ”΄ Release blocker --- PHASE 4 β€” CONFIGURATION & ENVIRONMENT AUDIT Finding PAYMENT_RETRY_LIMIT exists, but its production value is not confirmed. This creates a production-only risk. For example: Staging = 3 retries Production = unknown An unexpected production value could dramatically increase payment attempts. Feature Flag enable_payment_retry is initially disabled. This is a positive risk-control mechanism. However, the team must verify: Flag default = OFF Flag can be changed independently Flag can be immediately disabled Flag behavior is tested in production-like conditions Phase 4 Assessment: 🟠 High Risk --- PHASE 5 β€” DEPENDENCY & DATABASE RISK AUDIT Dependency Payment SDK: 4.7 β†’ 5.1 Required Validation Breaking API changes Retry behavior changes Timeout behavior Error-code changes Authentication behavior Runtime compatibility No evidence has been provided for these validations. Dependency Risk: 🟠 High Database New: payment_attempts Migration is reportedly backward-compatible. Positive. But: Rollback migration has not been tested. More importantly, payment records created by the new application may remain after application rollback. Therefore: Application rollback β‰  complete transaction rollback Database/Data Risk: πŸ”΄ High --- PHASE 6 β€” DEPLOYMENT RISK ANALYSIS Current deployment: DB Migration ↓ Kubernetes Rolling Deployment ↓ Application Startup ↓ Traffic Risk Migration occurs before the new application is deployed. This is acceptable only if: Old application can safely operate with the new schema. New columns/tables do not alter old behavior. Migration does not lock critical tables. Migration failure does not leave an unusable state. Positive Controls Kubernetes rolling deployment Previous image available Feature flag disabled initially Missing Evidence Migration duration Production database size Locking behavior Health-check validation Traffic-shifting strategy Phase 6 Assessment: 🟠 High Risk --- PHASE 7 β€” BACKWARD & FORWARD COMPATIBILITY Application ↔ Database Reported as backward-compatible. Need actual validation against the previous application version. Payment Provider Potential compatibility concern due to SDK upgrade. Mixed Versions During rolling deployment: Old Pods + New Pods ↓ Shared Database ↓ Payment Provider Both versions may process payment requests simultaneously. The idempotency implementation must therefore work across mixed versions. Assessment: 🟠 High Risk --- PHASE 8 β€” FAILURE MODE & BLAST-RADIUS ANALYSIS Failure Impact Detection Recovery Payment retry duplicates charge πŸ”΄ Severe Payment anomaly monitoring Disable retry + investigate/refund SDK breaks payment requests πŸ”΄ Severe Payment failure rate Roll back application Migration causes locking πŸ”΄ Severe DB latency/locks Stop rollout/recovery Order status update fails 🟠 High Error logs/business monitoring Reconciliation Retry configuration incorrect πŸ”΄ Severe Config validation/metrics Disable feature flag Mixed-version incompatibility 🟠 High Integration/production monitoring Stop rollout Most Dangerous Failure Duplicate customer payment. This has both technical and direct financial/customer impact. --- PHASE 9 β€” ROLLBACK READINESS AUDIT Application Rollback Possible. Previous image exists. Database Rollback Not proven safe. Rollback migration has not been tested. Data Rollback Not automatically possible. New payment records may remain. Therefore: > Application rollback is available, but complete release rollback is not yet demonstrated. Assessment: πŸ”΄ Release blocker --- PHASE 10 β€” RECOVERY & INCIDENT READINESS Available Previous artifact Documented rollback Existing monitoring Missing/Unconfirmed Tested DB recovery Payment reconciliation procedure Duplicate-payment incident runbook Clear incident owner Escalation procedure Customer communication procedure Assessment: 🟠 High Risk --- PHASE 11 β€” MONITORING & ALERTING READINESS Current monitoring is insufficient for this release. Required Immediately Metric Warning Critical Action Payment failure rate > baseline + 2Οƒ > baseline + 3Οƒ Investigate/rollback Payment retry rate > expected baseline Unexpected spike Disable retry Duplicate-payment rate Any unexplained increase Confirmed duplicates Disable retry + incident Checkout 5xx Elevated Sustained spike Stop rollout Checkout latency > baseline Major sustained increase Investigate DB latency Elevated Severe degradation Stop deployment Payment-provider errors Elevated Sustained failure Disable feature Missing Critical Metric Payment retry success/failure ratio. This should be available before enabling the feature. --- PHASE 12 β€” POST-DEPLOYMENT VALIDATION Immediate Verify all pods healthy. Verify application startup. Verify database connectivity. Test checkout endpoint. Test payment authorization. Verify feature flag remains OFF. Short Term Monitor 5xx. Monitor checkout latency. Monitor payment failures. Monitor retry activity. Monitor payment-provider errors. Monitor database performance. Business Validation Create test order. Complete payment. Verify exactly one payment transaction. Verify correct order status. Verify payment record. Verify no duplicate transaction. Failure Criterion Any unexplained duplicate charge should trigger immediate rollback/feature disablement. --- PHASE 13 β€” UNRESOLVED TECHNICAL RISK REGISTER Risk Probability Impact Status Duplicate payment during retry Medium πŸ”΄ Severe πŸ”΄ Blocking DB rollback untested Medium πŸ”΄ Severe πŸ”΄ Blocking Production retry limit unknown Medium πŸ”΄ Severe πŸ”΄ Blocking SDK 5.1 behavior insufficiently validated Medium 🟠 High 🟠 High Mixed-version compatibility unverified Medium 🟠 High 🟠 High Payment-specific alerts missing High 🟠 High 🟠 High Recovery/runbook gaps Medium 🟠 High 🟠 High --- PHASE 14 β€” RELEASE READINESS SCORING Dimension Score Code Safety 65/100 Test Readiness 58/100 Configuration Safety 60/100 Dependency Safety 65/100 Deployment Safety 72/100 Data Safety 55/100 Rollback Readiness 45/100 Monitoring Readiness 52/100 Operational Readiness 60/100 Overall 59/100 β€” Insufficient for unrestricted production deployment However, the aggregate score is not the deciding factor. There are critical blockers involving: Payment duplication Database rollback Production configuration Payment-specific monitoring --- PHASE 15 β€” RELEASE GATE & REMEDIATION PLAN πŸ”΄ MUST FIX BEFORE RELEASE 1. Payment Retry Testing Action: Add timeout, delayed-response, concurrent-retry and duplicate-payment tests. Validation: All critical payment failure scenarios pass. Exit Criteria: No duplicate transaction can be produced under tested retry scenarios. 2. Database Rollback Action: Execute rollback migration in a production-like environment. Validation: Confirm application and data remain consistent. Exit Criteria: Documented rollback completes successfully without data corruption. 3. Production Configuration Action: Confirm and validate PAYMENT_RETRY_LIMIT. Exit Criteria: Production value is explicitly reviewed and tested. 4. Payment Monitoring Action: Add payment retry and duplicate-payment monitoring. Exit Criteria: Alerts are tested and actionable before enabling the feature. --- 🟠 SHOULD FIX BEFORE RELEASE Validate SDK 5.1 behavior. Test mixed old/new application versions. Create payment reconciliation runbook. Define incident ownership. Validate migration locking behavior. --- 🟒 CAN FIX AFTER RELEASE Improve dashboard visualization. Expand non-critical regression coverage. Improve technical documentation. --- PHASE 16 β€” FINAL RELEASE READINESS REPORT Executive Summary Release: E-commerce API v2.8.0 Overall Risk: πŸ”΄ High Readiness: 59/100 Biggest Concerns 1. Payment retry can potentially cause duplicate charges. 2. Critical retry failure scenarios are not tested. 3. Production retry configuration is unconfirmed. 4. Database rollback has not been validated. 5. Payment-specific production monitoring is incomplete. --- 🚦 RELEASE GATE The release should not proceed to unrestricted production deployment yet. Before deployment, the team must: 1. Validate duplicate-payment prevention. 2. Test payment timeout/retry scenarios. 3. Confirm production configuration. 4. Test database rollback. 5. Validate SDK upgrade. 6. Add payment-specific monitoring. 7. Validate mixed-version compatibility. 8. Confirm incident/recovery ownership. --- πŸ§ͺ POST-RELEASE VERIFICATION After deployment: Deploy ↓ Verify Pods ↓ Verify DB ↓ Run Checkout Smoke Test ↓ Run Payment Test ↓ Verify Exactly One Transaction ↓ Monitor Payment Errors ↓ Monitor Retry Rate ↓ Monitor Business KPIs ↓ Enable Feature Flag Gradually If payment anomalies appear: Disable Feature Flag ↓ Stop Rollout ↓ Investigate ↓ Rollback Application If Safe ↓ Reconcile Payment/Data State πŸ”΄ FINAL DECISION: NO-GO Evidence-based reason: The release has a high-risk payment-path change, but the most important failure scenarios are not sufficiently tested. In addition, database rollback has not been proven, production retry configuration is unknown, and payment-specific monitoring is incomplete. The previous application artifact can be rolled back, but that alone does not prove that payment data and database state can be safely rolled back. 🎯 Shortest Path to GO Payment failure-path tests β†’ production configuration validation β†’ DB rollback rehearsal β†’ payment monitoring/alerts β†’ mixed-version validation β†’ controlled deployment with feature flag OFF β†’ smoke test β†’ gradual feature activation. Only after those gates pass should the decision be upgraded from πŸ”΄ NO-GO to 🟑 CONDITIONAL GO or 🟒 GO.
GPT

Software Release Readiness 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
A release can pass basic tests and still hide configuration, dependency, deployment, rollback, and monitoring risks that cause production incidents. πŸ” Analyze code changes & affected components πŸ§ͺ Find test coverage and validation gaps βš™οΈ Detect configuration & environment risks πŸ“¦ Assess dependency changes πŸš€ Identify deployment failure risks πŸ”„ Validate rollback readiness πŸ“Š Define production monitoring requirements 🚨 Prioritize unresolved technical risks πŸŸ’πŸ”΄ Deliver a clear Go / Conditiona
...more
Added over 1 month ago
Report
Browse Marketplace