operations
Installation
SKILL.md
Operations
Purpose
Handle DevOps, CI/CD, containers, Kubernetes, reliability, threat modeling, deployment safety, and operational risk with explicit safeguards.
Workflow
- MUST define the system boundary, change surface, and operational risk; if scope is unclear, stop until confirmed.
- MUST identify delivery, security, and runtime failure modes.
- MUST design the safest plan for build, release, runtime, and rollback.
- MUST verify reproducibility, least privilege, and observability needs.
- MUST deliver the plan with checks, rollback, and security notes. Each destructive step MUST carry its own explicit human approval; approval for another step or the word production MUST NOT substitute for it.
- MUST stop with an explicit
BLOCKED/ABORTrepresentation when prerequisites are absent; do not present executable steps after the abort. - MUST preserve the production artifact before destructive work and tie rollback to its exact namespace, cluster/context, and environment. Rollback MUST include a recovery check.
Output Contract
Default: