fix(chatmodes): update tool references from create_issue to issue_write across multiple chat modes and prompts

Author: krugazul

.github/chatmodes/awesome-copilot/prd.chatmode.md

@@ -1,7 +1,7 @@
 ---
 
 description: 'Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics. Optionally create GitHub issues upon user confirmation.'
-tools: ['codebase', 'edit/editFiles', 'fetch', 'findTestFiles', 'list_issues', 'githubRepo', 'search', 'add_issue_comment', 'create_issue', 'update_issue', 'get_issue', 'search_issues']
+tools: ['codebase', 'edit/editFiles', 'fetch', 'findTestFiles', 'list_issues', 'githubRepo', 'search', 'add_issue_comment', 'issue_write', 'update_issue', 'get_issue', 'search_issues']
 ---
 
 # Create PRD Chat Mode

.github/chatmodes/awesome-copilot/principal-software-engineer.chatmode.md

@@ -1,6 +1,6 @@
 ---
 description: 'Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.'
-tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
+tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'issue_write']
 ---
 # Principal software engineer mode instructions
 

.github/chatmodes/awesome-copilot/refine-issue.chatmode.md

@@ -1,6 +1,6 @@
 ---
 description: 'Refine the requirement or issue with Acceptance Criteria, Technical Considerations, Edge Cases, and NFRs'
-tools: [ 'list_issues','githubRepo', 'search', 'add_issue_comment','create_issue','create_issue_comment','update_issue','delete_issue','get_issue', 'search_issues']
+tools: [ 'list_issues','githubRepo', 'search', 'add_issue_comment','issue_write','create_issue_comment','update_issue','delete_issue','get_issue', 'search_issues']
 ---
 
 # Refine Requirement or Issue Chat Mode

.github/prompts/awesome-copilot/az-cost-optimize.prompt.md

@@ -179,7 +179,7 @@ This workflow analyzes Infrastructure-as-Code (IaC) files and Azure resources to
 
 ### Step 6: Create Individual Optimization Issues
 **Action**: Create separate GitHub issues for each optimization opportunity. Label them with "cost-optimization" (green color), "azure" (blue color).
-**MCP Tools Required**: `create_issue` for each recommendation
+**MCP Tools Required**: `issue_write` for each recommendation
 **Process**:
 1. **Create Individual Issues** using this template:
 
@@ -230,7 +230,7 @@ This workflow analyzes Infrastructure-as-Code (IaC) files and Azure resources to
 
 ### Step 7: Create EPIC Coordinating Issue
 **Action**: Create master issue to track all optimization work. Label it with "cost-optimization" (green color), "azure" (blue color), and "epic" (purple color).
-**MCP Tools Required**: `create_issue` for EPIC
+**MCP Tools Required**: `issue_write` for EPIC
 **Note about mermaid diagrams**: Ensure you verify mermaid syntax is correct and create the diagrams taking accessibility guidelines into account (styling, colors, etc.).
 **Process**:
 1. **Create EPIC Issue**:

.github/prompts/awesome-copilot/create-github-issue-feature-from-specification.prompt.md

@@ -1,7 +1,7 @@
 ---
 mode: 'agent'
 description: 'Create GitHub Issue for feature request from specification file using feature_request.yml template.'
-tools: ['codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
+tools: ['codebase', 'search', 'github', 'issue_write', 'search_issues', 'update_issue']
 ---
 # Create GitHub Issue from Specification
 
@@ -11,7 +11,7 @@ Create GitHub Issue for the specification at `${file}`.
 
 1. Analyze specification file to extract requirements
 2. Check existing issues using `search_issues`
-3. Create new issue using `create_issue` or update existing with `update_issue`
+3. Create new issue using `issue_write` or update existing with `update_issue`
 4. Use `feature_request.yml` template (fallback to default)
 
 ## Requirements

.github/prompts/awesome-copilot/create-github-issues-feature-from-implementation-plan.prompt.md

@@ -1,7 +1,7 @@
 ---
 mode: 'agent'
 description: 'Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.'
-tools: ['codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
+tools: ['codebase', 'search', 'github', 'issue_write', 'search_issues', 'update_issue']
 ---
 # Create GitHub Issue from Implementation Plan
 
@@ -11,7 +11,7 @@ Create GitHub Issues for the implementation plan at `${file}`.
 
 1. Analyze plan file to identify phases
 2. Check existing issues using `search_issues`
-3. Create new issue per phase using `create_issue` or update existing with `update_issue`
+3. Create new issue per phase using `issue_write` or update existing with `update_issue`
 4. Use `feature_request.yml` or `chore_request.yml` templates (fallback to default)
 
 ## Requirements

.github/prompts/awesome-copilot/create-github-issues-for-unmet-specification-requirements.prompt.md

@@ -1,7 +1,7 @@
 ---
 mode: 'agent'
 description: 'Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.'
-tools: ['codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
+tools: ['codebase', 'search', 'github', 'issue_write', 'search_issues', 'update_issue']
 ---
 # Create GitHub Issues for Unmet Specification Requirements
 
@@ -12,7 +12,7 @@ Create GitHub Issues for unimplemented requirements in the specification at `${f
 1. Analyze specification file to extract all requirements
 2. Check codebase implementation status for each requirement
 3. Search existing issues using `search_issues` to avoid duplicates
-4. Create new issue per unimplemented requirement using `create_issue`
+4. Create new issue per unimplemented requirement using `issue_write`
 5. Use `feature_request.yml` template (fallback to default)
 
 ## Requirements