prepare-release-plan skill updates (#15566)

* Update release plan and SDK release skills with improved wording and optional spec PR

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Apply suggestion from @praveenkuttappan

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Praveen Kuttappan <55455725+praveenkuttappan@users.noreply.github.com>

Author: 3 people

.github/skills/azsdk-common-prepare-release-plan/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   distribution: shared
 description: "Create and manage release plan work items for Azure SDK releases across languages. **UTILITY SKILL**. USE FOR: \"create release plan\", \"update release plan\", \"link SDK PR to plan\", \"namespace approval\", \"check release plan status\". DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan."
 compatibility:
-  requires: "azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs"
+  requires: "azure-sdk-mcp server, API spec PR, or TypeSpec project path"
 ---
 
 # Prepare Release Plan
@@ -26,8 +26,8 @@ compatibility:
 
 ## Steps
 
-1. **Prerequisites** — Check for API spec PR; prompt if unavailable.
-2. **Check Existing** — Query by plan number or spec PR link.
+1. **Prerequisites** — Check for API spec PR link or a TypeSpec project path; prompt if unavailable.
+2. **Check Existing** — Query by release plan number or spec PR link (do not query by work item ID).
 3. **Gather Info** — Collect Service Tree IDs, timeline. See [details](references/release-plan-details.md).
 4. **Create** — Run `azure-sdk-mcp:azsdk_create_release_plan`.
 5. **Namespace** — For mgmt plane first releases, link approval issue.
@@ -36,9 +36,10 @@ compatibility:
 ## Examples
 
 - "Create a release plan for my spec PR"
+- "Create a release plan for my TypeSpec project"
 - "Link my SDK PR to release plan"
 
 ## Troubleshooting
 
 - Requires `azure-sdk-mcp` server; no CLI fallback.
-- If creation fails, verify spec PR URL and Service Tree IDs.
+- If creation fails, verify Service Tree IDs and the provided spec PR URL or TypeSpec project path.

.github/skills/azsdk-common-sdk-release/SKILL.md

@@ -22,6 +22,7 @@ compatibility:
 
 1. **Collect Info** — Get `packageName` and `language` from the user. Optionally get `branch` (defaults to main).
 2. **Check Readiness** — Run `azure-sdk-mcp:azsdk_release_sdk` with `checkReady: true` to verify API review approval, changelog, package name approval, and release date.
+  - If APIView approval is pending display the link or guidance to find the link if not provided.
 3. **Review Results** — If not ready, display failing checks and guide user to resolve.
 4. **Trigger Release** — Once ready, run `azure-sdk-mcp:azsdk_release_sdk` with `checkReady: false`. Show pipeline link and inform user they must approve the release stage.
 

plugins/azure-sdk-tools/skills/prepare-release-plan/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   distribution: shared
 description: "Create and manage release plan work items for Azure SDK releases across languages. **UTILITY SKILL**. USE FOR: \"create release plan\", \"update release plan\", \"link SDK PR to plan\", \"namespace approval\", \"check release plan status\". DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan."
 compatibility:
-  requires: "azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs"
+  requires: "azure-sdk-mcp server, API spec PR, or TypeSpec project path"
 ---
 
 # Prepare Release Plan
@@ -26,8 +26,8 @@ compatibility:
 
 ## Steps
 
-1. **Prerequisites** — Check for API spec PR; prompt if unavailable.
-2. **Check Existing** — Query by plan number or spec PR link.
+1. **Prerequisites** — Check for API spec PR link or a TypeSpec project path; prompt if unavailable.
+2. **Check Existing** — Query by release plan number or spec PR link (do not query by work item ID).
 3. **Gather Info** — Collect Service Tree IDs, timeline. See [details](references/release-plan-details.md).
 4. **Create** — Run `azure-sdk-mcp:azsdk_create_release_plan`.
 5. **Namespace** — For mgmt plane first releases, link approval issue.
@@ -36,9 +36,10 @@ compatibility:
 ## Examples
 
 - "Create a release plan for my spec PR"
+- "Create a release plan for my TypeSpec project"
 - "Link my SDK PR to release plan"
 
 ## Troubleshooting
 
 - Requires `azure-sdk-mcp` server; no CLI fallback.
-- If creation fails, verify spec PR URL and Service Tree IDs.
+- If creation fails, verify Service Tree IDs and the provided spec PR URL or TypeSpec project path.

plugins/azure-sdk-tools/skills/sdk-release/SKILL.md

@@ -22,6 +22,7 @@ compatibility:
 
 1. **Collect Info** — Get `packageName` and `language` from the user. Optionally get `branch` (defaults to main).
 2. **Check Readiness** — Run `azure-sdk-mcp:azsdk_release_sdk` with `checkReady: true` to verify API review approval, changelog, package name approval, and release date.
+  - If APIView approval is pending display the link or guidance to find the link if not provided.
 3. **Review Results** — If not ready, display failing checks and guide user to resolve.
 4. **Trigger Release** — Once ready, run `azure-sdk-mcp:azsdk_release_sdk` with `checkReady: false`. Show pipeline link and inform user they must approve the release stage.