Beta to General Availability Readiness Review
Decide if you are ready to launch broadly.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Run a readiness review. Product state and beta results: [BETA_RESULTS]. Open issues: [OPEN_ISSUES]. Support and operations readiness: [OPERATIONS_READINESS]. Launch goals: [LAUNCH_GOALS]. Score readiness on 10 areas (product quality, performance, security, privacy and legal [VERIFY], accessibility, documentation, support, billing, operations and monitoring, go-to-market) from 1 to 5 with evidence and owner. Define a go threshold (no area below 3, no open severity-one issues) and compute the result. Produce a table: Area | Score | Evidence | Gap | Owner | Due. Provide a decision memo: go, go with conditions, or delay, with the reasoning and risks, plus a rollout recommendation (staged percentages) and the metrics that will trigger a rollback. Include a message to stakeholders (120 words). Produce the scorecard first, then a go or delay recommendation with the conditions, and a list of the five open issues that matter most with owner, severity, and the date each must be closed before launch.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.