migrate-spark-scala-to-snowpark-connect

name	migrate-spark-scala-to-snowpark-connect
description	Migrate Spark Scala workloads to Snowflake SCOS (Snowpark Connect for Spark). Use when: converting Scala Spark code to run on Snowflake, analyzing Scala Spark compatibility, updating imports to Spark Connect equivalents, or migrating from standalone Spark Scala. Generates SMA-compatible reports (Issues.csv, InputFilesInventory.csv, ArtifactDependencyInventory.csv) for the dvp-sma-dashboard-generator using official SMA EWI codes (SPRKCNTSCL*). Triggers: migrate scala spark, convert scala, scos scala migration, spark connect scala, scala compatibility, snowpark connect scala.
parent_skill	snowpark-connect
allowed-tools	Read, Write, Bash, Task

Migrate Spark Scala to SCOS — Coordinator

Orchestrate a multi-phase migration of Spark Scala workloads to Snowflake SCOS (Snowpark Connect for Spark). This coordinator delegates work to specialist sub-agents and validates each phase with the deterministic verify_phase.py script before advancing.

When to Load

[snowpark-connect] Intent Detection: After user indicates migration intent for Scala code (convert, migrate, update imports, rewrite for SCOS).

Arguments

• $ARGUMENTS — Path to the Spark Scala file or directory to migrate

Optional Metadata (from orchestrator)

Parameter	Variable	Description
Output path	$OUTPUT	Target directory for migrated files and Reports/
Customer Email	$EMAIL	Project metadata for reports
Customer Company	$COMPANY	Project metadata for reports
Project Name	$PROJECT	Project name for reports

If not provided, use ${ARGUMENTS}_scos as output and prompt for metadata before the first consumer (the project name is needed by the Phase 1a assessment report; email/company by the Phase 4 CSVs).

Prerequisites

Skill Directory

<SKILL_DIRECTORY> is the parent snowpark-connect/ directory containing pyproject.toml and scripts/. All tool invocations use uv run --project <SKILL_DIRECTORY>.

uv Package Manager

Install uv if it is not already available. Show both OS variants — the skill must work on macOS / Linux and Windows:

# macOS / Linux
uv --version || curl -LsSf https://astral.sh/uv/install.sh | sh

