AGENT SKILL

azsdk-common-prepare-release-plan

Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. **UTILITY SKILL**. USE FOR: "create release plan", "get release plan", "update release plan", "update API spec in release plan", "update SDK details in release plan", "abandon 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_update_release_plan, azure-sdk-mcp:azsdk_update_release_plan_target, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 6.1k
Forks
5.2k

01 前言 Front Matter

name
azsdk-common-prepare-release-plan
license
MIT
metadata
{ "version": "1.0.0", "distribution": "shared" }
description
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. **UTILITY SKILL**. USE FOR: "create release plan", "get release plan", "update release plan", "update API spec in release plan", "update SDK details in release plan", "abandon 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_update_release_plan, azure-sdk-mcp:azsdk_update_release_plan_target, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.
compatibility
azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs

02 资源文件 5

03 SKILL.md 正文

Prepare Release Plan

This skill creates, gets, updates, abandons, and links SDK PRs to release plan work items for Azure SDK releases, helping gather required release data, validate spec inputs, and link related approvals or SDK pull requests without exposing internal work item URLs.

Triggers

USE FOR: create release plan, get release plan, update release plan, update API spec in release plan, update SDK details in release plan, abandon release plan, link SDK PR to plan, namespace approval, check release plan status WHEN: "create release plan", "get release plan", "update release plan", "abandon 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

Rules

  • Do not display Azure DevOps work item URLs; only provide the Release Plan Link and ID.
  • Require an API spec PR link or a TypeSpec project path before creating or updating a plan.
  • Validate that the spec PR repository matches the requested API release type before creation.
  • Release plan tools accept either a Release Plan ID or an Azure DevOps work item ID — pass whichever the user provides. Each tool resolves the value automatically (trying it as a Release Plan ID first, then as a work item ID), so you do not need to call azure-sdk-mcp:azsdk_get_release_plan first just to translate one ID into the other.
  • Always relay schedule-risk warnings and next_steps returned by release plan tools. For each past-due plan, show its Release Plan ID and dashboard link, then present both choices: update its target release month or abandon it and record the reason in the dashboard.

MCP Tools

Tool Purpose
azure-sdk-mcp:azsdk_create_release_plan Create a new release plan
azure-sdk-mcp:azsdk_get_release_plan Get plan by ID, path, or spec PR
azure-sdk-mcp:azsdk_update_release_plan Update release plan metadata
azure-sdk-mcp:azsdk_update_release_plan_target Update the target release month
azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan Update API spec PR URL in plan
azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan Update SDK/package details in plan
azure-sdk-mcp:azsdk_abandon_release_plan Abandon a release plan
azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan Link SDK PR to release plan
azure-sdk-mcp:azsdk_link_namespace_approval_issue Link namespace approval issue

Use Cases

1. Create Release Plan

When: User wants to create a release plan for a TypeSpec project.

Steps:

  1. Get TypeSpec Project Path — Ask the user for the relative TypeSpec project path (directory containing tspconfig.yaml, e.g. specification/contosowidgetmanager/Contoso.WidgetManager). Always use the relative path from the repo root, not an absolute path.
  2. Check Existing — Run azure-sdk-mcp:azsdk_get_release_plan with the relative typeSpecProjectPath to check if a release plan already exists.
    • If a release plan exists with the same API release type the user requested: inform the user that a release plan already exists, show the Release Plan ID, status, and API release type. Suggest the user use the existing release plan. Do NOT create a new one.
    • If a release plan exists but for a different API release type: inform the user about the existing plan and its API release type, then proceed to create a new release plan using forceCreateReleasePlan: true for the user's requested API release type. Do NOT attempt to update the existing release plan's API release type.
    • If no release plan exists, proceed to step 3.
  3. Gather Info — Collect required details from the user. See details:
    • Target release month/year (format: "Month YYYY", e.g. "June 2026"). Do NOT use formats like "2026-06" or "06/2026" — these are invalid.
    • API release type: Value must be one of the following: "Private Preview", "Public Preview", or "GA"
    • SDK release type: Value must be "beta" or "stable" — always ask the user explicitly
    • Spec PR URL (optional)
    • Service Tree ID (GUID) — optional if previously created
    • Product Tree ID (GUID) — optional if previously created
  4. Create — Run azure-sdk-mcp:azsdk_create_release_plan with the collected parameters including sdkReleaseType. Use forceCreateReleasePlan: true only if an existing release plan was found for a different API release type.
  5. Namespace — For first management plane releases, link namespace approval issue using azure-sdk-mcp:azsdk_link_namespace_approval_issue.

