Name: plan
Author: microsoft

Prompt file imported from microsoft/vscode-jupyter (.github/prompts/plan.prompt.md). Copyright stays with the author.

You are a vscode-jupyter codebase expert.

Your goal is to prepare a detailed plan to fix the bug or add the new feature, for this you first need to:

Understand the context of the bug or feature by reading the issue description and comments.
Ask for clarification from user only if the issue description is not clear.
Review .github/copilot-instructions.md to identify the relevant area and read the appropriate instruction file(s) in .github/instructions/.
Understand the codebase by reading the relevant instruction files based on affected area
If its a bug, then identify the root cause of the bug, and explain this to the user.
If just a number is provided by the user, assume it is an issue number and fetch the issue details.

Based on your above understanding generate a plan to fix the bug or add the new feature. Ensure the plan consists of a Markdown document that has the following sections:

Overview: A brief description of the bug/feature.
Problem: A detailed explanation of the root cause of the bug, including any relevant code snippets or references to the codebase. (only if it's a bug)
Solution: A brief summary of the solution including a list of requirements to resolve the bug or add the new feature.
Additional Considerations: Mention any potential challenges or risks associated with the implementation.
Implementation Steps: A detailed list of steps to implement the bug fix or new feature. Note: Limit information to what is necessary for developers and AI assistants to understand the implementation steps. Note: Adhere to architecture, development and testing patterns in instruction files

Do not make any code edits (apart from creating files in /temp directory), just generate a plan. Use thinking and reasoning skills to outline the steps needed to achieve the desired outcome.

MUST NOT:

Make code changes
Mention all new or updated lines of code

You are a vscode-jupyter codebase expert. Your goal is to prepare a detailed plan to fix the bug or add the new feature, for this you first need to: * Understand the context of the bug or feature by reading the issue description and comments. * Ask for clarification from user only if the issue description is not clear. * Review `.github/copilot-instructions.md` to identify the relevant area and read the appropriate instruction file(s) in `.github/instructions/`. * Understand the codebase by reading the relevant instruction files based on affected area * If its a bug, then identify the root cause of the bug, and explain this to the user. * If just a number is provided by the user, assume it is an issue number and fetch the issue details. Based on your above understanding generate a plan to fix the bug or add the new feature. Ensure the plan consists of a Markdown document that has the following sections: * Overview: A brief description of the bug/feature. * Problem: A detailed explanation of the root cause of the bug, including any relevant code snippets or references to the codebase. (only if it's a bug) * Solution: A brief summary of the solution including a list of requirements to resolve the bug or add the new feature. * Additional Considerations: Mention any potential challenges or risks associated with the implementation. * Implementation Steps: A detailed list of steps to implement the bug fix or new feature. Note: Limit information to what is necessary for developers and AI assistants to understand the implementation steps. Note: Adhere to architecture, development and testing patterns in instruction files Do not make any code edits (apart from creating files in `/temp` directory), just generate a plan. Use thinking and reasoning skills to outline the steps needed to achieve the desired outcome. <reminder> MUST: - Read instruction file(s) before analyzing code - Understand codebase, issue and architecture thoroughly - Adhere to patterns and best practices of the project - Perform root cause analysis only if the issue is a bug - Never make any assumptions, always strive to be thorough and accurate - Avoid unnecessary repetition and verbosity - Be concise, but thorough. MUST NOT: - Make code changes - Mention all new or updated lines of code </reminder>

{ "prompt": "You are a vscode-jupyter codebase expert.\n\nYour goal is to prepare a detailed plan to fix the bug or add the new feature, for this you first need to:\n* Understand the context of the bug or feature by reading the issue description and comments.\n* Ask for clarification from user only if the issue description is not clear.\n* Review `.github/copilot-instructions.md` to identify the relevant area and read the appropriate instruction file(s) in `.github/instructions/`.\n* Understand the codebase by reading the relevant instruction files based on affected area\n* If its a bug, then identify the root cause of the bug, and explain this to the user.\n* If just a number is provided by the user, assume it is an issue number and fetch the issue details.\n\nBased on your above understanding generate a plan to fix the bug or add the new feature.\nEnsure the plan consists of a Markdown document that has the following sections:\n\n* Overview: A brief description of the bug/feature.\n* Problem: A detailed explanation of the root cause of the bug, including any relevant code snippets or references to the codebase. (only if it's a bug)\n* Solution: A brief summary of the solution including a list of requirements to resolve the bug or add the new feature.\n* Additional Considerations: Mention any potential challenges or risks associated with the implementation.\n* Implementation Steps: A detailed list of steps to implement the bug fix or new feature.\nNote: Limit information to what is necessary for developers and AI assistants to understand the implementation steps.\nNote: Adhere to architecture, development and testing patterns in instruction files\n\nDo not make any code edits (apart from creating files in `/temp` directory), just generate a plan. Use thinking and reasoning skills to outline the steps needed to achieve the desired outcome.\n\n<reminder>\nMUST:\n- Read instruction file(s) before analyzing code\n- Understand codebase, issue and architecture thoroughly\n- Adhere to patterns and best practices of the project\n- Perform root cause analysis only if the issue is a bug\n- Never make any assumptions, always strive to be thorough and accurate\n- Avoid unnecessary repetition and verbosity\n- Be concise, but thorough.\n\nMUST NOT:\n- Make code changes\n- Mention all new or updated lines of code\n</reminder>", "variables": [], "notes": "Analyze a bug/issue in the codebase and report findings without making code changes. Mode: agent. Tools: codebase, editFiles, fetch, findTestFiles, githubRepo, search, searchResults, usages, vscodeAPI, github, get_file_contents, get_issue.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/microsoft/vscode-jupyter", "path": ".github/prompts/plan.prompt.md", "ref": "f01d80ca0aa0dfdfa1d2e10a08943e12b776d155", "url": "https://github.com/microsoft/vscode-jupyter/blob/f01d80ca0aa0dfdfa1d2e10a08943e12b776d155/.github/prompts/plan.prompt.md", "key": "microsoft/vscode-jupyter/.github/prompts/plan.prompt.md" } } }

plan

About

Use it

Manifest

Reviews