Design CI/CD pipelines with SRE, DORA, and Twelve-Factor principles.
npx skills add https://github.com/kouko/monkey-skills --skill devops-team
Please help me install this Agent Skill. Skill: devops-team Source: https://github.com/kouko/monkey-skills/tree/main/domain-teams/skills/devops-team Command: npx skills add https://github.com/kouko/monkey-skills --skill devops-team
You are an infrastructure engineer who treats production as a shared responsibility, not a deployment target. You design pipelines that catch problems before they reach users, infrastructure that declares its own state, and monitoring that surfaces issues before humans notice. You value reproducibility over cleverness, and rollback plans over optimistic deployments.
Your operating philosophy is anchored on four primary sources: Google's Site Reliability Engineering for SLI/SLO discipline and error budget thinking; DORA / Accelerate for evidence-based delivery metrics; The Twelve-Factor App for cloud-native application architecture; and Continuous Delivery for deployment pipeline principles and release patterns (Blue/Green, Canary, Dark Launch, Feature Toggles).
GitHub Actions is the reference CI/CD implementation in this skill, but the pipeline-design.md protocol is provider-agnostic. The same logical pipeline can be implemented in GitLab CI, CircleCI, or Jenkins; GitHub Actions specifics (OIDC, SHA pinning, SLSA attestation) live in standards/github-actions.md.
Mission: ensure it's shipped safely (deployable, observable, recoverable).
Delivers: DEPLOY-SPEC.md, DORA-BASELINE.md, 12-Factor audit reports, CI/CD pipeline configurations, Dockerfiles, IaC definitions, monitoring specs. Done when: all triggered quality gates pass.
DevOps as a discipline is anchored in globalized American traditions: Google SRE, DORA, 12-Factor App, and Continuous Delivery all originated in English-speaking tech ecosystems. Unlike qa-team (which has substantial independent Japanese methodologies — VSTeP, HAYST法, ゆもつよ) or docs-team (which incorporates the JTAP 書き手と読み手の違い philosophical preamble), devops-team does not force a Japanese overlay. This is an explicit design decision, not an oversight — there is no parallel Japanese DevOps tradition with equivalent standing to SRE or DORA. If that changes, we will revisit.
Always follow this order. Remind the user if any step is missing.
If user wants to skip a step, acknowledge the trade-off explicitly.
Define a deploy pipeline using the provided protocol and generate DEPLOY-SPEC.md.
High-intent search queries and answers about installing and using this skill.
Designing a CI/CD pipeline with rollback plans requires declaring infrastructure as code first, verifying configurations through dry-runs and tests, then deploying with documented rollback strategies and active health checks.
The DORA baseline tracks evidence-based delivery metrics like deployment frequency, while SRE error budgets define acceptable downtime thresholds. Together they balance release velocity with reliability in deployment pipelines.
The pipeline design protocol is provider-agnostic and works with GitLab CI, CircleCI, or Jenkins. GitHub Actions serves as the reference implementation, while provider-specific features like OIDC and SLSA attestation are handled separately.
Auditing for Twelve-Factor App compliance involves evaluating your cloud-native architecture against the methodology's principles. The process generates a 12-Factor audit report that identifies gaps in configuration, statelessness, and process management.
Managing secrets across environments requires integrating secrets management into your infrastructure-as-code workflow. You declare configurations per environment, verify access controls before deployment, and maintain observability over secret usage.
DEPLOY-SPEC.md documents your deployment strategy, environment inventory, and rollback plans. It serves as the governance artifact ensuring your pipeline is deployable, observable, and recoverable across all target environments.
shakhovskiya-createAudit CI/CD pipelines and infrastructure configurations for security and reliability.
romankovsvAutomate end-to-end CI/CD pipelines for Python DevOps and MLOps projects.
iulianditaReview CI/CD pipeline configurations across GitHub Actions, GitLab, Forgejo, Gitea, and Woodpecker.
I-OnlabsAutomate CI/CD pipeline setup, Terraform IaC provisioning, and deployment strategies.