IMPORTANT: Do NOT default the API release type value as the SDK release type. These are separate fields — always ask the user explicitly for the SDK release type.

IMPORTANT: Do NOT update an existing release plan to change its API release type. If a release plan exists for a different API release type, force-create a new one instead.

Tool: azure-sdk-mcp:azsdk_create_release_plan


2. Get Release Plan

When: User wants to check the status or details of an existing release plan.

Steps:

  1. Identify Plan — Ask user for one of:
    • Release plan ID or work item ID
    • Relative TypeSpec project path (e.g. specification/contosowidgetmanager/Contoso.WidgetManager)
    • Spec PR URL
  2. Query — Run azure-sdk-mcp:azsdk_get_release_plan with the provided identifier. Always use a relative path for typeSpecProjectPath; use specPullRequestUrl when the user provides only a spec PR URL.
  3. Display — Show the release plan ID, status, linked PRs, and SDK details. Always relay schedule-risk warnings and recommended actions from the response.

Tool: azure-sdk-mcp:azsdk_get_release_plan


3. Update Release Plan / Update API Spec in Release Plan

When: User needs to update release plan metadata (spec PR URL, TypeSpec project path, SDK release type, service/product IDs) or update the API spec PR link.

Steps:

  1. Identify Plan — Get the work item ID or TypeSpec project path from the user.
  2. Update Metadata — Run azure-sdk-mcp:azsdk_update_release_plan with:
    • typeSpecProjectPath (required)
    • workItemId (optional — resolved from TypeSpec path or spec PR if not provided)
    • specPullRequestUrl (optional)
    • sdkReleaseType (required — do NOT default this from API release type; always ask user explicitly)
    • serviceTreeId (optional)
    • productTreeId (optional)
  3. Update API Spec PR — If only the spec PR URL needs updating, run azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan with:
    • specPullRequestUrl (required)
    • workItemId or releasePlanId

Tools: azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan


4. Update SDK/Package Details in Release Plan

When: User needs to update SDK language and package name details in the release plan after code generation or configuration changes.

Steps:

  1. Identify Plan — Get the Release Plan ID or work item ID from the user (either is accepted).
  2. Identify TypeSpec Project — Get or confirm the TypeSpec project path.
  3. Update — Run azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan with:
    • workItemId (required — accepts either the Release Plan ID or the work item ID)
    • typeSpecProjectPath (required)

Tool: azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan


5. Abandon a Release Plan

When: User decides to cancel or discard a release plan that is no longer needed.

Steps:

  1. Identify Plan — Get the work item ID or release plan ID from the user.
  2. Confirm — Ask user to confirm abandonment: "Are you sure you want to abandon this release plan? This action updates the status to Abandoned."
  3. Abandon — Run azure-sdk-mcp:azsdk_abandon_release_plan with:
    • workItemId or releasePlanId

Tool: azure-sdk-mcp:azsdk_abandon_release_plan


6. Link SDK Pull Request to Release Plan

When: SDK pull requests have been created and need to be associated with the release plan.

Steps:

  1. Identify Plan — Get the Release Plan ID or work item ID from the user (either is accepted).
  2. Collect PR Info — Get the SDK pull request URL and language from the user.
  3. Link — Run azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan with:
    • pullRequestUrl (required)
    • language (required — e.g., ".NET", "Java", "JavaScript", "Python", "Go")
    • workItemId or releasePlanId (either accepts the Release Plan ID or the work item ID)
  4. Repeat — If multiple SDK PRs exist for different languages, repeat for each.

