devops-deployer
Comprehensive DevOps and deployment workflow that orchestrates infrastructure automation, CI/CD pipelines, container orchestration, and cloud deployment. Handles everything from infrastructure as code and pipeline setup to monitoring, scaling, and disaster recovery.
What this skill does
# DevOps Deployer - Complete DevOps and Deployment Workflow ## Overview This skill provides end-to-end DevOps and deployment services by orchestrating DevOps architects, infrastructure specialists, and automation experts. It transforms deployment requirements into production-ready infrastructure with comprehensive automation, monitoring, and operational excellence. **Key Capabilities:** - 🏗️ **Infrastructure as Code** - Automated infrastructure provisioning and management - 🔄 **CI/CD Pipeline Automation** - Complete continuous integration and deployment workflows - ☸️ **Container Orchestration** - Docker, Kubernetes, and microservice deployment - 📊 **Monitoring & Observability** - Comprehensive monitoring, logging, and alerting systems - 🛡️ **Reliability & Scaling** - High availability, auto-scaling, and disaster recovery ## When to Use This Skill **Perfect for:** - CI/CD pipeline design and implementation - Infrastructure as code and cloud automation - Container orchestration and microservice deployment - Monitoring, logging, and observability setup - Disaster recovery and high availability implementation - DevOps process optimization and automation **Triggers:** - "Set up CI/CD pipeline for [application]" - "Implement infrastructure as code for [environment]" - "Deploy containerized application with Kubernetes" - "Create monitoring and observability system" - "Implement disaster recovery and backup strategies" ## DevOps Expert Panel ### **DevOps Architect** (DevOps Strategy & Architecture) - **Focus**: DevOps strategy, pipeline architecture, automation design - **Techniques**: CI/CD patterns, infrastructure as code, DevOps maturity models - **Considerations**: Team collaboration, automation efficiency, reliability ### **Infrastructure Specialist** (Cloud & Infrastructure) - **Focus**: Cloud infrastructure, networking, security, and scaling - **Techniques**: AWS, Azure, GCP, Terraform, CloudFormation, networking - **Considerations**: Cost optimization, security, compliance, scalability ### **Container Orchestration Expert** (Containers & Kubernetes) - **Focus**: Docker, Kubernetes, service mesh, container security - **Techniques**: Container orchestration, microservices, service discovery - **Considerations**: Resource optimization, security, monitoring, scaling ### **Automation Engineer** (Pipeline & Automation) - **Focus**: CI/CD pipelines, automation scripts, testing automation - **Techniques**: Jenkins, GitLab CI, GitHub Actions, Ansible, scripting - **Considerations**: Pipeline efficiency, reliability, security, maintainability ### **Monitoring Specialist** (Observability & Reliability) - **Focus**: Monitoring, logging, alerting, performance optimization - **Techniques**: Prometheus, Grafana, ELK stack, APM tools, SRE practices - **Considerations**: System reliability, performance visibility, incident response ## DevOps Implementation Workflow ### Phase 1: DevOps Requirements Analysis & Strategy **Use when**: Starting DevOps implementation or process improvement **Tools Used:** ```bash /sc:analyze devops-requirements DevOps Architect: DevOps maturity assessment and strategy Infrastructure Specialist: infrastructure requirements and constraints Automation Engineer: automation opportunities and pipeline needs ``` **Activities:** - Analyze current DevOps maturity and identify improvement areas - Define DevOps goals and success metrics - Assess infrastructure requirements and constraints - Identify automation opportunities and pipeline needs - Plan team training and cultural transformation ### Phase 2: Infrastructure Design & Architecture **Use when**: Designing infrastructure architecture and cloud strategy **Tools Used:** ```bash /sc:design --type infrastructure cloud-architecture Infrastructure Specialist: cloud infrastructure design and optimization DevOps Architect: infrastructure patterns and best practices Monitoring Specialist: monitoring and observability requirements ``` **Activities:** - Design cloud infrastructure architecture and networking - Plan infrastructure as code implementation strategy - Design security and compliance frameworks - Plan monitoring, logging, and observability architecture - Define scaling and high availability strategies ### Phase 3: CI/CD Pipeline Design & Implementation **Use when**: Creating continuous integration and deployment workflows **Tools Used:** ```bash /sc:design --type pipeline cicd-workflow Automation Engineer: CI/CD pipeline design and implementation DevOps Architect: pipeline patterns and best practices Infrastructure Specialist: pipeline infrastructure and environments ``` **Activities:** - Design CI/CD pipeline architecture and workflows - Implement build, test, and deployment automation - Create environment management and promotion strategies - Implement code quality gates and security scanning - Design rollback and recovery procedures ### Phase 4: Container Orchestration & Microservices **Use when**: Implementing containerization and microservice architecture **Tools Used:** ```bash /sc:implement container-orchestration Container Orchestration Expert: Kubernetes setup and configuration Infrastructure Specialist: container infrastructure and networking Monitoring Specialist: container monitoring and observability ``` **Activities:** - Design container architecture and microservice patterns - Implement Kubernetes clusters and configuration - Set up service mesh and inter-service communication - Configure container security and networking - Implement container monitoring and logging ### Phase 5: Monitoring & Observability Implementation **Use when**: Setting up comprehensive monitoring and observability systems **Tools Used:** ```bash /sc:implement monitoring-observability Monitoring Specialist: monitoring stack setup and configuration DevOps Architect: observability strategy and SRE practices Infrastructure Specialist: monitoring infrastructure and data retention ``` **Activities:** - Implement monitoring stack (Prometheus, Grafana, etc.) - Set up centralized logging and log aggregation - Create alerting rules and incident response procedures - Implement distributed tracing and APM - Design monitoring dashboards and reporting ### Phase 6: Reliability & Disaster Recovery **Use when**: Implementing high availability and disaster recovery capabilities **Tools Used:** ```bash /sc:implement disaster-recovery Infrastructure Specialist: backup and recovery implementation DevOps Architect: reliability engineering and SRE practices Monitoring Specialist: reliability monitoring and alerting ``` **Activities:** - Implement backup and disaster recovery procedures - Set up high availability and failover mechanisms - Create disaster recovery testing and validation - Implement incident response and runbook automation - Design reliability metrics and SLO monitoring ## Integration Patterns ### **SuperClaude Command Integration** | Command | Use Case | Output | |---------|---------|--------| | `/sc:design --type infrastructure` | Infrastructure design | Complete infrastructure architecture | | `/sc:implement cicd` | CI/CD pipeline | Production-ready CI/CD workflows | | `/sc:implement kubernetes` | Container orchestration | Kubernetes cluster and configuration | | `/sc:implement monitoring` | Monitoring system | Complete observability stack | | `/sc:implement disaster-recovery` | DR setup | Disaster recovery procedures | ### **Cloud Provider Integration** | Provider | Role | Capabilities | |----------|------|------------| | **AWS** | Cloud infrastructure | Complete AWS infrastructure and services | | **Azure** | Enterprise cloud | Azure-specific services and integration | | **GCP** | Cloud platform | Google Cloud services and optimization | | **Multi-cloud** | Hybrid infrastructure | Multi-cloud strategies and management | ### **MCP Server Integration** | Server | Expertise | Use Case | |--------|----------|---------| | **Sequential** | DevOps reasoning | Complex infra
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.