Perform a broad infrastructure and DevOps audit as a senior platform engineer, across reliability, security, cost, observability, and operability, then produce a prioritized, evidence-based findings table and self-contained remediation plans for other agents to execute. Strictly read-only — never applies changes. Use when asked to audit infrastructure, assess DevOps maturity, do a general health check across a repo or environment, or when the specific problem area is unknown and you need to survey everything first.
Identify cloud cost optimization opportunities as a senior FinOps/cloud engineer across compute, storage, networking, and managed services, then produce a prioritized, evidence-based findings table and self-contained remediation plans that cut waste without hurting reliability. Strictly read-only — never resizes, deletes, or modifies resources. Use when asked to reduce cloud spend, find waste, right-size infrastructure, or review cost efficiency of IaC or a live account.
Review Dockerfiles, container images, and Compose files as a senior container engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans covering image size, build speed, security, and correctness. Strictly read-only — inspects and scans only, never builds-and-pushes or edits. Use when asked to review Dockerfiles, container build setups, image layering, or container security and best practices.
Investigate a production incident as a senior SRE and produce a hypothesis-driven, evidence-logged investigation document plus recommended (never auto-applied) mitigations and durable follow-up plans. Strictly read-only — runs diagnostic and read-only commands only, never restarts, scales, rolls back, or changes anything itself. Use when asked to investigate an outage, degradation, error spike, latency regression, failed deploy, or any "why is production broken" question, or to run a blameless post-incident analysis.
Review Kubernetes manifests, Helm charts, Kustomize overlays, and live workloads as a senior Kubernetes engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans. Strictly read-only — never applies, scales, deletes, or patches anything. Use when asked to review Kubernetes YAML, Helm charts, or cluster workloads for reliability, security, resource management, or best-practice compliance.
Review monitoring, metrics, logging, tracing, dashboards, and alerting as a senior SRE, then produce a prioritized, evidence-based findings table and self-contained remediation plans that close observability gaps and reduce alert noise. Strictly read-only — never edits dashboards, alert rules, or config. Use when asked to review observability posture, assess whether incidents would be detected, evaluate SLOs/alerts, or fix noisy or missing monitoring.
Review CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, etc.) as a senior release engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans covering reliability, speed, security, and correctness. Strictly read-only — never triggers, cancels, or edits pipelines. Use when asked to review CI/CD configuration for flakiness, slow builds, insecure secrets handling, missing gates, or supply-chain risk.
Validate production deployment readiness as a senior release manager/SRE by checking whether a service or release meets reliability, security, observability, rollback, and operational bars before it ships, then produce a go/no-go assessment with an evidence-based gap list and self-contained remediation plans for blockers. Strictly read-only — never deploys, promotes, or changes anything. Use when asked whether something is ready to go to production, to run a pre-launch/pre-deploy checklist, or to gate a release.