Adding Bicep chat modes for *planning* and *implementation* #234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
node update-readme.jsand verified thatREADME.mdis up to date.Description
The Bicep plan chat mode is used to create a comprehensive Markdown file containing all the information required to deploy specific services. It defines the properties of AVM modules, “raw” resources, and more. The plan is grounded through tool calls to Azure Verified Modules and Microsoft Docs, and it retrieves Bicep best practices via Bicep MCP.
The Bicep implementation chat mode is used to generate a Bicep template based on the plan, or it can be used standalone. This chat mode is designed to break down the user’s prompt into actionable tasks, generate the Bicep Infrastructure as Code, and validate the generated code using
bicep <lint/build/format/restore>commands.Type of Contribution
Additional Notes
Links to showcase that the modes work as intended:
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.