deployment-procedures

Plan safe production deployments by evaluating build health, environment readiness, and backups before release. Choose a platform-aware zero-downtime strategy, then monitor a post-release verification window to validate system health.

Roll back a production release when post-deployment health validation fails or monitoring indicates service degradation. The skill supports fast rollback decisions and emergency triage to restore service quickly during an incident.

Pre-deployment checks require verifying build health, environment readiness, backup availability, and monitoring systems. These checks ensure release readiness and establish a clear recovery path before applying any production changes.

Yes, the deployment planning approach supports platform-aware choices for serverless systems, container orchestration platforms, static sites, and web apps. It tailors release workflows and rollback decisions to your specific hosting environment.

The best way to verify a release is by monitoring a defined post-release validation window. Check health endpoints, monitor system metrics, and confirm backup readiness to ensure the deployment stabilizes without service degradation.

Handle deployment emergencies by executing fast rollback decisions and emergency triage procedures. Validate monitoring alerts, revert to the last known good state, and confirm system health restoration through post-rollback verification.