Deployment Pipeline Design workflow skill. Use this skill when the user needs Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Deployment Pipeline Design workflow skill. Use this skill when the user needs Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/deployment-pipeline-design from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses metadata.json plus ORIGIN.md as the provenance anchor for review.
Deployment Pipeline Design Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Purpose, Pipeline Stages, Approval Gate Patterns, Deployment Strategies, Pipeline Orchestration, Pipeline Best Practices.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
The task is unrelated to deployment pipeline design
You need a different domain or tool outside this scope
Design CI/CD architecture
Implement deployment gates
Configure multi-environment pipelines
Establish deployment best practices
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Imported Workflow Notes
Imported: Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Imported: Purpose
Design robust, secure deployment pipelines that balance speed with safety through proper stage organization and approval workflows.
Examples
Example 1: Ask for the upstream workflow directly
Use @deployment-pipeline-design to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @deployment-pipeline-design against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @deployment-pipeline-design for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @deployment-pipeline-design using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/deployment-pipeline-design, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@conductor-validator - Use when the work is better handled by that native specialization after this imported skill establishes context.
@confluence-automation - Use when the work is better handled by that native specialization after this imported skill establishes context.
@content-creator - Use when the work is better handled by that native specialization after this imported skill establishes context.
@content-marketer - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
# Blue (current)kubectlapply-fblue-deployment.yamlkubectllabelservicemy-appversion=blue# Green (new)kubectlapply-fgreen-deployment.yaml# Test green environmentkubectllabelservicemy-appversion=green# Rollback if neededkubectllabelservicemy-appversion=blue
Parallel execution - Run independent jobs concurrently
Caching - Cache dependencies between runs
Artifact management - Store build artifacts
Environment parity - Keep environments consistent
Secrets management - Use secret stores (Vault, etc.)
Deployment windows - Schedule deployments appropriately
Monitoring integration - Track deployment metrics
Rollback automation - Auto-rollback on failures
Documentation - Document pipeline stages
Imported: Rollback Strategies
Automated Rollback
deploy-and-verify:steps:-name:Deploynewversionrun:kubectlapply-fk8s/-name:Waitforrolloutrun:kubectlrolloutstatusdeployment/my-app-name:Healthcheckid:healthrun:|
for i in {1..10}; do
if curl -sf https://app.example.com/health; then
exit 0
fi
sleep 10
done
exit 1
-name:Rollbackonfailureif:failure()run:kubectlrolloutundodeployment/my-app
Manual Rollback
# List revision history
kubectl rollout history deployment/my-app
# Rollback to previous version
kubectl rollout undo deployment/my-app
# Rollback to specific revision
kubectl rollout undo deployment/my-app --to-revision=3
Imported: Monitoring and Metrics
Key Pipeline Metrics
Deployment Frequency - How often deployments occur
Lead Time - Time from commit to production
Change Failure Rate - Percentage of failed deployments
Mean Time to Recovery (MTTR) - Time to recover from failure
Pipeline Success Rate - Percentage of successful runs
Average Pipeline Duration - Time to complete pipeline
Integration with Monitoring
-name:Post-deploymentverificationrun:|
# Wait for metrics stabilization
sleep 60
# Check error rateERROR_RATE=$(curl-s"$PROMETHEUS_URL/api/v1/query?query=rate(http_errors_total[5m])"|jq'.data.result[0].value[1]')if(($(echo"$ERROR_RATE > 0.01"|bc-l)));thenecho"Error rate too high: $ERROR_RATE"exit1fi
Imported: Limitations
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.
