@@ -14,7 +14,7 @@ High level steps involved:
1414
1515---
1616
17- ## Part A: Generate SDK Locally
17+ ## Generate SDK Locally
1818
1919### Step 1: Outline workflow
2020
@@ -26,9 +26,10 @@ High level steps involved:
2626 2 . Verify SDK repository
2727 3 . Validate repository path
2828 4 . Identify path to configuration file
29- 5 . Generate SDK using ` azsdk_package_generate_code ` MCP tool
30- 6 . Identify SDK project path
31- 7 . Build/Compile SDK using ` azsdk_package_build_code ` MCP tool
29+ 5 . Verify setup for the selected language
30+ 6 . Generate SDK using ` azsdk_package_generate_code ` MCP tool
31+ 7 . Identify SDK project path
32+ 8 . Build/Compile SDK using ` azsdk_package_build_code ` MCP tool
3233- Ask the user to confirm readiness to proceed.
3334
3435---
@@ -71,7 +72,6 @@ High level steps involved:
7172
7273- Check if the provided repository path exists and matches the selected SDK language repository.
7374- If invalid → prompt user to re-enter a valid path.
74- - Verify setup to ensure all required tools are installed for the selected language.
7575
7676---
7777
@@ -96,15 +96,20 @@ High level steps involved:
9696
9797---
9898
99- ### Step 6: Generate SDK
100-
99+ ### Step 6: Verify setup for selected language
101100** Actions** :
101+ - Run ` azsdk_verify_setup ` MCP tool to ensure the local environment is correctly configured for the selected SDK language.
102+
103+ ---
102104
105+ ### Step 7: Generate SDK
106+
107+ ** Actions** :
103108- Run ` azsdk_package_generate_code ` MCP tool to generate the SDK locally.
104109
105110---
106111
107- ## Part B: Build / Compile SDK Locally
112+ ## Build / Compile SDK Locally
108113
109114### Step 1: Identify SDK project path
110115
0 commit comments