What problem does it solve? It prevents configuration drift and failed deployments in an ArgoCD-managed Kubernetes lab by defining exactly which git paths ArgoCD owns, how sync and self-heal behave, and how to verify changes actually reached the live cluster before running workflows. ## Core Features & Use Cases - Application ownership map: Documents which ArgoCD Applications manage which git paths (workflow-templates, manifests, bootstrap) so new files land in the right place. - Sync troubleshooting: Diagnoses OutOfSync states, repo-specific reconciliation stalls, Server-Side Apply pitfalls, and the WorkflowTemplate snapshot race condition. - Verification protocol: Enforces a four-step check (git push, ArgoCD sync, live template inspection, then workflow submission) before declaring a fix deployed. - Use Case: You edited a WorkflowTemplate, pushed to main, but the cluster still runs the old version. This Skill walks you through forcing a hard refresh, confirming the live template content, and only then submitting a new workflow. ## Quick Start Ask the assistant to check whether my ArgoCD Applications are synced and why my pushed WorkflowTemplate change is not live in the cluster.