Skip to content

Commit 156e111

Browse files
smw-msazure-sdk
authored andcommitted
Update creation instructions
1 parent a290d03 commit 156e111

File tree

1 file changed

+6
-13
lines changed

1 file changed

+6
-13
lines changed

eng/common/instructions/azsdk-tools/create-release-plan.instructions.md

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
1-
> **Important Note for LLM**
2-
> Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
3-
> All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.
4-
> Only provide release plan details such as **Release Plan Link** and **Release Plan ID** to the user
1+
> **CRITICAL INSTRUCTIONS FOR LLM***
2+
> 1. Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
3+
> 2. All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.
4+
> 3. Only provide release plan details such as **Release Plan Link** and **Release Plan ID** to the user
5+
> 4. Always check the `NextSteps` field in the tool response and follow any additional prompts provided. Do NOT proceed to other steps until the NextSteps are completed.
56
67
# Release Plan Creation Process
78
Your goal is to create a valid release plan. You must prompt user to provide all required information and all input must match the format and requirement mentioned in step 3 below.
@@ -28,18 +29,10 @@ If any details are missing, prompt the user accordingly:
2829
- If the user doesn't know the required details, direct them to create a release plan using the release planner
2930
- Provide this resource: [Release Plan Creation Guide](https://eng.ms/docs/products/azure-developer-experience/plan/release-plan-create)
3031
- Once all information is gathered, use `azsdk_create_release_plan` to create the release plan
31-
- If existing release plans are found, follow the instructions under Step 3a - Handle Existing Release Plans
32+
- If existing release plans are found, extract and display key information: Release Plan ID, status, associated languages, SDK PRs
3233
- Display the newly created release plan details to the user for confirmation
3334
- Refer to #file:sdk-details-in-release-plan.instructions.md to identify languages configured in the TypeSpec project and add them to the release plan
3435

35-
### Step 3a: Handle Existing Release Plans
36-
- When `azsdk_create_release_plan` returns existing release plans.
37-
- Extract and display key information: Release Plan ID, status, associated languages, SDK PRs
38-
- Present the three options:
39-
1. **Work with the existing release plan** - Use the current release plan and make any needed updates
40-
2. **Force create a new release plan** - Create a completely new release plan even though one already exists
41-
3. **Cancel** - Don't proceed with release plan creation
42-
4336
## Step 4: Update SDK Details in Release Plan
4437
- Refer to #file:sdk-details-in-release-plan.instructions.md to add languages and package names to the release plan
4538
- If the TypeSpec project is for a management plane, refer to #file:verify-namespace-approval.instructions.md if this is first release of SDK.

0 commit comments

Comments
 (0)