deployment-procedures

Guide production deployments through a 5-phase process with rollback strategies.

132|22|Updated Dec 18, 2025

Search Tags:#planning #deployment #rollback #verification #risk-management #canary

Ready to run

npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill deployment-procedures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployment-procedures
Source: https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/deployment-procedures
Command: npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill deployment-procedures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid deployment paralysis by providing a principle-based, repeatable framework for safe production deployments.

Core Features & Use Cases

Structured deployment lifecycle: guides decisions for platform selection and deployment methods across static sites, web apps, microservices, serverless, and containers.
Verification & rollback focus: defines pre-deployment checks, backup strategies, health verification, and rollback plans to minimize risk.
Operational governance: follows a clear 5-phase process (Prepare, Backup, Deploy, Verify, Confirm or Rollback) with checklists and scalable templates.

Quick Start

Review the platform landscape and pick a deployment approach aligned with risk tolerance. Apply the 5-phase process to a new release: prepare checks, create backups, deploy with monitoring, verify health, and confirm or rollback.

Frequently Asked Questions about deployment-procedures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I avoid deployment paralysis when releasing to production?▼

Deployment paralysis is solved by following a repeatable 5-phase process: Prepare (pre-deployment checks), Backup (create recovery points), Deploy (execute with monitoring), Verify (health checks), and Confirm or Rollback. This structured framework eliminates decision uncertainty across static sites, web apps, microservices, serverless, and containers.

What should I verify before and after a production deployment?▼

Pre-deployment verification includes code quality checks, successful builds, correct environment variables, and monitoring readiness. Post-deployment verification confirms application health, validates data integrity, and monitors system performance. Both stages are essential to minimize risk and enable confident rollback if needed.

How do I plan a rollback strategy for production releases?▼

Rollback planning defines explicit recovery procedures within the deployment framework, including backup restoration methods, version identification, and health verification steps. Establish rollback triggers and document decision criteria before deployment to enable rapid recovery when issues arise.

Can I use this deployment framework with microservices, containers, and serverless?▼

Yes. The 5-phase process and verification checklists apply across platform types: static sites, web apps, microservices, serverless functions, and container orchestration. Adapt platform-specific deployment methods while maintaining the core framework for consistency and risk management.

What's the best way to select a deployment approach for my platform?▼

Review your platform landscape and risk tolerance, then choose a deployment method aligned with your infrastructure type. The framework guides this decision for static sites, web apps, microservices, serverless, and containers, ensuring your selection matches your operational needs and safety requirements.

Why do I need checklists and templates for deployment procedures?▼

Checklists and templates enforce operational governance by standardizing decisions across code quality, builds, environment configuration, and monitoring. They reduce human error, ensure consistent verification, and make deployment repeatable and scalable across teams and releases.