domains / families / devops / deployment-pipeline-design

deployment-pipeline-design

combined

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices. Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.

When to use

• Design robust, secure deployment pipelines that balance speed with safety through proper stage organization and approval workflows.
• Design CI/CD architecture
• Implement deployment gates
• Configure multi-environment pipelines
• Establish deployment best practices
• Implement progressive delivery

When not to use

• The task is unrelated to deployment pipeline design
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same skeleton (stages, approval patterns, deployment strategies, best practices), but they diverge on material steps and constraints. The antigravity copy includes a full multi-stage GitHub Actions orchestration example and a concrete Azure Pipelines multi-approver YAML, while the agentic-awesome copy replaces the Azure YAML with a policy/verification constraint, changes the blue-green kubectl commands from label to patch, adds a multi-stage implementation contract (immutable artifact digest, scoped credentials, observation window), and adds a rollback section. Crowning one copy would hide the other's real alternative steps and constraints.