diff --git a/skills/databricks-serverless-migration/SKILL.md b/skills/databricks-serverless-migration/SKILL.md
index bac1dcd..4e9c998 100644
--- a/skills/databricks-serverless-migration/SKILL.md
+++ b/skills/databricks-serverless-migration/SKILL.md
@@ -21,6 +21,17 @@ Analyze existing Databricks code for serverless compute compatibility and guide
 - Troubleshooting serverless-specific errors after migration
 - Choosing between Performance-Optimized and Standard mode
 
+## Input to get from the user
+Ask the user for explicit input parameters for the following items, providing reasonable defaults:
+- Which workspace contains the source workloads?
+- Which workspace will contain the migrated workloads?
+- What is the catalog and schema where output from the test migrated jobs should go?
+- How should the test jobs be prefixed or tagged?
+- Where in the workspace should the converted code go?
+- What compute should be used for reading output produced by classic jobs for comparison (if serverless is not available)?
+
+Prior to presenting these questions, make sure there are 6 questions (so you don't miss any of the above).
+
 ## Understanding Migration Blockers
 
 Migration blockers fall into three categories. Focus your effort on category 2 — that's where this skill helps most.
@@ -623,6 +634,14 @@ Submission is optional and opt-in. We use reports to prioritize new patterns and
 
 **Never transmit the report automatically.** The user owns their data and must review before sharing.
 
+## Success report
+
+If the migration was successful, generate a report as well, using similar methods. For each workload migrated, show what was done.
+
+## Multiple workload migration
+
+When migrating multiple workloads in one session, parallelize this work as much as possible to migrate multiple workloads in parallel, including using subagents.
+
 ## Reference Guides
 
 For detailed workarounds and code examples beyond the quick fixes above: