deployment-procedures

Deliver a structured framework for planning fail-safe software deployments with phased execution and rollback options.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/BeastAyyG/Campus-Cupids --skill deployment-procedures-beastayyg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-procedures
Source: https://github.com/BeastAyyG/Campus-Cupids/tree/main/.agent_backup/skills/deployment-procedures
Command: npx skills add https://github.com/BeastAyyG/Campus-Cupids --skill deployment-procedures-beastayyg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides deployment principles, practical guidance, and decision-making criteria to plan and execute safe production releases.

Core Features & Use Cases

  • Platform selection and decision trees for choosing deployment methods across environments (static sites, web apps, microservices, and serverless)
  • Pre-deployment principles and checks to ensure quality, backups, and readiness
  • Deployment workflow: Prepare, Backup, Deploy, Verify, Confirm or Rollback
  • Post-deployment verification: health checks, logs review, and critical user flows
  • Rollback strategies by platform plus general guardrails and communication
  • Zero-downtime strategies: Rolling, Blue-Green, Canary, and risk-based selection
  • Emergency procedures, investigation order, and rapid issue triage
  • Anti-patterns to avoid and best-practice recommendations
  • Comprehensive decision checklist and guidance for production readiness
  • Practical rules: small, frequent deploys, feature flags, automation, and documentation

Quick Start

Review the five-phase deployment process and implement backup, canary, and rollback plans before any production release.

Frequently Asked Questions about deployment-procedures

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

FAQPage Schema
What is the safest way to deploy to production across different platforms like microservices and static sites?

Safe production deployment uses a five-phase workflow—Prepare, Backup, Deploy, Verify, Confirm or Rollback—codified with decision trees for platform selection to ensure predictable releases across static sites, web apps, microservices, and serverless environments.

How do I choose between rolling, blue-green, and canary deployment strategies?

Choosing a deployment strategy requires risk-based selection criteria: rolling updates gradually replace instances, blue-green maintains two identical environments, and canary releases route a subset of traffic to new code to minimize downtime and limit blast radius.

What pre-deployment checks should I perform before a production release?

Pre-deployment checks must verify quality gates, confirm database backups are complete, and ensure environment readiness before executing the rollout, applying codified principles to prevent unsafe production releases.

How do I execute a rollback when a production deployment fails?

A production rollback follows platform-specific strategies and general guardrails, utilizing emergency procedures and a defined investigation order to rapidly triage issues and restore the previous stable state.

What post-deployment verification steps are needed after a production rollout?

Post-deployment verification involves running health checks, reviewing application logs, and testing critical user flows to confirm the release is functioning correctly before finalizing the deployment.

What are common deployment anti-patterns to avoid during CI/CD automation?

Deployment anti-patterns include large infrequent releases, manual verification bottlenecks, and missing rollback plans, which are countered by best practices like small frequent deploys, feature flags, and automated workflows.