# Plan: K8s Agent Production Validation

## Goal
Address the identified gaps in k8s agent production readiness:
1. Create a lightweight k8s skill for quick checks (parallel to existing workflow)
2. Validate agents against live cluster with read-only operations

## Context

**Already exists:**
- `/cluster-status` command → `cluster-health-check` workflow (multi-step, 4 agents)
- All k8s agents are defined with proper boundaries and formats

**Gap:** No single-agent skill for ultra-quick status (like `sysadmin-health` for linux).

---

## Phase 1: Create K8s Quick-Status Skill

Create `~/.claude/skills/k8s-quick-status/SKILL.md`

**Purpose:** Lightweight single-agent check (haiku) for instant cluster pulse. Faster than workflow when you just need basics.

**Checks:**
- `kubectl get nodes` - node readiness
- `kubectl get pods -A --field-selector=status.phase!=Running` - unhealthy pods
- `kubectl get events -A --field-selector=type=Warning --sort-by='.lastTimestamp'` - recent warnings
- `argocd app list` - sync status at a glance

**Format:** Match `sysadmin-health` structure exactly (YAML frontmatter + Markdown).

---

## Phase 2: Live Cluster Validation

Run read-only commands to validate connectivity and output quality.

### Test Sequence

| Agent | Commands | Purpose |
|-------|----------|---------|
| k8s-diagnostician | `kubectl get nodes -o wide`<br>`kubectl get pods -A`<br>`kubectl top nodes` | Cluster connectivity |
| prometheus-analyst | `curl localhost:9090/api/v1/query?query=up`<br>`curl localhost:9090/api/v1/alerts` | Metrics access |
| argocd-operator | `argocd app list` | GitOps connectivity |
| git-operator | `git -C <gitops-repo> log --oneline -n 5` | Repo access |

### Success Criteria
- All commands execute without error
- kubectl has valid kubeconfig
- Prometheus is reachable
- ArgoCD CLI is authenticated
- Git repo is accessible

---

## Phase 3: Document Results

Update `~/.claude/state/future-considerations.json` with:
- Validation status per agent
- Any connectivity issues discovered
- Recommendations for fixes

---

## Files to Create/Modify

| File | Action |
|------|--------|
| `~/.claude/skills/k8s-quick-status/SKILL.md` | Create |
| `~/.claude/state/future-considerations.json` | Update |

---

## Execution Order

1. Create `k8s-quick-status` skill
2. Run kubectl connectivity test
3. Run Prometheus connectivity test
4. Run ArgoCD connectivity test
5. Run Git repo connectivity test
6. Document findings in `future-considerations.json`
7. Report summary