run-migration-assessment

# Run Migration Assessment ## When to Use Use as the entry point for migration assessment requests when Azure versus Local, or readiness versus SKU, still needs to be determined. ## Workflow ### Step 1: Identify the Server Reuse known inputs. Determine only whether the source is Azure or Local: - Azure identifiers or an Azure SQL Server resource URI -> Azure. - IP, connection string, config file, or explicit on-premises/local wording -> Local. - Bare server or instance name -> ask: **"Is `{serverName}` a Local/on-premises SQL Server or an Azure SQL Server?"** Wait for the answer when the path is ambiguous. Do not resolve Azure resources, check Local prerequisites, request credentials, select output folders, inspect existing results, or run commands in this skill. ### Step 2: Route Azure Delegate to `evaluate-azure-migration-assessment` with all known context and the user's original intent. That skill owns resource resolution, existing-result handling, fresh execution, and output. ### Step 3: Route Local - Readiness or general assessment request -> delegate to `evaluate-offline-migration-readiness`. - Explicit performance collection or SKU-sizing request -> delegate to `recommend-sku-sizing`. Pass all known context and the user's original intent. The delegated skill owns host checks, prerequisites, connection details, output-folder selection, existing-result handling, execution, and output. ## Notes - Ask only whether the source is Azure or Local when that choice is ambiguous. - Do not duplicate delegated-skill prerequisites or workflows here. - Delegated skills own commands, errors, follow-up choices, and output formatting. ## Error Handling - Cannot determine Azure versus Local -> ask the user to select Azure or Local. - Missing details after routing -> let the delegated skill request them.