devops-engineer-job-protocols

Standardize DevOps task execution for infrastructure, CI/CD, and deployment governance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ngmthaq/my-copilot --skill devops-engineer-job-protocols
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-engineer-job-protocols
Source: https://github.com/ngmthaq/my-copilot/tree/main/skills/devops-engineer-job-protocols
Command: npx skills add https://github.com/ngmthaq/my-copilot --skill devops-engineer-job-protocols

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines and protocols for DevOps engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, but focusing on infrastructure, CI/CD, and deployment processes.

Core Features & Use Cases

  • Standardized Task Execution Protocol covering input verification, blast radius analysis, incremental planning, and IaC-driven implementation.
  • Governance and safety mandates: never modify application code, never approve your own output, require technical-leader involvement, and comprehensive documentation.
  • Applies to infrastructure provisioning, deployment automation, environment configuration, and release governance across development, staging, and production.

Quick Start

Read and apply the task execution protocol to the assigned infrastructure task, ensuring all steps are followed before any code changes.

Frequently Asked Questions about devops-engineer-job-protocols

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a standardized DevOps protocol for infrastructure deployment?

A standardized DevOps protocol enforces IaC-driven implementation and non-production validation before executing infrastructure provisioning. It mandates plan and preview steps, blast radius analysis, and comprehensive secret management to ensure safe deployment automation.

How do I execute CI/CD pipeline changes without modifying application code?

To execute CI/CD changes without modifying application code, apply governance mandates that restrict changes to infrastructure and deployment processes. Require technical-leader involvement and thorough documentation while enforcing a strict policy against frontend or backend code modifications.

What's the best way to manage release governance across development, staging, and production environments?

The best way to manage release governance is enforcing standardized task execution protocols across development, staging, and production. Apply blast radius analysis, incremental planning, and IaC-driven implementation to govern environment configuration and release management safely.

Does this deployment governance protocol support infrastructure provisioning tasks?

Yes, this deployment governance protocol directly supports infrastructure provisioning tasks. It applies standardized execution protocols to infrastructure-focused tasks, ensuring secret management and thorough documentation while preventing any frontend or backend application code changes.

Why should I not approve my own deployment automation output?

You should not approve your own deployment automation output due to strict governance and safety mandates. Requiring technical-leader involvement and preventing self-approval ensures infrastructure changes undergo proper review, maintaining release governance and code-only change compliance.

When do I need to perform a blast radius analysis for environment configuration?

You need to perform a blast radius analysis for environment configuration during the input verification phase of any infrastructure task. It is required before incremental planning and IaC-driven implementation to prevent unintended impacts on deployment automation.