Add a new aztf-agent chatmode to have only specific tools enabled. Also updated docs to explain how this works.

Author: raffertyuy

.github/chatmodes/aztf-agent.chatmode.md

@@ -0,0 +1,4 @@
+---
+description: AI-powered agent for implementing Azure Terraform modules.
+tools: ['changes', 'codebase', 'editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'Terraform MCP Server', 'azmcp-bestpractices-get', 'pylance mcp server', 'azure-mcp-server-ext']
+---

.github/copilot-instructions.md

@@ -16,10 +16,10 @@ Check the files in `/.github/instructions/*.instructions.md` for any additional
 
 
 ### File and Folder Structure
-- When you are creating new files or folders, follow the standards in #file:/docs/file-structure.md
-- If you need a reference for what each file or folder does, refer to #file:/docs/file-structure.md
-- When you create a new file in the `/` root folder or the `docs/` folder, update #file:/docs/file-structure.md with a brief decription of the file's purpose and any relevant details.
-- When you create a new folder, update #file:/docs/file-structure.md with a brief description of the folder's purpose and any relevant details.
+- When you are creating new files or folders, follow the standards in #file:/docs/file_structure.md
+- If you need a reference for what each file or folder does, refer to #file:/docs/file_structure.md
+- When you create a new file in the `/` root folder or the `docs/` folder, update #file:/docs/file_structure.md with a brief decription of the file's purpose and any relevant details.
+- When you create a new folder, update #file:/docs/file_structure.md with a brief description of the folder's purpose and any relevant details.
 
 ### **ALWAYS** Document Changes
 **ALL CODE CHANGES** must be documented in #file:/CHANGES_SUMMARY.md including:

.github/prompts/1-plan.prompt.md

@@ -1,5 +1,4 @@
 ---
-mode: 'agent'
 description: 'Plan an implementation'
 ---
 
@@ -19,7 +18,7 @@ Your goal is to generate an implementation plan, in a new markdown .md file, for
 
 ### 2. THEN
 - Create a detailed implementation plan that outlines the steps needed to achieve the objectives of the specification document.
-- Think about the file types that will be created, and review the file `/docs/file-structure.md` as well as instructions for the relevant file in the `/.github/instructions/` folder. For example, follow the instructions in `/.github/instructions/tf.instructions.md` for `*.tf` files.
+- Think about the file types that will be created, and review the file `/docs/file_structure.md` as well as instructions for the relevant file in the `/.github/instructions/` folder. For example, follow the instructions in `/.github/instructions/tf.instructions.md` for `*.tf` files.
 - The plan should be structured, clear, and easy to follow.
 - Always add validation steps in your plan to ensure the implementation meets the requirements.
 - Structure your plan as follows, and output as Markdown code block

.github/prompts/2-implement.prompt.md

@@ -1,5 +1,4 @@
 ---
-mode: 'agent'
 description: 'Implement a plan step by step'
 ---
 Your task is to implement each step of the provided plan, one at a time.
@@ -10,7 +9,7 @@ Your task is to implement each step of the provided plan, one at a time.
 Before implementation, check the corresponding instructions in the `~/.github/instructions` folder.
 For example, follow the instructions in `~/.github/instructions/tf.instructions.md` for `*.tf` files.
 
-Refer to [file-structure.md](../../docs/file-structure.md) and check other implementations in the workspace to see how they are done. **DO NOT** make changes to the other files that you are only using for reference.
+Refer to [file_structure.md](../../docs/file_structure.md) and check other implementations in the workspace to see how they are done. **DO NOT** make changes to the other files that you are only using for reference.
 
 Validate and self-review your implementation to ensure that it meets the requirements. 
 

.github/prompts/3-apply.prompt.md

@@ -1,5 +1,4 @@
 ---
-mode: 'agent'
 description: 'Test the Terraform module implementation by running `terraform plan` and `terraform apply`'
 ---
 Your task is to run `terraform plan` and then `terraform apply` on the `configuration.tfvars` of the terraform module provided to you. And then fix any issues that arise during the process. You will be working with the Terraform module located in `~/modules/<module_name>`.

CHANGES_SUMMARY.md

@@ -62,7 +62,7 @@ This document summarizes the updates made to the Azure DevCenter module to imple
 - **Breaking Change**: No
 
 ### Documentation Updates
-- **Updated**: `docs/file-structure.md` to include environment type implementation plan
+- **Updated**: `docs/file_structure.md` to include environment type implementation plan
 - **Fixed**: Markdown formatting and trailing newline issues
 - **Type**: Documentation improvement
 - **Breaking Change**: No

docs/file-structure.md docs/file_structure.mddocs/file-structure.md renamed to docs/file_structure.md

@@ -57,7 +57,7 @@ This section contains specific files/callouts. If the file is not explained here
 
 - **conventions.md**: Comprehensive coding standards and conventions for Terraform development, including file organization, naming conventions, variable structure patterns, and best practices for consistent code across all modules.
 - **getting_started.md**: Complete setup guide including prerequisites (Terraform, Azure CLI), authentication setup, GitHub Codespaces configuration with MCP (Model Context Protocol) server support, and step-by-step deployment instructions with both VS Code tasks and command-line options.
-- **file-structure.md**: (This file) Documentation of the files and folder structure standards and overview of this workspace.
+- **file_structure.md**: (This file) Documentation of the files and folder structure standards and overview of this workspace.
 - **module_guide.md**: Detailed reference for each Terraform module including purpose, usage examples, input variables, configuration options, and inter-module relationships for Resource Groups, Dev Centers, Projects, Environment Types, Network Connections, Galleries, and Catalogs.
 - **testing.md**: Comprehensive testing guide covering Terraform's native testing functionality with provider mocking, test structure (unit vs integration), running tests via VS Code tasks or command line, writing new tests following established patterns, troubleshooting common issues, and validation procedures.
 

docs/getting_started.md

@@ -110,11 +110,38 @@ az account show --query "[name,id]" -o tsv
 
 Note: We use environment variables for the subscription ID instead of including it in configuration files. This approach is more secure and follows infrastructure-as-code best practices. The VS Code tasks in this project will automatically handle exporting the subscription ID for you.
 
-### 3. Choose How to Run Terraform Commands
+### 3. AI-Assisted Module Development with Copilot Prompts (Recommended)
+
+The project includes specialized copilot prompts for AI-assisted development of Terraform modules. This approach enables "vibe coding" - intuitive module implementation through 3 easy steps:
+
+**Prerequisites:**
+- Ensure the Azure and Terraform MCP servers are running
+- Best used with the `aztf-agent` chat mode for optimal results
+
+**The 3-Step Workflow:**
+
+1. **`/1-plan`** - Plan your Terraform module implementation
+   - Reusable prompt located at: `/.github/prompts/1-plan.prompt.md`
+   - Analyzes requirements and designs module structure
+
+2. **`/2-implement`** - Implement the Terraform module code
+   - Reusable prompt located at: `/.github/prompts/2-implement.prompt.md`
+   - Generates module files, variables, outputs, and documentation
+
+3. **`/3-apply`** - Apply and test the module implementation
+   - Reusable prompt located at: `/.github/prompts/3-apply.prompt.md`
+   - Creates examples and validates the module functionality
+
+This AI-assisted approach leverages the MCP integrations to provide intelligent guidance throughout the module development process, making it easier to create well-structured, documented Terraform modules for Azure resources.
+
+### 4. Choose How to Run Terraform Commands
+
+> [!NOTE]
+> This is only necessary if you skipped `/3-apply` above.
 
 You have two options for running Terraform commands:
 
-#### Option 1: Using VS Code Tasks (Recommended)
+#### Option 1: Using VS Code Tasks
 
 The project includes predefined VS Code tasks for easy execution:
 
@@ -151,15 +178,15 @@ Each example includes:
 - Resource-specific configurations
 - Parent-child resource relationships where needed
 
-### 4. Apply the Configuration
+### 5. Apply the Configuration
 
 After reviewing the plan, apply it:
 
 ```bash
 terraform apply -var-file=examples/resource_group/simple_case/configuration.tfvars
 ```
 
-### 5. Clean Up Resources
+### 6. Clean Up Resources
 
 When you're done, you can remove all created resources using either VS Code tasks or the command line:
 

docs/plans/dev_center_environment_type.plan.md

@@ -110,7 +110,7 @@ This plan outlines the implementation of the `dev_center_environment_type` modul
 - [x] **Step 7: Update Documentation**
   - **Task**: Update project documentation to include environment type module information
   - **Files**:
-    - `docs/file-structure.md`: Already updated with environment type module and example locations
+    - `docs/file_structure.md`: Already updated with environment type module and example locations
     - `docs/module_guide.md`: Already updated with comprehensive environment type usage patterns and configuration options
   - **Dependencies**: Existing documentation standards
   - **Pseudocode**: Add environment type section with usage examples and configuration reference