deployment-procedures

Guide engineering teams through structured software deployment procedures and rollback strategies.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill deployment-procedures-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-procedures
Source: https://github.com/oalansilva/crypto/tree/main/.agent/skills/deployment-procedures
Command: npx skills add https://github.com/oalansilva/crypto --skill deployment-procedures-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production deployment principles and decision-making to reduce risk in production releases, emphasizing thinking over scripted steps.

Core Features & Use Cases

  • Platform-agnostic deployment decision framework (static sites to microservices)
  • Pre-deployment verification categories (code quality, build, environment, safety)
  • Stepwise deployment lifecycle (Prepare, Backup, Deploy, Verify, Confirm/Rollback)
  • Rollback and emergency procedures with structured guidance
  • Zero-downtime strategies and safety checks
  • Documentation and post-mortem emphasis

Quick Start

Plan a release by selecting platform, completing pre-deployment checks, and documenting rollback steps before deploying.

Frequently Asked Questions about deployment-procedures

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

FAQPage Schema
How do I ensure safe production deployment across different platform architectures?

Zero-downtime deployment strategies require structured safety checks during the deployment lifecycle. You prepare and backup the environment, deploy incrementally, verify stability, and confirm success or trigger a rollback to maintain service availability.

What are the essential pre-deployment verification checks before releasing to production?

A deployment rollback strategy defines emergency procedures and triggers to revert software to a previous stable state. It requires documenting rollback steps before deploying and executing them immediately when verification fails or monitoring detects critical issues.

How do I plan a release with proper deployment procedures and rollback steps?

Post-deployment monitoring confirms software stability by tracking verification metrics after release. It defines rollback triggers and emergency procedures to detect issues early, ensuring predictable releases and enabling structured post-mortem documentation if failures occur.

Can I use this deployment decision framework for both static sites and microservices?

When a production deployment fails, trigger rollback procedures immediately if verification checks fail or monitoring detects critical issues. Structured emergency procedures defined before deployment guide the safe reversion to a stable state.