deployment-procedures

Coordinate production deployments with five-phase workflows and rollback planning.

Updated Mar 18, 2026

Search Tags:#deployment #rollback #verification #ci-cd #platform-selection #production-release

Ready to run

npx skills add https://github.com/raccioly/coach-gravity --skill deployment-procedures-raccioly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployment-procedures
Source: https://github.com/raccioly/coach-gravity/tree/main/content/starter-kit/skills/deployment-procedures
Command: npx skills add https://github.com/raccioly/coach-gravity --skill deployment-procedures-raccioly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployment decision-making for safe, controlled software releases.

Core Features & Use Cases

principled platform selection
phase-based deployment workflows
rollback planning and post-deploy verification
guardrails for safe automation and human-in-the-loop decisions

Quick Start

Describe your deployment goal and platform, then apply the 5-phase process (Prepare, Backup, Deploy, Verify, Confirm or Rollback) to execute a safe 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 execute a production release with rollback readiness?▼

A safe production release coordinates deployments by balancing speed, risk, and rollback readiness. It enforces concrete checks, backout plans, and monitoring criteria while providing guardrails to prevent unsafe releases across static sites or microservices.

How do I plan a deployment workflow that includes post-deploy verification?▼

A deployment workflow with post-deploy verification follows a five-phase process: Prepare, Backup, Deploy, Verify, and Confirm or Rollback. This workflow establishes guardrails for safe automation and human-in-the-loop decisions to ensure monitoring criteria are met.

Does this deployment process work for both static sites and microservices?▼

Yes, this deployment process is applicable to platforms ranging from static sites to microservices. It provides principled platform selection and phase-based deployment workflows, enforcing rollback planning and post-deploy verification across different architectures.

What are the guardrails for safe automation during a CI-CD production release?▼

Guardrails for safe automation during a production release include enforcing concrete checks, backout plans, and monitoring criteria. The deployment workflow balances automation with human-in-the-loop decisions to prevent unsafe releases and maintain rollback readiness.

When should I trigger a rollback during a production deployment?▼

You should trigger a rollback during the Verify phase if post-deploy monitoring criteria fail. The deployment workflow mandates rollback readiness through pre-planned backout procedures, ensuring unsafe releases are safely reverted to maintain production stability.