From 1c6182f3945084ccbbe9ef48cbaece946b41b404 Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Thu, 24 Jul 2025 16:56:24 -0500
Subject: [PATCH 1/8] feat: add initial Copilot instructions and project
 overview

---
 .github/copilot-instructions.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 .github/copilot-instructions.md

diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..9c88107
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,30 @@
+# Copilot Instructions for This Repository
+
+## Project Overview
+This repository is designed for Copilot training, providing hands-on materials, prompts, and configuration files to help contributors and Copilot agents learn, test, and improve their use of GitHub Copilot and related AI tools.
+
+## Folder Structure Summary
+- `docs/` — Main training lessons and documentation for Copilot usage and best practices.
+- `samples/` — Sample applications (e.g., eShop, Orders, SimpleFullStack) for practical exercises and demonstrations.
+- `_schedule/` — Outlines and lesson plans for structured Copilot training sessions.
+- `.github/prompts/` — Custom Copilot chatmodes and agent prompt files (e.g., for C#, Azure Bicep, Security) that define agent behavior and review standards.
+- `package.json`, `README.md` — Project configuration and overview.
+
+## Copilot Agents & Chatmodes
+- **C# Agent**: Enforces C# coding standards, style, and best practices. Use for C# code reviews and generation.
+- **Azure Bicep Assistant**: Specializes in Azure IaC, Bicep, and ARM best practices. Use for infrastructure code and reviews.
+- **Security Review Agent**: Focuses on secure coding, vulnerability detection, and API security. Use for security audits and feedback.
+- **Default Copilot/Chat**: General-purpose Copilot for code suggestions, documentation, and Q&A.
+
+## Main Contributor/Agent Tasks
+- Review and improve code using Copilot agents and provided prompts.
+- Complete training exercises and lessons in `docs/` and `_schedule/`.
+- Generate, review, or update sample code in `samples/` as part of training.
+- Follow conventions and best practices outlined in `.github/prompts/`.
+- Contribute new prompts, lessons, or sample scenarios as needed.
+
+## Intended Audience & Guidelines
+- **Audience**: Developers, trainers, and Copilot agents seeking to learn or teach effective Copilot usage.
+- **Guidelines**: Keep contributions concise, actionable, and aligned with the provided prompts and standards. Avoid unnecessary detail to ensure clarity and minimize token usage.
+
+Refer to the `README.md` and lesson files for more detailed instructions on specific training modules or sample applications.

From 06ee6ed01924a0d070e558c3cb8dbdbec03f9038 Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 10:04:34 -0500
Subject: [PATCH 2/8] feat: add curriculum design and management instructions,
 including gap analysis and audience targeting

---
 .../chatmodes/curriculum-designer.chatmode.md | 45 ++++++++++
 .github/copilot-instructions.md               | 17 +++-
 .../curriculum-gaps.instructions.md           | 52 +++++++++++
 .../curriculum-map.instructions.md            | 41 +++++++++
 .../jupyter_notebooks.instructions.md         | 86 +++++++++++++++++++
 .github/instructions/markdown.instructions.md | 69 +++++++++++++++
 .../target-audience.instructions.md           | 43 ++++++++++
 .github/prompts/assess-relevance.prompt.md    | 19 ++++
 .github/prompts/issue-management.prompt.md    | 20 +++++
 .github/prompts/prompt-creation.prompt.md     | 19 ++++
 .github/prompts/review-curriculum.prompt.md   | 20 +++++
 .github/prompts/search-for-updates.prompt.md  | 20 +++++
 .github/prompts/update-content.prompt.md      | 23 +++++
 13 files changed, 473 insertions(+), 1 deletion(-)
 create mode 100644 .github/chatmodes/curriculum-designer.chatmode.md
 create mode 100644 .github/instructions/curriculum-gaps.instructions.md
 create mode 100644 .github/instructions/curriculum-map.instructions.md
 create mode 100644 .github/instructions/jupyter_notebooks.instructions.md
 create mode 100644 .github/instructions/markdown.instructions.md
 create mode 100644 .github/instructions/target-audience.instructions.md
 create mode 100644 .github/prompts/assess-relevance.prompt.md
 create mode 100644 .github/prompts/issue-management.prompt.md
 create mode 100644 .github/prompts/prompt-creation.prompt.md
 create mode 100644 .github/prompts/review-curriculum.prompt.md
 create mode 100644 .github/prompts/search-for-updates.prompt.md
 create mode 100644 .github/prompts/update-content.prompt.md

diff --git a/.github/chatmodes/curriculum-designer.chatmode.md b/.github/chatmodes/curriculum-designer.chatmode.md
new file mode 100644
index 0000000..3ecc4c7
--- /dev/null
+++ b/.github/chatmodes/curriculum-designer.chatmode.md
@@ -0,0 +1,45 @@
+---
+description: 'Design, review, and improve technical education programs, learning paths, and e-learning content for diverse learners. Expert in instructional design, accessibility, and continuous curriculum improvement.'
+tools: ['changes', 'codebase', 'editFiles', 'fetch', 'githubRepo', 'problems', 'runCommands', 'runNotebooks', 'search', 'usages', 'microsoft-docs', 'add_comment_to_pending_review', 'add_issue_comment', 'create_and_submit_pull_request_review', 'create_branch', 'create_issue', 'create_pull_request', 'get_commit', 'get_discussion', 'get_discussion_comments', 'get_file_contents', 'get_issue', 'get_issue_comments', 'get_pull_request', 'get_pull_request_comments', 'get_pull_request_diff', 'get_pull_request_files', 'get_pull_request_reviews', 'get_pull_request_status', 'get_tag', 'list_branches', 'list_issues', 'list_tags', 'search_code', 'search_issues', 'search_repositories', 'update_issue', 'sequentialthinking']
+---
+
+# Curriculum Designer Chatmode Instructions
+
+## Persona Overview
+You are a world-class curriculum designer and e-learning architect. Your mission is to create engaging, accessible, and effective learning experiences for technical audiences. You break down complex topics, scaffold knowledge, and ensure content is inclusive and up-to-date.
+
+## Core Principles
+- Learner-Centered Design: Prioritize learner needs, backgrounds, and goals.
+- Evidence-Based Instruction: Apply proven instructional design models (ADDIE, Bloom’s Taxonomy, UDL).
+- Accessibility & Inclusivity: Ensure content is accessible to all learners and supports diverse learning styles.
+- Continuous Improvement: Proactively update curriculum based on feedback, trends, and new technologies.
+- Collaboration: Partner with subject matter experts and stakeholders for technical accuracy and pedagogical effectiveness.
+
+## Workflow Guidelines
+1. Information Gathering: Ask clarifying questions about learner profiles, goals, and context before designing content.
+2. Learning Path Design: Scaffold modules from foundational to advanced, using storytelling, analogies, and real-world examples.
+3. Content Creation: Develop interactive, multimedia-rich materials (videos, quizzes, labs, simulations).
+4. Assessment & Feedback: Design formative and summative assessments, apply spaced repetition and retrieval practice.
+5. Accessibility Review: Check for compliance with accessibility standards (e.g., WCAG), and apply UDL principles.
+6. Curriculum Evolution: Integrate new lessons, sunset outdated content, and maintain curriculum coherence.
+7. Stakeholder Engagement: Collaborate with experts, instructors, and product teams.
+
+## Interaction Patterns
+- Start with clarifying questions to reduce ambiguity and understand requirements.
+- Iterate and refine learning paths and modules based on feedback and assessment data.
+- Validate learning outcomes and adapt instruction as needed.
+- Encourage continuous dialogue and improvement.
+
+## Response Style
+- Use clear, supportive, and actionable language.
+- Scaffold explanations and break down complex concepts.
+- Provide examples, analogies, and real-world scenarios.
+- Offer constructive feedback and suggest improvements.
+- Ensure responses are accessible and inclusive.
+
+## Example Prompts
+- Design a beginner-to-intermediate learning path for cloud computing.
+- How can I make this module more accessible for learners with disabilities?
+- Create a formative assessment for a Python basics course.
+- Update the curriculum to include the latest cybersecurity trends.
+- Collaborate with a subject matter expert to review technical accuracy.
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
index 9c88107..480b6f1 100644
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -7,15 +7,21 @@ This repository is designed for Copilot training, providing hands-on materials,
 - `docs/` — Main training lessons and documentation for Copilot usage and best practices.
 - `samples/` — Sample applications (e.g., eShop, Orders, SimpleFullStack) for practical exercises and demonstrations.
 - `_schedule/` — Outlines and lesson plans for structured Copilot training sessions.
-- `.github/prompts/` — Custom Copilot chatmodes and agent prompt files (e.g., for C#, Azure Bicep, Security) that define agent behavior and review standards.
 - `package.json`, `README.md` — Project configuration and overview.
+- `.curriculum-admin/` — Curriculum administration metadata. Contains:
+  - `curriculum-map.md`: Overview of modules, lessons, and their relationships.
+  - `target-audience.md`: Defines learner profiles, starting skill levels, and desired outcomes.
+  - `curriculum-gaps.md`: Identifies missing, weak, or outdated areas in the curriculum.
+  These files are used by Copilot and LLMs to provide rich context for training content analysis, updates, and understanding the learner perspective. They enable more efficient and targeted curriculum improvements by making gaps, audience needs, and curriculum structure explicit.
 
 ## Copilot Agents & Chatmodes
+- **Curriculum Designer Chatmode**: Assists in designing, reviewing, and updating curriculum content. Provides recommendations for lesson structure, learning outcomes, and gap analysis based on `.curriculum-admin` files.
 - **C# Agent**: Enforces C# coding standards, style, and best practices. Use for C# code reviews and generation.
 - **Azure Bicep Assistant**: Specializes in Azure IaC, Bicep, and ARM best practices. Use for infrastructure code and reviews.
 - **Security Review Agent**: Focuses on secure coding, vulnerability detection, and API security. Use for security audits and feedback.
 - **Default Copilot/Chat**: General-purpose Copilot for code suggestions, documentation, and Q&A.
 
+
 ## Main Contributor/Agent Tasks
 - Review and improve code using Copilot agents and provided prompts.
 - Complete training exercises and lessons in `docs/` and `_schedule/`.
@@ -27,4 +33,13 @@ This repository is designed for Copilot training, providing hands-on materials,
 - **Audience**: Developers, trainers, and Copilot agents seeking to learn or teach effective Copilot usage.
 - **Guidelines**: Keep contributions concise, actionable, and aligned with the provided prompts and standards. Avoid unnecessary detail to ensure clarity and minimize token usage.
 
+## Use of `.curriculum-admin` by Copilot & LLMs
+
+When performing training content analysis, updates, or reviewing curriculum relevance, Copilot agents and LLMs use the `.curriculum-admin` files to:
+- Understand the current curriculum structure and coverage (`curriculum-map.md`).
+- Align content and recommendations with learner needs and desired outcomes (`target-audience.md`).
+- Identify and prioritize gaps for improvement (`curriculum-gaps.md`).
+
+These files provide essential context for delivering high-quality, learner-centered training and help minimize unnecessary token usage by focusing analysis and updates on what matters most.
+
 Refer to the `README.md` and lesson files for more detailed instructions on specific training modules or sample applications.
diff --git a/.github/instructions/curriculum-gaps.instructions.md b/.github/instructions/curriculum-gaps.instructions.md
new file mode 100644
index 0000000..3c5df39
--- /dev/null
+++ b/.github/instructions/curriculum-gaps.instructions.md
@@ -0,0 +1,52 @@
+---
+description: "Identifies missing, weak, or outdated areas in the current curriculum. It supports strategic planning, prioritization, and continuous improvement by providing a clear, actionable summary of gaps and their impact."
+applyTo: ".curriculum-admin/curriculum-gaps.md"
+---
+# Curriculum Gaps File Instructions
+
+## Purpose
+The curriculum gaps file identifies missing, weak, or outdated areas in the current curriculum. It supports strategic planning, prioritization, and continuous improvement by providing a clear, actionable summary of gaps and their impact.
+
+## Definition of Gaps
+Gaps are areas where the current curriculum-map does not fully address the desired outcomes or skill expectations of the target audience. A gap exists when, after completing all curriculum modules, the audience may still lack required knowledge, skills, or familiarity with a topic that is expected for their role or goals. Gaps are identified by comparing the curriculum-map against the target audience’s needs and desired training outcomes.
+
+## Related Documents
+
+The identification of curriculum gaps relies on two key related documents:
+
+- **curriculum-map.md**: Outlines the structure, modules, and intended learning outcomes of the curriculum. Used as the baseline for comparison to determine coverage and alignment with goals.
+- **target-audience.md**: Defines the roles, skill levels, and expectations of the intended learners. Provides context for what knowledge and skills are required for success.
+
+Gaps are determined by analyzing the curriculum-map against the needs and expectations described in the target-audience.md. This ensures that gap identification is contextual, actionable, and relevant to both curriculum design and learner outcomes.
+
+
+## Structure
+- **Header:** Title and last updated date.
+- **Gap List:**
+  - Gap description (concise and specific)
+  - Impact on learning outcomes or audience
+  - Evidence/rationale (e.g., feedback, assessment data, issue references)
+  - Priority (high/medium/low)
+  - Proposed actions or next steps
+- **Summary Table (optional):** Quick reference for major gaps and priorities.
+- **Links:** Reference related issues, curriculum map entries, and audience profiles.
+
+## Update Conditions
+- When new gaps are identified via feedback, assessment, or curriculum review.
+- When gaps are resolved or reprioritized.
+- After major curriculum changes or refactorings.
+
+## Update Process
+1. Review feedback, issues, and curriculum map.
+2. Add, update, or resolve gap entries as needed.
+3. Record update in file header.
+
+## Reporting Outputs
+- Summarize changes in chat (e.g., "Added gap for Module Z, resolved gap for Lesson Y").
+- The updated file is the primary artifact; chat output should reference the file and highlight key changes.
+
+## Standards
+- Be concise, specific, and evidence-based in describing gaps.
+- Prioritize gaps based on impact and urgency.
+- Regularly review and update to reflect current curriculum state.
+- Cross-reference with curriculum map and audience files for context.
diff --git a/.github/instructions/curriculum-map.instructions.md b/.github/instructions/curriculum-map.instructions.md
new file mode 100644
index 0000000..5be4269
--- /dev/null
+++ b/.github/instructions/curriculum-map.instructions.md
@@ -0,0 +1,41 @@
+---
+description: "Standards and guidelines for creating and updating the curriculum map with Markdown files"
+applyTo: ".curriculum-admin/curriculum-map.md"
+---
+# Curriculum Map File Instructions
+
+## Purpose
+The curriculum map provides a clear, structured overview of all modules, lessons, and their relationships within the training program. It is the primary reference for understanding curriculum coverage, sequencing, and identifying gaps.
+
+## Structure
+- **Header:** Title and last updated date.
+- **Audience Reference:** Link or summary from `target-audience.md`.
+- **Module List:**
+  - Module name
+  - Description
+  - Prerequisites
+  - Learning outcomes
+  - Lessons (with brief descriptions)
+- **Visual Map (optional):** Diagram or table showing relationships and progression.
+- **Gap References:** Link to `curriculum-gaps.md` for identified gaps.
+
+## Update Conditions
+- When new modules/lessons are added, removed, or restructured.
+- When learning outcomes or prerequisites change.
+- After major curriculum reviews or refactorings.
+
+## Update Process
+1. Review recent curriculum changes and issues.
+2. Update module/lesson lists and relationships.
+3. Cross-check with `target-audience.md` and `curriculum-gaps.md`.
+4. Record update in file header.
+
+## Reporting Outputs
+- When updating, summarize changes in chat (e.g., "Added Module X, updated outcomes for Module Y").
+- The updated file itself is the primary artifact; chat output should reference the file and highlight key changes.
+
+## Standards
+- Keep content concise, clear, and actionable.
+- Use consistent formatting for modules and lessons.
+- Ensure all modules/lessons have learning outcomes and prerequisites listed.
+- Regularly cross-reference with audience and gap files.
diff --git a/.github/instructions/jupyter_notebooks.instructions.md b/.github/instructions/jupyter_notebooks.instructions.md
new file mode 100644
index 0000000..d4b1e1d
--- /dev/null
+++ b/.github/instructions/jupyter_notebooks.instructions.md
@@ -0,0 +1,86 @@
+---
+description: "Standards and guidelines for creating effective curriculum with Jupyter Notebooks"
+applyTo: "**/*.{lesson,curriculum,training}.ipynb"
+---
+
+# Jupyter Notebook Curriculum Standards & Guidelines
+
+## Structure & Organization
+- Start with a markdown cell for lesson title, objectives, author, date, and version.
+- Use markdown cells for explanations, instructions, and summaries.
+- Use code cells for hands-on exercises, demonstrations, and assessments.
+- Organize content into logical sections: introduction, activities, assessment, summary.
+
+## Formatting Best Practices
+- Add comments and docstrings in code cells for clarity.
+- Provide sample outputs and troubleshooting tips.
+- Use images, tables, and links to enrich content.
+- Use headings and lists in markdown cells for navigation and scannability.
+
+## Accessibility & Inclusivity
+- Use clear, inclusive language and avoid jargon.
+- Provide alt text for all images and diagrams.
+- Ensure logical cell order and semantic structure for screen readers.
+
+## Content Quality
+- Write concise, actionable instructions and explanations.
+- Reference external resources and further reading for deeper learning.
+- Include real-world examples and analogies.
+
+## Documentation Hygiene
+- Document metadata (author, date, version) in the first cell.
+- Keep notebooks up-to-date and sunset outdated material.
+- Use consistent file naming: lowercase, hyphens, descriptive names (e.g., `data-visualization.ipynb`).
+
+## Example Template
+```json
+{
+  "cells": [
+    {
+      "cell_type": "markdown",
+      "metadata": {"language": "markdown"},
+      "source": [
+        "# Lesson Title\n",
+        "**Objectives:**\n",
+        "- Understand X\n",
+        "- Apply Y\n",
+        "**Author:** Name\n",
+        "**Date:** YYYY-MM-DD\n",
+        "**Version:** 1.0\n"
+      ]
+    },
+    {
+      "cell_type": "markdown",
+      "metadata": {"language": "markdown"},
+      "source": [
+        "## Introduction\n",
+        "Brief overview..."
+      ]
+    },
+    {
+      "cell_type": "code",
+      "metadata": {"language": "python"},
+      "source": [
+        "# Example code cell\n",
+        "print('Hello, world!')"
+      ]
+    },
+    {
+      "cell_type": "markdown",
+      "metadata": {"language": "markdown"},
+      "source": [
+        "## Assessment\n",
+        "- Complete the exercise"
+      ]
+    },
+    {
+      "cell_type": "markdown",
+      "metadata": {"language": "markdown"},
+      "source": [
+        "## Further Reading\n",
+        "- [Resource Name](https://example.com)"
+      ]
+    }
+  ]
+}
+```
\ No newline at end of file
diff --git a/.github/instructions/markdown.instructions.md b/.github/instructions/markdown.instructions.md
new file mode 100644
index 0000000..1528607
--- /dev/null
+++ b/.github/instructions/markdown.instructions.md
@@ -0,0 +1,69 @@
+---
+description: "Standards and guidelines for creating effective curriculum with Markdown files"
+applyTo: "**/*.{lesson,curriculum,training}.md"
+---
+
+# Markdown Curriculum Standards & Guidelines
+
+## Structure & Organization
+- Use clear, hierarchical headings (`#`, `##`, `###`) for navigation and table of contents.
+- Begin with a summary section: learning objectives, prerequisites, and outcomes.
+- Organize content with short paragraphs, bullet points, and numbered lists for scannability.
+- Use task lists (`- [ ]`) for actionable steps or checklists.
+
+## Formatting Best Practices
+- Use fenced code blocks (triple backticks) with language identifiers for syntax highlighting.
+- Avoid command prompts (e.g., `$`) in code examples to improve copy-paste usability.
+- Use descriptive links: `[link text](URL)` and ensure URLs are valid.
+- Add images with descriptive alt text: `![alt text](image URL)`.
+- Use tables for structured data and align columns consistently.
+- Break lines at 80 characters for readability.
+
+## Accessibility & Inclusivity
+- Use inclusive, clear language and avoid jargon.
+- Provide alt text for all images and diagrams.
+- Ensure color contrast and avoid relying solely on color for meaning.
+- Use semantic headings and lists for screen reader compatibility.
+
+## Content Quality
+- Write concise, actionable instructions and explanations.
+- Reference external resources and further reading for deeper learning.
+- Document troubleshooting tips and common issues.
+- Include examples, analogies, and real-world scenarios.
+
+## Documentation Hygiene
+- Add metadata (author, date, version) at the top if needed.
+- Keep content up-to-date and sunset outdated material.
+- Use consistent file naming: lowercase, hyphens, descriptive names (e.g., `python-basics.md`).
+
+## Example Template
+```markdown
+# Lesson Title
+
+**Objectives:**
+- Understand X
+- Apply Y
+
+**Prerequisites:**
+- Basic knowledge of Z
+
+---
+
+## Introduction
+Brief overview...
+
+## Step-by-step Instructions
+1. ...
+2. ...
+
+## Code Example
+```python
+print("Hello, world!")
+```
+
+## Assessment
+- [ ] Complete the exercise
+
+## Further Reading
+- [Resource Name](https://example.com)
+```
\ No newline at end of file
diff --git a/.github/instructions/target-audience.instructions.md b/.github/instructions/target-audience.instructions.md
new file mode 100644
index 0000000..264fa53
--- /dev/null
+++ b/.github/instructions/target-audience.instructions.md
@@ -0,0 +1,43 @@
+---
+description: "Standards and guidelines for creating effective target audience description files using Markdown"
+applyTo: ".curriculum-admin/target-audience.md"
+---
+# Target Audience File Instructions
+
+## Purpose
+The target audience file defines the learner profiles, starting skill levels, and desired end-state outcomes for the curriculum. It ensures curriculum design and updates are aligned with actual learner needs and organizational goals.
+
+## Structure
+- **Header:** Title and last updated date.
+- **Audience Profiles:**
+  - Role(s) (e.g., developer, analyst, manager)
+  - Background/starting skill level
+  - Prior experience (if relevant)
+  - Learning preferences or accessibility needs
+- **Desired Outcomes:**
+  - Skills and competencies to be achieved
+  - Certifications or milestones (if applicable)
+  - Example scenarios/use cases
+- **Organizational Variations:**
+  - Notes on specific organizations or cohorts (if relevant)
+  - Customization guidance
+
+## Update Conditions
+- When curriculum is adapted for a new audience or organization.
+- When learner needs or desired outcomes change.
+- After major feedback or assessment cycles.
+
+## Update Process
+1. Gather new audience data or requirements.
+2. Update profiles and outcomes as needed.
+3. Record update in file header.
+
+## Reporting Outputs
+- Summarize changes in chat (e.g., "Updated audience profile for new cohort").
+- The updated file is the primary artifact; chat output should reference the file and highlight key changes.
+
+## Standards
+- Be specific and actionable in describing audience and outcomes.
+- Use clear, inclusive language.
+- Regularly review and update to reflect current learner needs.
+- Cross-reference with curriculum map and gap files for alignment.
diff --git a/.github/prompts/assess-relevance.prompt.md b/.github/prompts/assess-relevance.prompt.md
new file mode 100644
index 0000000..0005b87
--- /dev/null
+++ b/.github/prompts/assess-relevance.prompt.md
@@ -0,0 +1,19 @@
+# assess-relevance Workflow Prompt
+
+## Objective
+Grade the relevance of new features and recommend inclusion in the curriculum.
+
+## Steps
+1. For each new feature, assess its relevance to the curriculum.
+2. Assign a relevance grade (percentage %) and a recommendation (yes/no).
+3. Output a table for human review and decision-making.
+
+## Tools
+- Feature assessment rubric
+- Curriculum map
+
+## Output
+- Feature relevance table with grades and recommendations
+
+## Example Prompt
+"For each new feature identified, assess its relevance to the current curriculum. Assign a relevance grade (percentage %) and a recommendation (yes/no) for inclusion. Present results in a table for review."
diff --git a/.github/prompts/issue-management.prompt.md b/.github/prompts/issue-management.prompt.md
new file mode 100644
index 0000000..829483b
--- /dev/null
+++ b/.github/prompts/issue-management.prompt.md
@@ -0,0 +1,20 @@
+# issue-management Workflow Prompt
+
+## Objective
+Create, tag, and track GitHub issues for each new content item or lesson to add, update, or remove.
+
+## Steps
+1. For each new content item, create a separate GitHub issue in the training content repo.
+2. Tag issues with "content" and a specific action tag: "add content", "update content", or "remove content".
+3. Track issue progress and update status as work is completed.
+
+## Tools
+- GitHub issues
+- Issue tagging system
+
+## Output
+- List of issues for new, updated, or removed content
+- Issue status updates
+
+## Example Prompt
+"For each new content item or lesson, create a GitHub issue in the training content repo. Tag the issue appropriately and track its progress until completion."
diff --git a/.github/prompts/prompt-creation.prompt.md b/.github/prompts/prompt-creation.prompt.md
new file mode 100644
index 0000000..0100ffe
--- /dev/null
+++ b/.github/prompts/prompt-creation.prompt.md
@@ -0,0 +1,19 @@
+# prompt-creation Workflow Prompt
+
+## Objective
+Draft effective prompts for new or updated curriculum content, following best practices and examples from GitHub documentation and awesome-copilot.
+
+## Steps
+1. Review examples of effective prompts from `github/docs` and `github/awesome-copilot`.
+2. Draft new prompts for each content item or lesson, ensuring clarity and instructional value.
+3. Format prompts according to Markdown curriculum standards.
+
+## Tools
+- GitHub repo tool
+- Example prompt repositories
+
+## Output
+- Well-formed prompts for new/updated content
+
+## Example Prompt
+"Draft a prompt for a new lesson based on the latest GitHub Copilot feature. Use examples from `github/docs` and `github/awesome-copilot` to ensure clarity and effectiveness. Format according to curriculum standards."
diff --git a/.github/prompts/review-curriculum.prompt.md b/.github/prompts/review-curriculum.prompt.md
new file mode 100644
index 0000000..56613f5
--- /dev/null
+++ b/.github/prompts/review-curriculum.prompt.md
@@ -0,0 +1,20 @@
+# review-curriculum Workflow Prompt
+
+## Objective
+Map the current curriculum and identify gaps or outdated content.
+
+## Steps
+1. Review all existing lessons, modules, and content structure.
+2. Summarize curriculum coverage and identify missing or outdated topics.
+3. Output a curriculum map and gap analysis.
+
+## Tools
+- Curriculum repository
+- Documentation review
+
+## Output
+- Curriculum map/summary
+- List of gaps and outdated items
+
+## Example Prompt
+"Review the current training curriculum. Summarize the coverage, identify any gaps or outdated topics, and provide a curriculum map for reference."
diff --git a/.github/prompts/search-for-updates.prompt.md b/.github/prompts/search-for-updates.prompt.md
new file mode 100644
index 0000000..cc4f1dc
--- /dev/null
+++ b/.github/prompts/search-for-updates.prompt.md
@@ -0,0 +1,20 @@
+# search-for-updates Workflow Prompt
+
+## Objective
+Identify and summarize new features or updates from GitHub documentation repos (VS Code, GitHub Copilot).
+
+## Steps
+1. Search official documentation repos for recent updates.
+2. List new features, changes, or deprecations.
+3. Summarize each item with a brief description and source link.
+4. Output a table of new content items for review.
+
+## Tools
+- GitHub repo tool
+- Documentation search
+
+## Output
+- Table of new/updated features with links and descriptions
+
+## Example Prompt
+"Search the GitHub documentation repos for VS Code and GitHub Copilot. List all new features or updates from the past month, including a brief description and source link for each."
diff --git a/.github/prompts/update-content.prompt.md b/.github/prompts/update-content.prompt.md
new file mode 100644
index 0000000..7ad596f
--- /dev/null
+++ b/.github/prompts/update-content.prompt.md
@@ -0,0 +1,23 @@
+# update-content Workflow Prompt
+
+## Objective
+Create, update, or remove curriculum content based on GitHub issues and feature assessments.
+
+## Steps
+1. Work on assigned GitHub issues for content updates.
+2. Create, update, or remove lessons/modules as described in the issue.
+3. Update issue progress via comments and close when complete.
+4. Submit changes via feature branches and pull requests.
+
+## Tools
+- GitHub issues
+- Curriculum repository
+- Feature branch workflow
+
+## Output
+- Updated curriculum content
+- Closed issues
+- Pull requests for curriculum changes
+
+## Example Prompt
+"For each assigned GitHub issue, create, update, or remove the relevant curriculum content. Document progress in issue comments, submit changes via a feature branch, and close the issue when complete."

From e2d4ba337b4e04106de2ca18ef49700169963948 Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 10:46:39 -0500
Subject: [PATCH 3/8] feat: create target audience profile and generator prompt
 for curriculum

---
 .curriculum-admin/target-audience.md          | 53 +++++++++++++++++++
 .../generate-target-audience.prompt.md        | 48 +++++++++++++++++
 2 files changed, 101 insertions(+)
 create mode 100644 .curriculum-admin/target-audience.md
 create mode 100644 .github/prompts/generate-target-audience.prompt.md

diff --git a/.curriculum-admin/target-audience.md b/.curriculum-admin/target-audience.md
new file mode 100644
index 0000000..5f2f351
--- /dev/null
+++ b/.curriculum-admin/target-audience.md
@@ -0,0 +1,53 @@
+# Neudesic Internal Consultant Audience Profile
+_Last updated: July 25, 2025_
+
+## Audience Profiles
+
+- **Primary Roles:** Internal Neudesic consultants, including developers, architects, and technical leads.
+- **Starting Skill Level & Background:** Highly skilled in software development, cloud, and modern engineering practices. Most have strong experience with enterprise projects, agile methodologies, and technical problem-solving.
+- **Prior Experience:** Extensive development background but little to no familiarity with GitHub Copilot usage, prompt engineering, or AI-assisted development workflows.
+- **Learning Preferences & Accessibility Needs:**
+  - Prefer hands-on, scenario-based, and self-paced learning.
+  - Value real-world examples, code walkthroughs, and practical labs.
+  - Inclusive of diverse backgrounds, learning styles, and accessibility needs (e.g., visual aids, screen reader compatibility, clear language, support for neurodiversity).
+  - May require support for remote/virtual training and asynchronous access.
+- **Example Personas:**
+  - "Priya," a senior developer who excels at building cloud-native apps but is new to Copilot and wants to boost productivity.
+  - "Alex," a technical lead who mentors teams and seeks to evaluate Copilot for adoption across projects.
+  - "Jordan," an architect who designs solutions and wants to understand Copilot’s impact on code quality and workflow.
+
+## Desired Outcomes
+
+- **Skills & Competencies:**
+  - Confidently use GitHub Copilot for code generation, documentation, and testing.
+  - Apply prompt engineering techniques to improve Copilot results.
+  - Integrate Copilot into daily development workflows and team practices.
+  - Understand Copilot’s limitations, security implications, and best practices.
+- **Certifications/Milestones:**
+  - Complete Copilot training modules and hands-on labs.
+  - Demonstrate proficiency via formative assessments and real-world scenarios.
+- **Real-World Scenarios/Use Cases:**
+  - Accelerate feature development and bug fixes using Copilot.
+  - Improve code review and documentation processes.
+  - Evaluate Copilot’s fit for different project types and team structures.
+
+## Organizational Variations
+
+- **Specific Cohorts:**
+  - Neudesic internal teams, including consulting, delivery, and innovation groups.
+- **Customization Needs:**
+  - May tailor examples, labs, and scenarios to reflect Neudesic’s technology stack, client environments, and project workflows.
+
+## Update Process
+
+- **Update Triggers:**
+  - When curriculum is adapted for new Neudesic teams or roles.
+  - When feedback indicates changing learner needs or desired outcomes.
+  - After major curriculum or technology updates.
+- **Update Steps:**
+  1. Gather new audience data or requirements from stakeholders and feedback.
+  2. Update profiles, outcomes, and organizational notes as needed.
+  3. Record update in file header with date and summary.
+
+---
+_This file should be reviewed and updated regularly to ensure alignment with current learner needs and organizational goals. Summarize changes in chat and record updates in the header._
diff --git a/.github/prompts/generate-target-audience.prompt.md b/.github/prompts/generate-target-audience.prompt.md
new file mode 100644
index 0000000..0cc4d89
--- /dev/null
+++ b/.github/prompts/generate-target-audience.prompt.md
@@ -0,0 +1,48 @@
+---
+# Target Audience Generator Prompt
+
+## Objective
+Guide the user through a structured interview to build or update a detailed, actionable, and inclusive target audience description file for the curriculum. The output must be a Markdown file at `.curriculum-admin/target-audience.md`, following the standards in `target-audience.instructions.md`.
+
+## Instructions
+1. Check if `.curriculum-admin/target-audience.md` already exists:
+   - If it exists, review its contents and ask if any changes or updates are needed, or if any required sections are missing.
+   - If it does not exist, guide the user through the full interview below to create a new file.
+2. Ask each question below, encouraging specific, example-rich, and inclusive answers. Use clear language and reference curriculum map/gap files for alignment.
+3. Format the output as a Markdown file with sections for Header, Audience Profiles, Desired Outcomes, and Organizational Variations.
+4. Remind the user to review and update the file regularly, summarizing changes in chat.
+
+## Interview Questions
+- **Header**
+  - What is the title for this audience profile?
+  - What is the last updated date?
+
+- **Audience Profiles**
+  - What are the primary roles of your learners (e.g., developer, analyst, manager)?
+  - What is their starting skill level and background?
+  - Do they have any relevant prior experience?
+  - What are their learning preferences or accessibility needs (e.g., disabilities, language, hands-on, visual, self-paced)?
+  - Can you provide example personas or scenarios for typical learners?
+
+- **Desired Outcomes**
+  - What skills and competencies should learners achieve?
+  - Are there certifications or milestones they should reach?
+  - What real-world scenarios or use cases should they be able to handle after training?
+
+- **Organizational Variations**
+  - Are there specific organizations or cohorts this curriculum serves?
+  - Is any customization needed for these groups?
+
+- **Update Process**
+  - How will you know when the audience profile needs updating?
+  - What process will you follow to update it?
+
+## Standards & Tips
+- Be specific and actionable in describing audience and outcomes.
+- Use clear, inclusive language and provide examples/analogies.
+- Regularly review and update to reflect current learner needs.
+- Cross-reference with curriculum map and gap files for alignment.
+- Summarize changes in chat and record updates in the file header.
+
+## Output
+A well-structured Markdown file at `.curriculum-admin/target-audience.md` containing all sections above, formatted according to the instructions.

From 91ed9772c8514465c72d34c807431116d201d057 Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 12:09:32 -0500
Subject: [PATCH 4/8] feat: add comprehensive curriculum gap analysis and
 curriculum map prompts, including actionable recommendations and updates for
 improved curriculum alignment

---
 .curriculum-admin/curriculum-gaps.md          | 47 +++++++++++++
 .curriculum-admin/curriculum-map.md           | 52 ++++++++++++++
 .../prompts/generate-curriculum-map.prompt.md | 51 ++++++++++++++
 .../identify-curriculum-gaps.prompt.md        | 68 +++++++++++++++++++
 .github/prompts/search-for-updates.prompt.md  | 21 ++++--
 5 files changed, 233 insertions(+), 6 deletions(-)
 create mode 100644 .curriculum-admin/curriculum-gaps.md
 create mode 100644 .curriculum-admin/curriculum-map.md
 create mode 100644 .github/prompts/generate-curriculum-map.prompt.md
 create mode 100644 .github/prompts/identify-curriculum-gaps.prompt.md

diff --git a/.curriculum-admin/curriculum-gaps.md b/.curriculum-admin/curriculum-gaps.md
new file mode 100644
index 0000000..c06db00
--- /dev/null
+++ b/.curriculum-admin/curriculum-gaps.md
@@ -0,0 +1,47 @@
+
+# Curriculum Gap Analysis
+
+### Limited Coverage of Advanced Copilot Agent Workflows
+
+- **Description:** The curriculum briefly mentions advanced Copilot Agent features but lacks in-depth modules on workflow automation, integration, and scaling.
+- **Impact:** Technical leads and architects cannot fully leverage Copilot for automation and advanced project scenarios.
+- **Suggested Action:** Add dedicated modules and labs for advanced Copilot Agent workflows and integrations.
+- **Priority:** High
+- **Linked Curriculum Areas:** docs/8-using-github-copilot-agent.md, target-audience: Technical Leads, Architects
+- **Tags:** content, add-content
+
+### Insufficient Real-World Prompt Engineering Labs
+
+- **Description:** Prompt engineering labs do not include enough iterative, scenario-based exercises for hands-on learning and refinement.
+- **Impact:** Learners miss opportunities to practice and master prompt engineering in realistic contexts.
+- **Suggested Action:** Expand labs with more real-world scenarios and iterative refinement exercises.
+- **Priority:** High
+- **Linked Curriculum Areas:** _schedule/02-prompt_engineering.md, target-audience: All Learners
+- **Tags:** content, update-content
+
+### Accessibility and Inclusivity Gaps
+
+- **Description:** Accessibility practices are present but need expansion (e.g., more visual aids, alt text, scenario variety for neurodiverse learners).
+- **Impact:** Neurodiverse and visually impaired learners may struggle to engage fully with the curriculum.
+- **Suggested Action:** Enhance accessibility by adding diagrams, alt text, and scenario-based labs.
+- **Priority:** Medium
+- **Linked Curriculum Areas:** All modules, target-audience: Diverse Learners
+- **Tags:** content, update-content
+
+### Lack of Explicit Assessment and Feedback Mechanisms
+
+- **Description:** The curriculum does not describe formative or summative assessments to validate learner proficiency and provide feedback.
+- **Impact:** Learners and instructors lack clear measures of progress and competency.
+- **Suggested Action:** Add formative and summative assessments to each module, including quizzes, labs, and scenario-based evaluations.
+- **Priority:** High
+- **Linked Curriculum Areas:** All modules, target-audience: All Learners
+- **Tags:** content, add-content
+
+### Overlap Between Best Practices and Design Patterns
+
+- **Description:** Some best practices content overlaps with design patterns, causing potential confusion.
+- **Impact:** Learners may not clearly distinguish between general best practices and specific design patterns.
+- **Suggested Action:** Merge or clarify distinctions between best practices and design pattern modules.
+- **Priority:** Medium
+- **Linked Curriculum Areas:** docs/6-best-practices-with-copilot.md, _schedule/03-design_patterns.md, target-audience: All Learners
+- **Tags:** content, update-content
diff --git a/.curriculum-admin/curriculum-map.md b/.curriculum-admin/curriculum-map.md
new file mode 100644
index 0000000..d31dbd0
--- /dev/null
+++ b/.curriculum-admin/curriculum-map.md
@@ -0,0 +1,52 @@
+# GitHub Copilot Curriculum Map
+_Last updated: July 25, 2025_
+
+## Audience Reference
+See [target-audience.md](./target-audience.md) for detailed learner profiles, skill levels, and desired outcomes.
+
+## Module List & Progression
+
+| Module | Description | Prerequisites | Learning Outcomes | Lessons |
+|--------|-------------|---------------|-------------------|---------|
+| Setup & Installation | Account setup, IDE integration, Copilot CLI/web, troubleshooting. | None | Install and configure Copilot tools; resolve setup issues. | 1. [Installing and Configuring GitHub Copilot](../docs/1-installing-copilot.md) |
+| Introduction to Copilot | Overview of Copilot, LLMs, tools, capabilities, limitations. | Setup & Installation | Understand Copilot’s role, models, and responsible usage. | 2. [Getting Started with GitHub Copilot](../_schedule/01-github_copilot.md) |
+| Development with Copilot | Hands-on use of Copilot features for code generation, refactoring, CLI, chat, edits. | Introduction to Copilot | Use Copilot for code, refactoring, and CLI tasks. | 3. [Development with Copilot](../docs/2-development-with-copilot.md) |
+| Testing with Copilot | Create and improve unit/integration tests using Copilot Edits and features. | Development with Copilot | Enhance test projects, generate and refactor tests. | 4. [Testing with Copilot](../docs/3-testing-with-copilot.md) |
+| Documentation with Copilot | Generate code/project/API documentation using Copilot Chat and Edits. | Development with Copilot | Create/refine documentation, write OpenAPI specs. | 5. [Creating Documentation with Copilot](../docs/4-creating-documentation-with-copilot.md) |
+| DevOps with Copilot | Build pipelines, deployment workflows, containerization, K8s manifests with Copilot. | Development with Copilot | Implement CI/CD, containerization, cloud deployment. | 6. [DevOps with Copilot](../docs/5-devops-with-copilot.md) |
+| Copilot Best Practices | Context, prompt engineering, coding standards, chat/edits usage. | All previous modules | Apply best practices for Copilot usage and prompt writing. | 7. [Best Practices with Copilot](../docs/6-best-practices-with-copilot.md) |
+| Hot Keys & Commands | Reference for Copilot shortcuts, chat participants, slash commands. | None | Efficient navigation and usage of Copilot features. | 8. [Hot Keys and Commands](../docs/7-hot-keys-and-commands.md) |
+| Copilot Agent | Advanced agent features, automation, multi-step reasoning, project scaffolding. | All previous modules | Use Copilot Agent for advanced tasks and automation. | 9. [Using GitHub Copilot Agent](../docs/8-using-github-copilot-agent.md) |
+| Design Patterns & Prompt Engineering | Scaffolding, incremental work, prompt writing, role prompting, TDD, documentation-driven design. | All previous modules | Structure projects, write effective prompts, apply design patterns. | 10. [Prompt Engineering](../_schedule/02-prompt_engineering.md), 11. [Design Patterns](../_schedule/03-design_patterns.md) |
+
+## Visual Progression Map
+
+```
+Setup & Installation → Introduction → Development → Testing → Documentation → DevOps → Best Practices → Hot Keys → Agent → Design Patterns/Prompt Engineering
+```
+
+## Accessibility & Inclusivity
+- Content uses clear, inclusive language and supports diverse learning styles.
+- Lessons include hands-on labs, real-world scenarios, and visual aids.
+- Materials are compatible with screen readers and remote/asynchronous access.
+- Recommendations: Add more visual diagrams, alt text for images, and scenario-based labs for neurodiverse learners.
+
+## Gap & Redundancy Analysis
+- No explicit curriculum-gaps file found; inferred gaps:
+  - Limited coverage of advanced Copilot Agent workflows and integrations.
+  - Need for deeper prompt engineering labs and real-world scenarios.
+  - Accessibility practices could be expanded (e.g., more visual aids, alt text, scenario variety).
+  - Redundancy: Some best practices overlap with design patterns; consider merging or clarifying distinctions.
+
+## Actionable Recommendations
+- Add advanced Copilot Agent and workflow integration modules.
+- Expand prompt engineering labs with more real-world scenarios and iterative refinement exercises.
+- Enhance accessibility: add diagrams, alt text, and scenario-based labs.
+- Regularly review and update modules for new Copilot features and audience feedback.
+- Merge overlapping best practices and design pattern content for clarity.
+
+## References
+- [Target Audience](./target-audience.md)
+- [Curriculum Map Instructions](../.github/instructions/curriculum-map.instructions.md)
+- [Markdown Standards](../.github/instructions/markdown.instructions.md)
+- [Jupyter Notebook Standards](../.github/instructions/jupyter_notebooks.instructions.md)
diff --git a/.github/prompts/generate-curriculum-map.prompt.md b/.github/prompts/generate-curriculum-map.prompt.md
new file mode 100644
index 0000000..fc22c76
--- /dev/null
+++ b/.github/prompts/generate-curriculum-map.prompt.md
@@ -0,0 +1,51 @@
+# Curriculum Map Generator Prompt
+
+## Objective
+Generate a comprehensive, actionable curriculum map in Markdown format at `.curriculum-admin/curriculum-map.md`. The map should summarize all curriculum items, their relationships, progression, gaps, and alignment with audience needs, using best practices in instructional design.
+
+## Tools
+Always use sequential thinking for creating the curriculum map
+
+## Steps
+1. **Review Sources:**
+   - If it exists, analyze the current curriculum map in `.curriculum-admin/curriculum-map.md`.
+   - Scan the entire codebase for curriculum content, lessons, modules, and documentation.
+   - Identify curriculum folders and files using conventions, configuration files (e.g., `copilot-instructions.md`), and documentation (e.g., `README.md`).
+   - Include any other documentation describing the training or curriculum structure.
+   - Read the instructions for creating and updating curriculum maps at /.github/instructions/curriculum-map.instructions.md
+
+2. **Extract & Organize Curriculum Items:**
+   - List all modules, lessons, and training materials.
+   - For each item, summarize its purpose and learning outcomes.
+   - Map relationships and progression between items (e.g., prerequisites, recommended order).
+
+3. **Gap & Redundancy Analysis:**
+   - Identify missing, weak, or outdated areas in the curriculum.
+   - Highlight overlaps or redundancies.
+   - Recommend areas for improvement or expansion.
+
+
+4. **Accessibility & Inclusivity:**
+   - Check for accessibility and inclusivity in curriculum structure and content.
+   - Suggest improvements to support diverse learning styles and needs.
+
+5. **Actionable Recommendations:**
+   - Provide clear, prioritized recommendations for curriculum improvement.
+   - Scaffold suggestions from foundational to advanced.
+
+6. **Output Formatting:**
+   - Format the curriculum map as a well-organized Markdown file at `.curriculum-admin/curriculum-map.md`.
+   - Use clear, learner-centered language and actionable structure.
+   - Include tables, lists, and diagrams as appropriate for clarity.
+
+## Best Practices
+- Apply instructional design principles (e.g., ADDIE, Bloom’s Taxonomy, UDL).
+- Use examples and analogies where helpful.
+- Ensure the map is easy to update and maintain.
+- Avoid hardcoding file/folder names; adapt to repo conventions.
+- Make recommendations concise and actionable.
+
+## Example Output
+Provide a sample curriculum map section, showing modules, lessons, relationships, gaps, and recommendations.
+
+---
diff --git a/.github/prompts/identify-curriculum-gaps.prompt.md b/.github/prompts/identify-curriculum-gaps.prompt.md
new file mode 100644
index 0000000..17ce6c6
--- /dev/null
+++ b/.github/prompts/identify-curriculum-gaps.prompt.md
@@ -0,0 +1,68 @@
+# Curriculum Gap Analysis Prompt
+
+## Objective
+Generate a curriculum gap analysis by reviewing the current curriculum-map and target-audience files. Output actionable findings in `.curriculum-admin/curriculum-gaps.md` to drive continuous improvement and GitHub issue creation.
+
+## Tools
+Always use sequential thinking for analyzing curriculum and generating the curriculum-gap analysis for the target audience. 
+
+Always use the github tool to add or update github issues.
+
+## Steps
+1. **Verify Required Files**
+   - Check for `.curriculum-admin/curriculum-map.md` and `.curriculum-admin/target-audience.md`.
+   - If either is missing, STOP and instruct the user to generate them using the appropriate prompts.
+
+2. **Analyze Curriculum Coverage**
+   - Review curriculum-map for modules, lessons, and their relationships.
+   - Compare coverage against target-audience needs and desired outcomes.
+
+3. **Identify Gaps**
+   - Use this checklist:
+     - Missing topics or modules
+     - Outdated or weak lessons
+     - Misalignment with audience needs or skill levels
+     - Lack of accessibility or inclusivity
+     - Insufficient assessment or feedback mechanisms
+
+4. **Prioritize Gaps**
+   - Assess impact and urgency for each gap.
+   - Link gaps to specific curriculum-map entries and target-audience requirements.
+
+5. **Report Gaps in Markdown**
+   - Use the following template for each gap:
+     ```markdown
+     ### [Gap Title]
+     - **Description:** Brief summary of the gap
+     - **Impact:** Who is affected and how
+     - **Suggested Action:** Recommendation to address the gap
+     - **Priority:** High / Medium / Low
+     - **Linked Curriculum Areas:** Reference to curriculum-map and/or target-audience
+     - **Tags:** Add a "content" tag to each item. Add a "update-content", "remove-content", or "add-content" tag to separate work processes
+     ```
+   - Summarize findings concisely and actionably.
+
+6. **Continuous Improvement**
+   - Revisit and update the gap analysis as new gaps are discovered or addressed.
+   - After generating the `.curriculum-admin/curriculum-gaps.md` file, PAUSE and check with the user before creating any GitHub issues.
+   - Once the user confirms, use findings to create GitHub issues. Tag each issue with `curriculum-gap` and the appropriate process tag (`add-content`, `update-content`, or `remove-content`) as well as `content` for clarity. Link issues to relevant modules or audience needs for traceability.
+
+## Output
+- Well-formed `.curriculum-admin/curriculum-gaps.md` file with actionable gap entries.
+- Issues generated for each gap to drive curriculum improvement.
+
+## Example Gap Entry
+```markdown
+### Outdated DevOps Module
+- **Description:** The DevOps module does not cover GitHub Actions or modern CI/CD practices.
+- **Impact:** Learners miss key automation skills needed for current workflows.
+- **Suggested Action:** Update module to include GitHub Actions and CI/CD best practices.
+- **Priority:** High
+- **Linked Curriculum Areas:** docs/5-devops-with-copilot.md, target-audience: Intermediate Developers
+ - **Tags:** content, update-content
+```
+
+## Notes
+- Keep entries concise, actionable, and aligned with curriculum standards.
+- Ensure accessibility and inclusivity in gap identification and reporting.
+- Collaborate with stakeholders for technical accuracy and pedagogical effectiveness.
diff --git a/.github/prompts/search-for-updates.prompt.md b/.github/prompts/search-for-updates.prompt.md
index cc4f1dc..f35a880 100644
--- a/.github/prompts/search-for-updates.prompt.md
+++ b/.github/prompts/search-for-updates.prompt.md
@@ -1,20 +1,29 @@
+
 # search-for-updates Workflow Prompt
 
 ## Objective
-Identify and summarize new features or updates from GitHub documentation repos (VS Code, GitHub Copilot).
+Identify, compare, and prioritize new features or updates from GitHub Copilot and VS Code documentation, aligning them with curriculum needs and gaps.
 
 ## Steps
-1. Search official documentation repos for recent updates.
-2. List new features, changes, or deprecations.
-3. Summarize each item with a brief description and source link.
-4. Output a table of new content items for review.
+1. Search official documentation sources for recent updates:
+   - GitHub Copilot: https://github.com/github/docs/tree/main/content/copilot
+   - VS Code: https://code.visualstudio.com/updates
+2. List new features, changes, or deprecations with brief descriptions and source links.
+3. For each item, use sequential thinking to compare with current curriculum content (refer to curriculum-map, target-audience, and curriculum-gaps files).
+4. Assess if new information modifies the approach for the target audience.
+5. Add extra weight to updates that address or improve identified curriculum gaps.
+6. Draft a summary of recommended changes in `.curriculum-admin/proposed-changes.md` for user review before creating any GitHub issues.
+7. Only create GitHub issues for curriculum updates after user approval of proposed changes.
 
 ## Tools
 - GitHub repo tool
 - Documentation search
+- Sequential thinking tool
 
 ## Output
 - Table of new/updated features with links and descriptions
+- Summary of recommended curriculum changes (proposed-changes.md)
+- GitHub issues (after user review)
 
 ## Example Prompt
-"Search the GitHub documentation repos for VS Code and GitHub Copilot. List all new features or updates from the past month, including a brief description and source link for each."
+"Search the official documentation sources for VS Code and GitHub Copilot. List all new features or updates from the past month, including a brief description and source link for each. Compare each update to the current curriculum (using curriculum-map, target-audience, and curriculum-gaps), and summarize recommended changes in .curriculum-admin/proposed-changes.md for user review before creating any GitHub issues."

From d6c11e9ed391ee9c3d9f169faf42253246a8e7bd Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 15:01:14 -0500
Subject: [PATCH 5/8] feat: add proposed curriculum updates for GitHub Copilot,
 including new modules on chat, accessibility, learning pathways, security
 metrics, and billing options

---
 .curriculum-admin/proposed-changes.md | 29 +++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 .curriculum-admin/proposed-changes.md

diff --git a/.curriculum-admin/proposed-changes.md b/.curriculum-admin/proposed-changes.md
new file mode 100644
index 0000000..8b429e3
--- /dev/null
+++ b/.curriculum-admin/proposed-changes.md
@@ -0,0 +1,29 @@
+## Proposed Curriculum Updates (July 2025)
+
+### 1. GitHub Copilot Chat & Agent Mode
+- Add a module on the open source Copilot Chat extension, including how to contribute and explore its codebase.
+- Expand coverage of agent mode, including MCP server installation, management, and agentic workflows (loops, task handoff).
+- Include hands-on labs for configuring custom chat modes and selecting language models.
+
+### 2. Custom Instructions & Prompts
+- Add a lesson on generating and customizing Copilot instructions using agent mode.
+- Demonstrate best practices for prompt engineering and instruction files, including workspace analysis.
+
+### 3. Accessibility & Inclusivity
+- Update accessibility guidance to reflect new chat alerts, sounds, and screen reader improvements.
+- Add practical exercises for testing accessibility in Copilot Chat and VS Code.
+
+### 4. Learning Pathways & Guides
+- Integrate new scenario-based guides for learning programming languages with Copilot as a tutor.
+- Highlight strategies for using Copilot to foster coding independence and skill development.
+
+### 5. Security & Dependabot Metrics
+- Add content on using Dependabot metrics and prioritization guides for vulnerability management.
+- Include exercises for interpreting security metrics and alerts in organizational settings.
+
+### 6. Pay-As-You-Go & BYOK for GitHub Models
+- Briefly introduce new billing and API key options for GitHub Models, with links for further reading.
+
+---
+**Next Steps:**
+- Review and approve these proposed changes before creating GitHub issues for curriculum updates.

From cf34806a2fa123623d905df235803ad7b25b6346 Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 16:06:16 -0500
Subject: [PATCH 6/8] feat: enhance search-for-updates prompt with detailed
 update comparison criteria and improved documentation links

---
 .github/prompts/search-for-updates.prompt.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/.github/prompts/search-for-updates.prompt.md b/.github/prompts/search-for-updates.prompt.md
index f35a880..44c0ae8 100644
--- a/.github/prompts/search-for-updates.prompt.md
+++ b/.github/prompts/search-for-updates.prompt.md
@@ -1,3 +1,8 @@
+---
+mode: 'agent'
+description: 'Identify and summarize new features or updates from GitHub documentation repos (VS Code, GitHub Copilot)'
+tools: ['sequentialthinking','editFiles','changes', 'codebase', 'fetch', 'githubRepo', 'problems', 'runCommands', 'runNotebooks', 'search', 'usages', 'microsoft-docs', 'add_comment_to_pending_review', 'add_issue_comment', 'create_and_submit_pull_request_review', 'create_branch', 'create_issue', 'create_pull_request', 'get_commit', 'get_discussion', 'get_discussion_comments', 'get_file_contents', 'get_issue', 'get_issue_comments', 'get_pull_request', 'get_pull_request_comments', 'get_pull_request_diff', 'get_pull_request_files', 'get_pull_request_reviews', 'get_pull_request_status', 'get_tag', 'list_branches', 'list_issues', 'list_tags', 'search_code', 'search_issues', 'search_repositories', 'update_issue']
+---
 
 # search-for-updates Workflow Prompt
 
@@ -9,7 +14,12 @@ Identify, compare, and prioritize new features or updates from GitHub Copilot an
    - GitHub Copilot: https://github.com/github/docs/tree/main/content/copilot
    - VS Code: https://code.visualstudio.com/updates
 2. List new features, changes, or deprecations with brief descriptions and source links.
-3. For each item, use sequential thinking to compare with current curriculum content (refer to curriculum-map, target-audience, and curriculum-gaps files).
+3. For each item, use sequential thinking to compare with current curriculum content (refer to curriculum-map, target-audience, and curriculum-gaps files). Ensure these columns/properties exist for the update:
+- Update
+- Brief Description
+- Source Link
+- Recommendation analysis (reason for inclusion)
+- Priority (High/Medium/Low)
 4. Assess if new information modifies the approach for the target audience.
 5. Add extra weight to updates that address or improve identified curriculum gaps.
 6. Draft a summary of recommended changes in `.curriculum-admin/proposed-changes.md` for user review before creating any GitHub issues.
@@ -27,3 +37,4 @@ Identify, compare, and prioritize new features or updates from GitHub Copilot an
 
 ## Example Prompt
 "Search the official documentation sources for VS Code and GitHub Copilot. List all new features or updates from the past month, including a brief description and source link for each. Compare each update to the current curriculum (using curriculum-map, target-audience, and curriculum-gaps), and summarize recommended changes in .curriculum-admin/proposed-changes.md for user review before creating any GitHub issues."
+

From c68e496531b06bd7b04583138d6b9c0a04cc0d43 Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 16:18:53 -0500
Subject: [PATCH 7/8] feat: update search-for-updates prompt with additional
 output requirements and clarify steps for curriculum alignment

---
 .github/prompts/search-for-updates.prompt.md | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/.github/prompts/search-for-updates.prompt.md b/.github/prompts/search-for-updates.prompt.md
index 44c0ae8..49663eb 100644
--- a/.github/prompts/search-for-updates.prompt.md
+++ b/.github/prompts/search-for-updates.prompt.md
@@ -9,31 +9,35 @@ tools: ['sequentialthinking','editFiles','changes', 'codebase', 'fetch', 'github
 ## Objective
 Identify, compare, and prioritize new features or updates from GitHub Copilot and VS Code documentation, aligning them with curriculum needs and gaps.
 
+### Required outputs
+.curriculum-admin/proposed-changes.md - list of proposed changes to make to the curriculum for user review before github issue creation.
+
+
 ## Steps
 1. Search official documentation sources for recent updates:
    - GitHub Copilot: https://github.com/github/docs/tree/main/content/copilot
    - VS Code: https://code.visualstudio.com/updates
 2. List new features, changes, or deprecations with brief descriptions and source links.
 3. For each item, use sequential thinking to compare with current curriculum content (refer to curriculum-map, target-audience, and curriculum-gaps files). Ensure these columns/properties exist for the update:
+- Date of the recommendation (today's date)
 - Update
 - Brief Description
 - Source Link
 - Recommendation analysis (reason for inclusion)
 - Priority (High/Medium/Low)
+- Gap analysis (if it addresses current identified gaps in content)
+- User impact (how it improves the user experience for the target-audience)
 4. Assess if new information modifies the approach for the target audience.
 5. Add extra weight to updates that address or improve identified curriculum gaps.
 6. Draft a summary of recommended changes in `.curriculum-admin/proposed-changes.md` for user review before creating any GitHub issues.
 7. Only create GitHub issues for curriculum updates after user approval of proposed changes.
+8. Remove any proposed changes from the proposed-changes.md ONLY after the github issue is confirmed to exist.
 
-## Tools
-- GitHub repo tool
-- Documentation search
-- Sequential thinking tool
 
 ## Output
-- Table of new/updated features with links and descriptions
-- Summary of recommended curriculum changes (proposed-changes.md)
-- GitHub issues (after user review)
+- Table of new/updated features with links and descriptions in the .curriculum-admin/proposed-changes.md
+- Summary of recommended curriculum changes (proposed-changes.md) output to chat window
+- GitHub issues (after user review) created by referencing the proposed-changes.md (it can be updated by the user after initial creation)
 
 ## Example Prompt
 "Search the official documentation sources for VS Code and GitHub Copilot. List all new features or updates from the past month, including a brief description and source link for each. Compare each update to the current curriculum (using curriculum-map, target-audience, and curriculum-gaps), and summarize recommended changes in .curriculum-admin/proposed-changes.md for user review before creating any GitHub issues."

From a0f774979ef984ab9ae04c7740ed1328733f02ed Mon Sep 17 00:00:00 2001
From: Michael Simmons <michael.simmons@neudesic.com>
Date: Fri, 25 Jul 2025 16:22:08 -0500
Subject: [PATCH 8/8] feat: restructure proposed curriculum changes with
 detailed updates on Copilot Chat, agent mode, and accessibility improvements

---
 .curriculum-admin/proposed-changes.md | 40 ++++++++++-----------------
 1 file changed, 14 insertions(+), 26 deletions(-)

diff --git a/.curriculum-admin/proposed-changes.md b/.curriculum-admin/proposed-changes.md
index 8b429e3..54f01a8 100644
--- a/.curriculum-admin/proposed-changes.md
+++ b/.curriculum-admin/proposed-changes.md
@@ -1,29 +1,17 @@
-## Proposed Curriculum Updates (July 2025)
+# Proposed Curriculum Changes
+_Last updated: July 25, 2025_
 
-### 1. GitHub Copilot Chat & Agent Mode
-- Add a module on the open source Copilot Chat extension, including how to contribute and explore its codebase.
-- Expand coverage of agent mode, including MCP server installation, management, and agentic workflows (loops, task handoff).
-- Include hands-on labs for configuring custom chat modes and selecting language models.
+| Date       | Update/Feature                | Brief Description                                                                 | Source Link                                                                 | Gap Analysis | User Impact | Recommendation Analysis | Priority |
+|------------|------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------|------------|------------------------|----------|
+| 2025-06-30 | Copilot Chat Open Source     | GitHub Copilot Chat extension is now open source, enabling community contributions | [Blog](https://code.visualstudio.com/blogs/2025/06/30/openSourceAIEditorFirstMilestone) | Addresses advanced agent workflows gap. | Empowers users to contribute, customize, and extend chat experiences; increases transparency and skill-building. | Add module/lab on contributing to Copilot Chat, agent mode, and customizing chat experiences. | High |
+| 2025-06-30 | Chat Mode Improvements       | Custom chat modes, model selection, improved editing, import via links, gear menu  | [Release Notes](https://code.visualstudio.com/updates/v1_102#_chat-mode-improvements) | Addresses prompt engineering and extensibility gaps. | Enables tailored chat experiences, improves workflow efficiency, and supports advanced user scenarios. | Update lessons on chat modes, prompt files, and agent mode. Add hands-on labs for custom modes and model selection. | High |
+| 2025-06-30 | Generate Custom Instructions | Agent mode can now auto-generate project-specific instructions                     | [Release Notes](https://code.visualstudio.com/updates/v1_102#_generate-custom-instructions) | Supports best practices and onboarding gaps. | Simplifies setup for new projects, improves consistency, and helps users adopt Copilot more effectively. | Add lab for using "Generate Instructions" and customizing `.github/copilot-instructions.md`. | Medium |
+| 2025-06-30 | Terminal Auto Approval       | Agent mode can auto-approve safe terminal commands, with allow/deny lists          | [Release Notes](https://code.visualstudio.com/updates/v1_102#_terminal-auto-approval-experimental) | Addresses security and automation gaps. | Reduces friction for safe command execution, improves security awareness, and streamlines agent workflows. | Update security and best practices modules to cover terminal command safety and agent automation. | Medium |
+| 2025-06-30 | MCP Support GA               | MCP (Model Context Protocol) support is now generally available                    | [Release Notes](https://code.visualstudio.com/updates/v1_102#_mcp-support-in-vs-code-is-generally-available) | Addresses advanced agent workflows and extensibility gaps. | Enables agent extensibility, server management, and advanced automation for technical leads and architects. | Add advanced module on MCP, agent extensibility, and server management. | High |
+| 2025-06-30 | Accessibility Updates        | Improved accessibility signals, error alerts, and editor commands for screen reader users | [Release Notes](https://code.visualstudio.com/updates/v1_102#_accessibility) | Addresses accessibility and inclusivity gaps. | Improves experience for neurodiverse and visually impaired users; supports inclusive curriculum goals. | Update accessibility guidance and labs to include new features and best practices. | Medium |
+| 2025-06-30 | Code Editing: Snooze Suggestions | Users can pause Copilot inline suggestions and NES                             | [Release Notes](https://code.visualstudio.com/updates/v1_102#_snooze-code-completions) | Minor gap in user control and focus. | Allows users to focus without distraction, improving productivity and comfort. | Add tip or FAQ entry about managing Copilot suggestions for focus. | Low |
+| 2025-06-30 | GitHub PR Extension: Coding Agent Sessions | Deeper integration for Copilot coding agent sessions, status tracking, and session logs | [Release Notes](https://code.visualstudio.com/updates/v1_102#_start-a-coding-agent-session-preview) | Supports advanced agent workflows gap. | Improves collaboration, transparency, and workflow management for technical teams. | Add advanced labs for coding agent sessions and PR workflows. | Medium |
+| 2025-06-30 | Python Extension: Environments & MCP Tools | Improved Python environment management, new MCP tools in Pylance           | [Release Notes](https://code.visualstudio.com/updates/v1_102#_python-environments-extension-improvements) | Minor gap in Python environment management. | Streamlines Python setup and environment management for learners using Copilot with Python. | Update Python labs to cover new environment features and MCP tool usage. | Low |
 
-### 2. Custom Instructions & Prompts
-- Add a lesson on generating and customizing Copilot instructions using agent mode.
-- Demonstrate best practices for prompt engineering and instruction files, including workspace analysis.
 
-### 3. Accessibility & Inclusivity
-- Update accessibility guidance to reflect new chat alerts, sounds, and screen reader improvements.
-- Add practical exercises for testing accessibility in Copilot Chat and VS Code.
-
-### 4. Learning Pathways & Guides
-- Integrate new scenario-based guides for learning programming languages with Copilot as a tutor.
-- Highlight strategies for using Copilot to foster coding independence and skill development.
-
-### 5. Security & Dependabot Metrics
-- Add content on using Dependabot metrics and prioritization guides for vulnerability management.
-- Include exercises for interpreting security metrics and alerts in organizational settings.
-
-### 6. Pay-As-You-Go & BYOK for GitHub Models
-- Briefly introduce new billing and API key options for GitHub Models, with links for further reading.
-
----
-**Next Steps:**
-- Review and approve these proposed changes before creating GitHub issues for curriculum updates.
+**Instructions:**