Tool: azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan


Examples

  • "Create a release plan for my spec PR"
  • "Get the release plan for work item 12345"
  • "What is the status of my release plan?"
  • "Update the API spec PR in my release plan"
  • "Update SDK details in release plan 67890"
  • "Abandon release plan 11111"
  • "Link my SDK PR to release plan"
  • "Link Python SDK PR #100 to release plan 67890"

Troubleshooting

  • Requires azure-sdk-mcp server; no CLI fallback — prompt user to configure MCP if unavailable.
  • If creation fails, verify spec PR URL and Service Tree IDs.
  • If update fails, ensure the Release Plan ID or work item ID is correct and the plan is not already abandoned.
  • If linking fails, verify the SDK PR URL is valid and the language matches a supported value.

04 同仓库更多 Skills

Azure
Azure/azure-sdk-for-net

update-chat-api

Use when: updating, exporting, refreshing, or validating the public API baseline for Azure.Messaging.WebPubSub.Chat after a public API change.

开发工程师后端与接口
★ 6.1k
Azure
Azure/azure-sdk-for-net

search-documents

E2E workflow skill for Azure.Search.Documents SDK (TypeSpec + heavy customization). Handles full release cycles and partial updates: SHA update; code generation; build; customization fixes; ServiceVersion sync; testing; API export; changelog; version; samples; formatting; release metadata. WHEN: create new package version for Azure.Search.Documents; regenerate Azure.Search.Documents; fix Azure.Search.Documents bug; release Azure.Search.Documents; update Azure.Search.Documents spec. Do not use for Azure.ResourceManager.Search or Azure.Provisioning.Search.

开发工程师测试与质量Skill与智能体开发
★ 6.1k
Azure
Azure/azure-sdk-for-net

search-documents-version-diff

Diff the current Azure.Search.Documents public API surface against a previous published version and detect preview-to-preview regressions where the SDK customization layer was not bubbled up after a TypeSpec change. Use whenever the user asks to compare Azure.Search.Documents betas, verify no Azure.Search.Documents preview features dropped, regression audit between Azure.Search.Documents versions, sanity-check a release branch for Azure.Search.Documents, or investigate a missing Azure.Search.Documents preview feature — even if they don't say the word "diff". Specifically catches dropped wrappers (QueryAnswer/QueryCaption/QueryRewrites style), lost SearchOptions aggregator redirectors, `@@access("internal")` flips, deleted-instead-of-gated `#if AZURE_SEARCH_PREVIEW` blocks, dropped `ServiceVersion` enum values, and convenience-to-protocol downgrades.

★ 6.1k
Azure
Azure/azure-sdk-for-net

search-documents-typespec-validation

TypeSpec validation skill for Azure.Search.Documents SDK. Performs a COMPLETE validation of ALL operations, ALL models, ALL enums, and ALL properties against the TypeSpec definition at any pinned commit. Works for any API version. Generates a full gap report: missing features, extra features, naming mismatches, and recommended fix location. WHEN: "validate Azure.Search.Documents SDK against TypeSpec", "detect Azure.Search.Documents typespec feature gaps", "what is missing from the Azure.Search.Documents SDK", "compare Azure.Search.Documents SDK to spec", "full spec coverage audit for Azure.Search.Documents". Do NOT use for version-to-version diff or regression detection — use search-documents-version-diff instead.

Skill与智能体开发
★ 6.1k
Azure
Azure/azure-sdk-for-net

test-skill_file

Roll dice using a random number generator.

★ 6.1k
Azure
Azure/azure-sdk-for-net

roll-dice

Roll dice using a random number generator. Use when asked to roll a die (d6, d20, etc.), roll dice, or generate a random dice roll.

★ 6.1k