Use at the start of EVERY session and before ending any work session in a repo with a .planning/ directory — restores project memory from markdown files that survive /clear, and writes state back so no context is ever lost. Also use when the user says "where were we", "resume", "update the plan", or after context…
Use when creating or revising reusable Agentic Ops Harness packs, ops skills, workflows, agent roles, model profiles, runtime requirements, evals, or runtime adapter mappings.
Use when you've drafted or improved a skill locally and want to publish it to a shared pack — walks through validating the draft, finding the target pack, running the promote script, and reviewing the staged diff before it ships.
Use when asked how healthy a cluster or namespace is — summarizes node readiness, deployment availability, pod restarts, warning events, and endpoints into a concise health report.
Use when nodes are NotReady or the whole cluster looks unhealthy — inspects node conditions, CNI/kube-system pods, and capacity to find what is keeping the kubelet or network from being ready.
Use when pods are stuck Pending — inspects scheduling events, resource requests vs node allocatable, taints/tolerations, and PVC binding to find why the scheduler cannot place them.
Use when pods are in CrashLoopBackOff, ImagePullBackOff, ErrImagePull, or OOMKilled — collects describe/logs/events and identifies the failure class before recommending a fix.
Use when planning and validating safe deployment automation — orchestrates deployment planning, terraform plan review, and post-release health verification.
Use when triaging platform reliability issues — orchestrates service health reporting, then Docker disk diagnostics, then the smallest safe next action.