will/claude-code
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
f09d74dd967e8baa9fa30a27df479106f133810d
claude-code/plans/wise-dazzling-marshmallow.md
OpenCode Test 431e10b449 Implement programmer agent system and consolidate agent infrastructure 
Programmer Agent System:
- Add programmer-orchestrator (Opus) for workflow coordination
- Add code-planner (Sonnet) for design and planning
- Add code-implementer (Sonnet) for writing code
- Add code-reviewer (Sonnet) for quality review
- Add /programmer command and project registration skill
- Add state files for preferences and project context

Agent Infrastructure:
- Add master-orchestrator and linux-sysadmin agents
- Restructure skills to use SKILL.md subdirectory format
- Convert workflows from markdown to YAML format
- Add commands for k8s and sysadmin domains
- Add shared state files (model-policy, autonomy-levels, system-instructions)
- Add PA memory system (decisions, preferences, projects, facts)

Cleanup:
- Remove deprecated markdown skills and workflows
- Remove crontab example (moved to workflows)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-29 13:23:42 -08:00

2.5 KiB
Raw Blame History

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
kubectl get pods -A
kubectl top nodes		 Cluster connectivity
prometheus-analyst curl localhost:9090/api/v1/query?query=up
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