Back to catalog / Developer tools
Deployment pipeline design: define progressive rollout and rollback gates
Organize build, security checks, promotion, observation, and approvals into an auditable release flow.
Skills
Confirm application type, platform, environment topology, tolerated downtime, and rollback SLO. Define stage dependencies and parallel checks for tests, SAST/DAST/SCA, artifact signing, and manual approval. Choose rolling, canary, or blue-green and specify promotion thresholds such as error rate/latency, observation duration, and automatic stop conditions at each traffic step. Document rollback and data-migration compatibility, and verify signals exist. Edit pipeline files only; production triggers, threshold changes, or environment deployment require user approval.
Permissions
Prerequisites
- For multi-stage CI/CD, quality gates, canary/blue-green rollout, and rollback thresholds.
- Needs target, environment topology, downtime/rollback SLOs, scans, and monitoring.
Permissions
- May edit pipeline/release config and traffic-shift/rollback rules.
- Pipeline can deploy production; do not trigger releases or alter gates without approval.
Limitations
Define success metrics, observation windows, stop conditions, and approvals per stage; validate rollback and irreversible data changes.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/cicd-automation/skills/deployment-pipeline-design/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Pipeline configuration · Deployment metrics · Health probes
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief