OpenChoreo Import

Take an application spec (Helm chart, Kustomize overlay, Docker Compose file, or raw Kubernetes YAML) and produce a step-by-step migration plan. The plan is the deliverable; the agent iterates with the user as decisions and feedback land.

Step 0 — Tooling

node --version (≥ 18) is always required (the preview server is Node). For each source format, a renderer that turns the input into something analyzable:

• Helm → helm (≥ 3.12) to helm template the chart
• Kustomize → kustomize (or kubectl kustomize) to build the overlay
• Docker Compose → nothing extra (the compose file is YAML, read it directly)
• Raw YAML → nothing extra

A missing renderer isn't a hard stop — install if possible (rendering is the clean path; values + conditionals + ranges decide what a chart actually emits, so only the rendered output is faithful). If install isn't feasible, do a best-effort enumeration from the raw templates and flag that the analysis is degraded, not exhaustive — the plan still ships, just with the limitation called out. Compose and raw YAML need nothing extra.

Step 1 — Load the model primer (MANDATORY read)

Read ./references/concepts.md. The OpenChoreo workload model is intentionally narrow — what fits and what doesn't is the central question of this skill. Load once per session.