# Windows (PowerShell)
uv --version; if ($LASTEXITCODE -ne 0) { irm https://astral.sh/uv/install.ps1 | iex }

The state model

A migration is a long, multi-phase run: nothing durable lives in this conversation, because it gets summarized or truncated before the run ends. Nor does it live in a checklist you keep in your head or in prose you write as you go — those drift out of step with what actually happened on disk. State lives in one structured, durable place: <CONVERSION>/migration_state.json.

phases_completed is the progress — it is not a log of it. The phase you are on is simply the first row of the phase table whose state key is absent; the phases that passed are the keys that are present. Read progress from the file rather than tracking it separately, and never let a phase's real outcome and its recorded outcome diverge — a phase that did not genuinely run must not be recorded as passed (see Phase Completeness).

After any compaction or context loss, rebuild from migration_state.json — never from memory. It carries the manifest, the paths, coordinator_mode, phases_completed, and per-file pending_files / processed_files progress: enough to resume exactly where the run stopped (see Resumption). You are also its single writer — specialists return results for you to merge, so the file stays consistent (see Universal Gate Contract).

Workflow

You are a coordinator. You NEVER hand-write code fixes yourself — the judgment-heavy Phase 2 fixer is delegated to a specialist sub-agent via the task() tool. The deterministic phases (Phase 1 analysis, Phase 1a assessment render, Phase 3 imports/session/build/headers via update_imports_scala.py, Phase 4 reports) and all phase verification run as scripts you invoke directly — no sub-agent, no tokens. (verify_phase.py replaced the former LLM critic agents; update_imports_scala.py replaced the former import-updater specialist; Phases 1, 1a, and 4 call their generators directly because those generators are deterministic.) State is tracked in migration_state.json.

Progress UI Emit Hooks (Experimental)

These one-liners feed the live dashboard (the same server the PySpark path uses). All are non-fatal (|| true) — migration never blocks on the UI. <SKILL_DIRECTORY> is the parent snowpark-connect/ directory; <CONVERSION> is the resolved Conversion-SCOS-<TIMESTAMP> path.

BUS="python3 <SKILL_DIRECTORY>/../scripts/progress_bus.py"
RUN="<CONVERSION>"
CONNECTION_NAME="<the Snowflake connection resolved in the Cortex preflight>"

⚠️ EXPERIMENTAL — the Progress UI is OFF by default. Never launch it automatically. Start the dashboard only when the user has explicitly asked to see the Progress UI / live dashboard. If they have not explicitly asked, skip the launch block below entirely — no server, no browser window, no accidental launches. The event-emit commands are harmless no-ops when the server is not running, so continue to run them normally regardless.

Assessment-only flows skip this section entirely. If this skill was loaded for assessment / readiness-report intent (stopping after Phase 1a), do not mention, offer, or launch the Progress UI — it only applies to full migrations.

Only if the user explicitly requested the Progress UI, launch the server once, right after $CONVERSION is resolved. The launcher requires the --confirm-experimental interlock (it is a no-op without it), is idempotent (reuses a live server), and is non-fatal:

UI="python3 <SKILL_DIRECTORY>/../scripts/ui_launch.py"
$UI start --run "$RUN" --skill-dir "<SKILL_DIRECTORY>/.." --port auto \
  --confirm-experimental \
  $([ "<config.ui_auto_open_browser>" = "yes" ] || echo "--no-browser") \
  2>/dev/null || true

Emit at each key boundary:

When	Command
Phase 0 done / CONVERSION resolved	$BUS run-init --run "$RUN" --path snowpark-connect --data "{\"project_name\":\"$PROJECT\",\"conversion_type\":\"snowpark-connect (scala)\",\"total_files\":$TOTAL_FILES,\"connection_name\":\"$CONNECTION_NAME\"}" || true
Each phase starts	$BUS phase-start --run "$RUN" --phase "<phase-name>" || true
Each phase ends	$BUS phase-end --run "$RUN" --phase "<phase-name>" || true
Fixer worker chunk assigned (Phase 2)	$BUS agent-status --run "$RUN" --worker "fixer-$N" --status started --phase migration --message "chunk $N/$TOTAL assigned" || true
Fixer converts a file (Phase 2)	$BUS file-progress --run "$RUN" --file "$REL_PATH" --status converted --worker "fixer-$N" --phase migration || true
Phase 2b compile passes for a file	$BUS file-progress --run "$RUN" --file "$REL_PATH" --status verified --phase verification || true
revert_failing_scala_files.py reverts	$BUS file-progress --run "$RUN" --file "$REL_PATH" --status reverted --phase verification || true
Assessment report ready (Phase 1a)	$BUS report-ready --run "$RUN" --file "$REPORTS_DIR/MigrationReadinessReport.html" --phase report-assessment || true
Each Reports/*.csv ready (Phase 4)	$BUS report-ready --run "$RUN" --file "$REPORTS_DIR/Issues.csv" --phase reports || true
Migration summary done	$BUS summary --run "$RUN" --data "{\"total_files\":$TOTAL_FILES,\"converted\":$CONVERTED,\"verified\":$VERIFIED}" || true

Scala phase-name mapping (use these exact names so the dashboard's stage tracker lights up correctly): Phase 0.5 → preprocessing, Phase 0.6 → sql-rewrite, Phase 1 → analysis, Phase 1a → report-assessment, Phase 2 → migration, Phase 2b → verification, Phase 3 → imports-headers, Phase 4 → reports.

Emit run-init once when $CONVERSION is first resolved, immediately after launching the server, using the manifest length as total_files and the preflight connection as connection_name. The dashboard's "Ask" chat is answered by SNOWFLAKE.CORTEX.COMPLETE over that same connection (read from the run-init event), so including connection_name keeps chat on the Cortex-enabled connection instead of falling back to default.

Report linking is automatic. The server scans Reports/ and links MigrationReadinessReport.html, AssessmentIR.json, and the dashboard CSVs as soon as they exist on disk, so they surface even if a report-ready hook is missed. The report-ready emits above are a redundant signal, not the only path.

Phase Playbooks

Every phase's step-by-step procedure lives in its own file under phases/. Read the playbook for the phase you are about to run, run it, then come back here for the next one. Do not preload them all — that is the whole point of the split.

#	Phase	Playbook	State key (phases_completed)	Must run
0	Collect info, create conversion folder	phases/phase-0-setup.md	— (writes state skeleton)	yes
0.5	Deterministic AST pre-processing (Scalafix)	phases/phase-0.5-preprocess.md	0_5b_scalafix ✓	MUST RUN
0.6	Standalone SQL rewrite	phases/phase-0.5-preprocess.md	0_6_sql_rewrite	conditional
1	Analysis	phases/phase-1-analysis.md	1_analysis ✓	yes
1.1	Adjudication	phases/phase-1-analysis.md	1_5_adjudication	default
1a	Render assessment report	phases/phase-1.2-assessment.md	1a_assessment_report ✓	yes
2	Apply fixes (parallel fixer pool)	phases/phase-2-fixes.md	2_fixes ✓	yes
2a	Coverage verification + deterministic fallback	phases/phase-2-gates.md	2a_fallback ✓	MUST RUN
2b	Compilation verification	phases/phase-2-gates.md	2b_compilation ✓	MUST RUN
2c	Evidence-based verification	phases/phase-2-gates.md	2c_verification	recommended
3	Imports, session, build, headers	phases/phase-3-imports.md

✓ = one of the 8 keys validate_migration_state.py --strict --language scala requires. Note the naming trap: Phase 1a writes 1a_assessment_report (not 1_a_...). The state key — not the phase number — is the contract with the validator.

Phase Completeness

Because playbooks load one at a time, the phase table above is your only map — work down it in order and do not rely on remembering what comes next.

Before you report the migration complete, run the completeness check (Phase 4a). It is the single authority on whether every phase was navigated:

python3 <SKILL_DIRECTORY>/scripts/validate_migration_state.py \
  --strict --language scala \
  --state <CONVERSION>/migration_state.json

Exit 0 = all 8 required keys present. Exit 1 = at least one phase never ran. Never report success without a green run of this command — it is the canonical success criterion, and skipping it means nothing checked the pipeline end to end.

Two limits of this check you must compensate for by being honest, because it cannot catch you:

• A skip with a reason passes. {"status": "skipped", "skip_reason": "<any text>"} is accepted as satisfied; only a missing key or a skip with no reason fails. So only ever record skipped when the phase genuinely could not run, and put the real cause in skip_reason — never to move past a phase that merely looked hard.
• This validator is itself an optional phase (4a_validation), so nothing forces you to run it. That is exactly why it is listed MUST RUN above.

Per-phase verify_phase.py checks are the complement: they inspect the code on disk, so they catch a phase that ran but did nothing — State-key presence proves navigation; the verifiers prove work.

Universal Gate Contract

Every deterministic gate (scripts/verify_phase.py and scripts/scos_gates.py) uses the same behavioral protocol. Read the verdict from stdout — never rely on a non-portable $? capture.

verify_phase.py exit codes (phases 1, 2, 3, 4):

Exit	Verdict	Action
0	PASS / PASS_WITH_GAPS	Advance. PASS_WITH_GAPS carries advisory WARN findings — record them, do not block.
1	FAIL	Gap-scoped re-dispatch: pass the listed failing checks as targeted feedback and fix only those, leaving already-resolved code untouched. Re-run the verifier. Never re-run a whole file statelessly; that regresses correct work.

scos_gates.py exit codes (Phase 1a assessment, and as the legacy Python-compatible gate):

Exit	Verdict	Action
0	PASS / PASS_WITH_GAPS	Advance.
2	FAIL	Gap-scoped re-dispatch (same as above).
3	IO / usage error	STOP and escalate. A missing state file or bad path will not be fixed by re-running the specialist.

On every FAIL, read the gate output carefully before acting. Some failure codes are not fixable by a specialist at all: phase2_not_orchestrated means you skipped a coordinator step; manifest_file_missing is a coverage problem; a pre-existing compile failure in the customer's source must not trigger a fixer re-dispatch. Check what the gate is reporting before dispatching anything.

Empty stdout means the gate did not run — it is NOT a FAIL. A malformed command line exits non-zero with empty stdout because argparse exits 2 and does not honour the 3 reserved above. If stdout is empty or the verdict is missing, fix your own invocation and re-run the gate. Do NOT re-dispatch a specialist.

Default retry budget is 2 attempts on failure, then escalate to the user. Phase 1a allows 3.

On every advance, record the outcome under migration_state.json :: phases_completed with status, the verifier/gate name, and attempts; on an unrunnable phase record {"status": "skipped", "skip_reason": "<one-line reason>"}. You (the coordinator) are the single writer of migration_state.json — specialists return results for you to merge.

After each phase, git checkpoint inside <CONVERSION>; the playbooks give the exact commit messages and tags (phase-0-source, phase-1-complete, …), which the gates depend on for baselines.

Specialists and References

File	Role
agents/analyzer.md	Phase 1 analysis procedure (reference)
agents/adjudicator.md	Phase 1.1b adjudication
agents/reporter.md	Phase 1a + Phase 4 report rendering (reference)
agents/data_edge_resolver.md	Phase 1.3 data-edge enrichment (if applicable)
agents/fixer.md	Phase 2 code fixing (incl. targeted re-fix mode)
references/fix-rules.md	Scala fix rules
references/sql-fix-rules.md	SQL fix rules
<SKILL_DIRECTORY>/references/scala/rdd-conversion.md	Holistic RDD chain conversion

Resumption

If context is lost mid-migration, read migration_state.json to determine the last completed phase and resume from the next one. The gate file contains the manifest, paths, and per-file progress needed to continue.

Stopping Points

• Phase 0: After collecting project info — confirm settings before starting
• Phase 2: If verify_phase.py --phase 2 fails after 2 retries — escalate to user with specific errors
• Phase 5: After migration completes — ask user about validation

Success Criteria

• scripts/validate_migration_state.py --strict --language scala exits 0 (this is the canonical, machine-checkable success criterion — see Phase 4a)
• migration_state.json shows all phases 0.5, 1, 1a, 2, 2a, 2b, 3, 4 completed and verified; Phase 0.6 completed or marked not_applicable; Phase 2c completed (evidence-based verification reconciled)
• Reports/Issues.csv exists with data rows
• Reports/InputFilesInventory.csv code-row count (conversion units, Ignored == "False") matches the manifest
• Reports/MigrationReadinessReport.html and Reports/AssessmentIR.json exist (both an early Phase 1a snapshot and a final Phase 4 render)
• All .scala files pass the Phase 2b compile gate — scalac -Ystop-after:typer (when the SCOS client JAR is resolvable), else -Ystop-after:parser, else tokenizer fallback; the mode used is recorded in phases_completed.2b_compilation.compile_mode
• Every .scala file has a migration header block comment
• Build files actively transformed (Scala 2.12+, Spark 3.5+, com.snowflake:snowpark-connect-java-client added)
• File count matches between original and migrated directories
• Feedback/migrate_gaps.md exists (Phase 4b) or Phase 4b was skipped with a logged reason

Output

<output_root>/
  Conversion-SCOS-<timestamp>/                       ← <CONVERSION>
    Output/                                          ← <MIGRATED> — converted files
    Reports/
      Issues.csv                                     ← EWI issues (SPRKCNTSCL*)
      InputFilesInventory.csv                        ← Source file inventory
      ArtifactDependencyInventory.csv                ← Import dependencies
      MigrationReadinessReport.html                  ← Stakeholder-facing readiness report
      AssessmentIR.json                              ← Structured IR (stable contract)
    Logs/                                            ← Migration log
    migration_state.json                             ← Phase gate tracking
    analysis.json                                    ← Compatibility analysis
    Feedback/
      migrate_gaps.md                                ← FDE-ready triage file (Phase 4b)