1# Hand-off to vm-creator
2 
3When the user wants to **provision** the recommended option (not just compare), hand off to [vm-creator](../../vm-creator/vm-creator.md). Don't skip directly to an output adapter — the user must see and approve the Plan Card first.
4 
5## Required before hand-off
6 
7Render the [Plan Card](../../vm-creator/references/plan-card.md) markdown table **in chat** with the chosen SKU, region, instance count, pricing, and quota status pre-filled from the recommender's work. The user is approving the Plan Card, not the artifact.
8 
9## Routing signals
10 
11| User says | Action |
12|---|---|
13| "let's create it" / "spin one up" / "deploy this" | Render Plan Card → route to `vm-creator` Step 5 with selected SKU + region pre-filled |
14| "give me the az CLI / Bicep / Terraform" | Render Plan Card → route to `vm-creator` Step 6 (Output Choice) |
15| "just compare prices" / "I'm still deciding" | Stay in `vm-recommender`; offer to revisit |
16 
17## Example hand-off message
18 
19> *"Want me to generate the create command? I can output az CLI, Bicep, Terraform, or apply it via Azure MCP — I'll carry over the SKU, region, and pricing we just landed on."*
20 
21## What carries over
22 
23| Recommender output | Plan Card row |
24|---|---|
25| Hosting Model (VM vs VMSS) | `Hosting model` |
26| VM Size (ARM SKU) | `Size` |
27| Region | `Region` |
28| Instance Count (or `min–max`) | `Instance count` (VMSS only) |
29| Estimated $/hr | `Estimated cost` |
30| Quota Status (✅/⚠️/❌) | `Quota` |
31 
32`vm-creator` Steps 2–4 (Depth Probe, Adaptive Gather, Validate) still run after hand-off to fill in OS, auth, networking, and tagging — they're additive on top of the recommender's spec choice.
33