milind-soni Release Readiness
Use this when
A change is approaching merge, deployment, distribution, or a public release.
Process
- Map the release to its acceptance criteria and affected user flows.
- Confirm automated checks and record relevant manual verification.
- Review data changes, compatibility, security, permissions, failure states, and observability.
- Identify remaining uncertainty and classify it by likelihood and impact.
- Confirm rollout order, owner, rollback path, and post-release checks.
- Prepare concise user-facing or maintainer-facing notes where behavior changes.
Output
Return a clear Ready, Ready with conditions, or Not ready decision followed by evidence, open risks, rollout, rollback, monitoring, and communication.
Guardrails
Never infer passing checks that were not run. A green test suite does not replace verifying the important rendered or end-to-end behavior.