# Design Reliable CI/CD Deployment Pipelines

Complex releases can fail without clear stages, gates, and rollback paths. This skill designs structured CI/CD pipelines with progressive delivery and verification controls.

## Install

```bash
npx skillstore add sickn33/deployment-pipeline-design
```

## Metadata

- Status: approved
- Slug: sickn33-deployment-pipeline-design
- Skillstore revision: r2
- Version status: missing
- Tree hash: 0c3cf168b38d8cbd9af2f022a439dc677559e3f762af31f5dc2e016677d70efa
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/deployment-pipeline-design
- 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, network, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-deployment-pipeline-design
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-deployment-pipeline-design/manifest

## Capabilities

- Defines source, build, test, staging, approval, production, verification, and rollback stages.
- Compares rolling, blue-green, canary, and feature flag deployment strategies.
- Provides examples for GitHub Actions, GitLab CI, Azure Pipelines, Kubernetes, and Argo Rollouts.
- Designs manual, delayed, and multi-approver production gates.
- Adds health checks, error-rate validation, notifications, and rollback steps.

## Use Cases

- Standardize service releases: Create a reusable stage model with tests, staging validation, production deployment, health checks, and rollback.
- Add governed production gates: Define approval ownership, required evidence, release timing, and recovery responsibilities before production changes.
- Plan progressive delivery: Compare rollout strategies and choose traffic stages, verification metrics, and failure thresholds for a service.

## Prompt Templates

### Outline a basic pipeline

```
Design a CI/CD pipeline for [application] using [platform], covering build, test, staging, approval, production, verification, and rollback.
```

### Select a deployment strategy

```
Compare rolling, blue-green, and canary deployment for [service], considering traffic, downtime, rollback speed, infrastructure cost, and operational complexity.
```

### Create governed release gates

```
Design approval gates for [environments] with [approvers], evidence requirements, timeouts, audit records, and emergency rollback responsibilities.
```

### Design progressive delivery

```
Create a multi-stage pipeline for [service] with canary weights, health metrics, failure thresholds, notifications, automated rollback, and post-deployment verification.
```

## Limitations

- Provides design guidance and illustrative templates but does not deploy applications.
- Templates require adaptation and security review for each repository, credential model, and infrastructure environment.
- Referenced resource and asset files are not included in this package.
- Does not select platform permissions, secret stores, or monitoring thresholds automatically.

## Best Practices

- Validate every template against the target CI platform and a non-production environment.
- Keep credentials in approved secret stores and grant each pipeline stage minimal permissions.
- Define measurable promotion and rollback criteria before enabling automated production changes.

## Anti Patterns

- Do not deploy to production before required tests and approval evidence are complete.
- Do not treat a single health endpoint as complete release verification.
- Do not copy example commands without reviewing destinations, permissions, timeouts, and failure behavior.

## Security Audit

- Audited at: 2026-07-23T22:00:03.184\+00:00
- Summary: All 37 static findings are false positives caused by Markdown backticks, inert CI examples, placeholder domains, and a literal API\_KEY placeholder. No code executes commands, reads environment secrets, or contacts external services, and no prompt injection or malicious intent was found.

## Stats

- Views: 111
- Downloads: 8
- Favorites: 0
- Popularity score: 0