deployment-procedures

Define and apply safe production deployment workflows with rollback strategies.

Updated Aug 22, 2025

Search Tags:#devops #deployment #rollback #production #verification #operations

Ready to run

npx skills add https://github.com/AnthonyCongHieu/voice_tool --skill deployment-procedures-anthonyconghieu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployment-procedures
Source: https://github.com/AnthonyCongHieu/voice_tool/tree/main/voice_tools_v1/.agent/skills/deployment-procedures
Command: npx skills add https://github.com/AnthonyCongHieu/voice_tool --skill deployment-procedures-anthonyconghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployment is error-prone and risky; teams need principled processes to release safely, with clear rollback plans and verification before and after changes.

Core Features & Use Cases

Platform selection guides across common environments (static sites, web apps, microservices, serverless).
A structured 5-phase deployment workflow (Prepare, Backup, Deploy, Verify, Confirm or Rollback).
Verification categories (Code Quality, Build, Environment, Safety) and a comprehensive pre-deployment checklist.
Rollback principles and platform-specific rollback methods to minimize downtime.
Zero-downtime deployment strategies (Rolling, Blue-Green, Canary) and emergency procedures for service outages.
Anti-patterns to avoid and decision checklists to streamline releases.

Quick Start

Learn to apply deployment thinking by stepping through a safe-release procedure for your next release.

Frequently Asked Questions about deployment-procedures

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

FAQPage Schema

What is a safe production deployment workflow?▼

A safe production deployment workflow minimizes release risk through a structured five-phase process: Prepare, Backup, Deploy, Verify, and Confirm or Rollback. It enforces testing, monitoring, and rollback readiness to ensure reliable production changes.

How do I plan a rollback strategy for a failed release?▼

Plan a rollback strategy by defining platform-specific rollback methods and emergency procedures for service outages before deploying. Establishing these rollback principles ensures you can quickly revert changes and minimize downtime if post-deployment validation fails.

What are the best zero-downtime deployment strategies for web apps?▼

The best zero-downtime deployment strategies are Rolling, Blue-Green, and Canary deployments. These approaches update services without interrupting users by gradually shifting traffic or switching between identical production environments.

What should be on a pre-deployment verification checklist?▼

A pre-deployment verification checklist should cover Code Quality, Build, Environment, and Safety categories. It specifies requirements for testing, backups, and monitoring to verify automated tooling and human decision-making readiness before releasing.

Does this deployment process work for serverless and microservices environments?▼

Yes, the deployment process works for serverless and microservices environments using platform-agnostic workflows. It provides platform selection guides and specifies rollback methods across common environments including static sites, web apps, microservices, and serverless.

What are common deployment anti-patterns to avoid during a release?▼

Common deployment anti-patterns to avoid include skipping backups, neglecting post-deployment validation, and lacking a rollback plan. Applying decision checklists streamlines releases and prevents these risky practices that cause service outages.