# Plan Safer Production Deployments

Production releases can fail when teams skip preparation, monitoring, or rollback planning. This skill structures deployment decisions around verification, controlled execution, and recovery.

## Install

```bash
npx skillstore add sickn33/deployment-procedures
```

## Metadata

- Status: approved
- Slug: sickn33-deployment-procedures
- Skillstore revision: r2
- Version status: missing
- Tree hash: 0660f5d9dde4d7f2800e3a2946153dbaaf6258ef551364c1990abb972a1e08a4
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/deployment-procedures
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-deployment-procedures
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-deployment-procedures/manifest

## Capabilities

- Compares hosting approaches for static sites, web applications, microservices, and serverless systems.
- Builds pre-deployment checklists covering tests, builds, environment settings, backups, monitoring, and communication.
- Structures releases into preparation, backup, deployment, verification, and confirmation or rollback phases.
- Defines post-deployment checks for service health, errors, user flows, and performance.
- Recommends rollback triggers and method categories for managed platforms, VPS, Docker, and Kubernetes.
- Compares rolling, blue-green, and canary strategies for zero-downtime releases.

## Use Cases

- Prepare a routine release: Create a platform-aware checklist with preparation, backup, deployment, verification, and communication steps.
- Select a rollout strategy: Compare rolling, blue-green, and canary approaches against service risk and rollback needs.
- Define incident recovery gates: Set measurable rollback triggers and organize investigation priorities for a production release.

## Prompt Templates

### Create a deployment checklist

```
Create a deployment checklist for [application] on [platform]. Include preparation, backup, deployment, verification, rollback, monitoring, and team communication.
```

### Choose a rollout strategy

```
Compare rolling, blue-green, and canary deployment for [service]. Recommend one based on [risk], [traffic], [capacity], and [rollback requirement].
```

### Define verification and rollback gates

```
Design post-deployment checks for [critical flows]. Define measurable success thresholds, observation windows, rollback triggers, owners, and communication steps.
```

### Review an end-to-end release plan

```
Review this release plan for [system]: [plan]. Identify missing prerequisites, unsafe assumptions, migration risks, monitoring gaps, and rollback weaknesses. Propose a safer sequence.
```

## Limitations

- Provides general principles rather than commands tailored to a specific provider or repository.
- Does not execute deployments, access infrastructure, modify files, or monitor live systems.
- Cannot verify credentials, environment variables, backups, builds, migrations, or production health.
- Requires platform details, risk tolerance, and success criteria for useful recommendations.

## Best Practices

- Provide the platform, architecture, change scope, maintenance window, and available rollback method.
- Define measurable health, error, flow, and performance thresholds before deployment begins.
- Test backups and rollback procedures before relying on them during an incident.

## Anti Patterns

- Requesting one universal command sequence without describing the platform or application.
- Deploying before tests, backups, monitoring, communication, and rollback ownership are ready.
- Treating a restart as sufficient investigation when service health remains uncertain.

## Security Audit

- Audited at: 2026-07-23T22:04:06.132\+00:00
- Summary: All three static findings are false positives caused by Markdown code fences around text diagrams in SKILL.md. The skill contains deployment guidance but no executable scripts, command invocation logic, prompt injection, credential handling, or exfiltration behavior. No semantic security findings were identified.

## Stats

- Views: 104
- Downloads: 12
- Favorites: 0
- Popularity score: 0