{"id":51555072,"url":"https://github.com/microsoft/frontier-ghcp-rvas","last_synced_at":"2026-07-10T04:00:55.729Z","repository":{"id":367080379,"uuid":"1256017017","full_name":"microsoft/frontier-ghcp-rvas","owner":"microsoft","description":"GitHub Copilot Real Value Acceleration Service (RVAS)","archived":false,"fork":false,"pushed_at":"2026-07-09T18:09:09.000Z","size":9092,"stargazers_count":1,"open_issues_count":0,"forks_count":2,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-07-09T19:16:38.133Z","etag":null,"topics":["ghcp","github","github-copilot"],"latest_commit_sha":null,"homepage":"https://microsoft.github.io/frontier-ghcp-rvas","language":"COBOL","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/microsoft.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-06-01T11:38:05.000Z","updated_at":"2026-07-09T18:09:42.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/microsoft/frontier-ghcp-rvas","commit_stats":null,"previous_names":["microsoft/frontier-ghcp-hackathon","microsoft/frontier-ghcp-rvas"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/microsoft/frontier-ghcp-rvas","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Ffrontier-ghcp-rvas","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Ffrontier-ghcp-rvas/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Ffrontier-ghcp-rvas/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Ffrontier-ghcp-rvas/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/microsoft","download_url":"https://codeload.github.com/microsoft/frontier-ghcp-rvas/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/microsoft%2Ffrontier-ghcp-rvas/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":35319810,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-07-10T02:00:06.465Z","response_time":60,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ghcp","github","github-copilot"],"created_at":"2026-07-10T04:00:55.035Z","updated_at":"2026-07-10T04:00:55.721Z","avatar_url":"https://github.com/microsoft.png","language":"COBOL","funding_links":[],"categories":[],"sub_categories":[],"readme":"# GitHub Copilot RVAS\n\n![GitHub Copilot RVAS banner](docs/images/rvas-banner.jpg)\n\nWelcome to the GitHub Copilot RVAS (Real Value Acceleration Solution)! This repository helps your team **drive real work outcomes** with GitHub Copilot, and use those outcomes to build lasting adoption across your organization. Choose from **22 worked-example challenges** that demonstrate proven outcome patterns, or bring your own app and run an RVAS delivery session on your own codebase.\n\n## Two Ways to Run an RVAS Delivery Session\n\n### Option 1: Pick a Worked-Example Challenge\n\nChoose one of the **22 challenge tracks** below. Each challenge maps to a specific business outcome and provides starter code, a devcontainer, and a progression path through real work. Use these to learn outcome-driven AI-assisted development patterns you can apply to your own work.\n\n### Option 2: Bring Your Own Challenge\n\nRun an RVAS delivery session on your own app or repository. The **[Bring Your Own Challenge (BYOC) kit](./byoc/)** provides a canvas to define your target outcome, templates to author a custom challenge, and a facilitator runbook to guide your session. This turns the session into working time that delivers a measurable result for your team.\n\nSee **[byoc/README.md](./byoc/README.md)** for the full kit.\n\n## Overview\n\nThe repository includes **22 challenge tracks** organized by the outcomes they help you deliver:\n\n### Challenges by Outcome\n\nEach challenge below drives a measurable business outcome -- shipping features, modernizing legacy systems, raising quality, automating delivery, standing up platform foundations, or building AI-powered capabilities. Delivering that outcome is what makes the case for wider Copilot adoption.\n\n- 📋 **[Challenge 0: Product Planning Track](./tracks/challenge-0-product-planning-track.md)** - Product planning, backlog management, documentation (no code) | **Outcome:** Ship Product Features Faster\n- 🔧 **[Challenge 1: Web API Track](./tracks/challenge-1-web-api-track.md)** - REST APIs, authentication, testing | **Outcomes:** Ship Product Features Faster, Raise Quality and Confidence\n- 📊 **[Challenge 2: ML \u0026 AI Track](./tracks/challenge-2-ml-ai-track.md)** - Data analysis, ML models, feature engineering | **Outcome:** Build AI-Powered Capabilities\n- ☁️ **[Challenge 3: DevOps Track](./tracks/challenge-3-devops-track.md)** - Infrastructure as Code, containers, CI/CD | **Outcomes:** Automate Delivery and Ops Toil, Stand Up Cloud Platform Foundations\n- 🎨 **[Challenge 4: Frontend Track](./tracks/challenge-4-frontend-track.md)** - React, TypeScript, modern UI | **Outcomes:** Ship Product Features Faster, Raise Quality and Confidence\n- 🔍 **[Challenge 5: QA \u0026 Testing Track](./tracks/challenge-5-qa-track.md)** - AI-assisted testing, test planning, Copilot for QA workflows | **Outcome:** Raise Quality and Confidence\n- 🤖 **[Challenge 6: Agentic Workflows Track](./tracks/challenge-6-agentic-workflows-track.md)** - Build AI-powered repository automation with GitHub Agentic Workflows | **Outcomes:** Automate Delivery and Ops Toil, Build AI-Powered Capabilities\n- 🧩 **[Challenge 7: Copilot SDK Track](./tracks/challenge-7-copilot-sdk-track.md)** - Build a Copilot SDK application (advanced) | **Outcome:** Build AI-Powered Capabilities\n- ✈️ **[Challenge 8: Flight Delay Predictor Track](./tracks/challenge-8-flight-delay-track.md)** - Full-stack ML app (advanced) | **Outcomes:** Ship Product Features Faster, Build AI-Powered Capabilities\n- 🏢 **[Challenge 9: Cross-Functional Team Sprint](./tracks/challenge-9-team-sprint-track.md)** - Full team agile sprint, ideation to deployment (4-6 people) | **Outcome:** Ship Product Features Faster\n- 🥾 **[Challenge 10: Technical Team Sprint](./tracks/challenge-10-tech-sprint-track.md)** - Technical team sprint from spec to deployment (2-4 developers) | **Outcome:** Ship Product Features Faster\n- 🏦 **[Challenge 11: Legacy MUMPS Modernization](./tracks/challenge-11-mumps-modernization-track.md)** - Reverse-engineer and translate a MUMPS banking system (solo, advanced) | **Outcome:** Modernize Legacy Systems\n- 🔄 **[Challenge 12: Legacy Code Modernization](./tracks/challenge-12-legacy-modernization-track.md)** - Reverse-engineer and modernize an undocumented Java application | **Outcome:** Modernize Legacy Systems\n- 📄 **[Challenge 13: Living Documentation](./tracks/challenge-13-living-docs-track.md)** - Automate javadoc, diagrams, changelogs, and PR doc reviews | **Outcomes:** Raise Quality and Confidence, Automate Delivery and Ops Toil\n- 🔩 **[Challenge 14: Pipeline Factory](./tracks/challenge-14-pipeline-factory-track.md)** - Build CI/CD pipelines, debug broken deployments, generate runbooks | **Outcome:** Automate Delivery and Ops Toil\n- 📝 **[Challenge 15: Backlog Generator](./tracks/challenge-15-backlog-generator-track.md)** - Convert requirement specs into structured backlogs with MCP | **Outcomes:** Ship Product Features Faster, Automate Delivery and Ops Toil\n- 🖥️ **[Challenge 16: Ops Assistant](./tracks/challenge-16-ops-assistant-track.md)** - Build AI-assisted log analysis, incident routing, and ops tooling | **Outcome:** Automate Delivery and Ops Toil\n- 🚀 **[Challenge 17: Spec-to-Ship Accelerator](./tracks/challenge-17-spec-to-ship-track.md)** - Full lifecycle from functional spec to deployed code | **Outcomes:** Ship Product Features Faster, Automate Delivery and Ops Toil\n- 🏗️ **[Challenge 18: COBOL Banking Modernization](./tracks/challenge-18-cobol-modernization-track.md)** - Reverse-engineer and modernize a COBOL banking system into a full-stack web app | **Outcome:** Modernize Legacy Systems\n- 🔧 **[Challenge 19: WCF Banking Modernization](./tracks/challenge-19-wcf-modernization-track.md)** - Understand a legacy WCF SOAP banking service and migrate it to a REST API | **Outcome:** Modernize Legacy Systems\n- 💻 **[Challenge 20: PowerShell Automation](./tracks/challenge-20-powershell-automation-track.md)** - Fix, test, document, and package PowerShell scripts for real sysadmin work | **Outcomes:** Automate Delivery and Ops Toil, Modernize Legacy Systems\n- ☁️ **[Challenge 21: Azure Terraform Track](./tracks/challenge-21-azure-terraform-track.md)** - Build an Azure Terraform foundation with modules, identity, policy checks, and CI guardrails | **Outcome:** Stand Up Cloud Platform Foundations\n\n**[View All Tracks \u0026 Choose Yours](./tracks/README.md)**\n\nCoaches who need a focused workshop path can use the site's Challenge Set Builder and Learning Paths pages to select challenges and generate a single shareable student URL.\n\nEach track provides a curated path through the challenges based on your role, with specific guidance, tips, and learning objectives.\n\n## Duration\n\n**6-8 hours** per track.\n\n## Documentation Site\n\nThe repository includes a bespoke static documentation site in the `web/` directory. The site is dependency-free and built with vanilla HTML, CSS, and JavaScript.\n\nTo build the site data locally:\n\n```bash\nnode web/build.js\n```\n\nThis reads `challenges/*/meta.yml`, `learning-paths.json`, and track markdown files, then writes JSON to `web/assets/data/`.\n\nTo preview locally:\n\n```bash\ncd web\npython3 -m http.server\n```\n\nThen open `http://localhost:8000/index.html` in your browser.\n\nThe GitHub Pages deployment workflow automatically builds and deploys the site from `.github/workflows/deploy-site.yml` on every push to `main`.\n\n## Getting Started\n\n### Option 1: Work a Challenge Track\n\n1. **Choose a challenge** that drives an outcome you want to produce. See **[tracks/README.md](./tracks/README.md)** for the full catalog organized by outcome.\n2. **Set up your environment** using the prerequisites and devcontainer guidance in your chosen track file.\n3. **Work through the stages** in the track, delivering a demonstrable result at the end.\n\n### Option 2: Bring Your Own Challenge\n\n1. **Define your outcome** using the **[Outcome Canvas](./byoc/outcome-canvas.md)**.\n2. **Author your challenge** using the templates in **[byoc/templates/](./byoc/templates/)** (if you need a custom progression; otherwise skip this and work directly on your app).\n3. **Run your session** following the **[BYOC Facilitator Runbook](./byoc/facilitator-runbook.md)**.\n4. **Measure success** using the **[Outcome Scorecard](./byoc/outcome-scorecard.md)**.\n\nSee the **[BYOC Kit README](./byoc/README.md)** for the end-to-end flow and a worked example.\n\n---\n\n### Step 1: Choose Your Track\n\n**Not sure which track?** See the **[Track Selection Guide](./tracks/README.md)** for help choosing.\n\n**Running a coached session?** Use the site's Challenge Set Builder or Learning Paths pages to prepare a curated challenge set and share one student URL with participants.\n\n### Step 2: Set Up Environment\n\n#### Prerequisites\n\n- GitHub account with Copilot access\n- GitHub Codespaces enabled (recommended) OR\n- Local development environment with VS Code and GitHub Copilot extension\n\n#### Start Hacking\n\n**Option A: GitHub Codespaces (Recommended)**\n\n1. Click the green **\"Code\"** button at the top of this repository.\n2. Select the **\"Codespaces\"** tab.\n3. Click **\"Create codespace on main\"**.\n4. Wait for the environment to set up (2-3 minutes).\n\n**Option B: Local Development**\n\n1. Clone this repository:\n\n   ```bash\n   git clone https://github.com/microsoft/frontier-ghcp-rvas.git\n   cd frontier-ghcp-rvas\n   ```\n\n2. Open the folder in VS Code.\n3. When prompted, click **\"Reopen in Container\"** (requires Docker and Dev Containers extension).\n\nThe environment is pre-configured with:\n\n- Node.js (LTS)\n- Python 3.11\n- Docker\n- Terraform\n- kubectl\n- All necessary VS Code extensions\n\n### Step 3: Clean Start (CRITICAL)\n\nThe `.github/` directory contains instructions, agents, and skills used by the RVAS delivery session organizers. Run the cleanup script to reset it before you begin.\n\n**Linux / macOS / Codespaces:**\n\n```bash\n./scripts/clean-start.sh\n```\n\n**Windows (PowerShell):**\n\n```powershell\n.\\scripts\\clean-start.ps1\n```\n\nThis empties `.github/copilot-instructions.md`, removes existing agents and skills, and detaches the git remote so you don't accidentally push to the template repo. After running the script, add your own project-specific instructions (see your Track guide for examples).\n\n### Step 4: Verify Your Setup\n\nBefore starting, make sure Copilot is working:\n\n**Check Copilot Status:**\n\n- Look at the bottom-right of VS Code\n- Copilot icon should be visible and say \"Ready\"\n\n**Test Inline Suggestions:**\n\n1. Create a new file (e.g., `test.js`)\n2. Type: `// function to add two numbers`\n3. You should see Copilot suggestions appear!\n\n**Test Chat:**\n\n1. Press `Ctrl+Shift+I` (Windows/Linux) or `Cmd+Shift+I` (Mac)\n2. Type: \"Hello, are you working?\"\n3. Copilot should respond!\n\n### Step 5: Start Your Track\n\nOnce your environment is ready:\n\n1. Open your chosen track guide (e.g., `tracks/challenge-1-web-api-track.md`)\n2. Follow the recommended challenge sequence\n3. Use the track-specific tips and guidance\n\n## Skills You'll Build While Driving Outcomes\n\nAs you work through these challenges, you'll build proficiency with GitHub Copilot's capabilities as a by-product of delivering real work:\n\n### 1. **Chat \u0026 Agentic Capabilities**\n\n- `/explain`, `/fix`, `/tests` commands\n- **Agentic Mode** - Autonomous multi-step task execution\n- **Planning Mode** - High-level architectural reasoning\n- Workspace context chat\n\n### 2. **Prompt Engineering**\n\n- Effective prompt patterns\n- Context-aware requests\n- Iterative refinement\n- Collections and reusable prompts\n\n### 3. **Extensibility \u0026 Custom Agents**\n\n- **MCP Servers** - Connect external tools and data\n- **Custom Agents** - Build and use specialized assistants\n- Enhanced context for Copilot\n\n### 4. **Inline Suggestions**\n\n- Code completion\n- Multi-line suggestions\n- Ghost text navigation\n\n## Challenges\n\n**Tip:** Instead of choosing challenges individually, we recommend following a [role-based track](./tracks/README.md) for a structured learning experience!\n\nAll 22 challenges are available, and each track has a dedicated challenge:\n\n### [Challenge 0: Product Planning -- TaskFlow v2.0](./challenges/challenge-0-product-planning/) ([Track](./tracks/challenge-0-product-planning-track.md))\n\n**Team**: Product Owners, Business Analysts, Project Managers\n**Skills**: Markdown, GitHub Issues, GitHub Projects, Pull Requests\n**Copilot Focus**: Long-form writing, brainstorming, GitHub MCP server for issue/PR management\n\nPlan the next major release of a task management platform across 5 progressive stages. Start with competitive analysis and quantified personas, then write and critique user stories, build feature specs aligned to real API endpoints, resolve conflicting stakeholder requests under a fixed budget, and produce a production-grade release plan with risk matrices, rollback strategies, and monitoring specs. No application code required.\n\n---\n\n### [Challenge 1: Web Development - REST API Builder](./challenges/challenge-1-web-api/) ([Track](./tracks/challenge-1-web-api-track.md))\n\n**Team**: Backend/Web Developers\n**Skills**: Express.js/FastAPI, API design, error handling, testing\n**Copilot Focus**: Inline completion, `/tests` command, workspace chat\n\nBuild a task management REST API across 5 progressive stages: basic CRUD, JWT authentication with role-based access, SQLite persistence with data relationships, debugging a broken v2 API module (3 intentional bugs), and production readiness with load testing, caching, and structured logging.\n\n---\n\n### [Challenge 2: ML/AI - Data Analysis \u0026 Model Development](./challenges/challenge-2-ml-ai/) ([Track](./tracks/challenge-2-ml-ai-track.md))\n\n**Team**: Data Scientists, ML Engineers\n**Skills**: Python, pandas, scikit-learn, data visualization\n**Copilot Focus**: Jupyter notebooks integration, `/explain` for algorithms, code generation\n\nPredict customer churn across 5 stages: discover 7+ hidden data quality issues, create visualizations with statistical hypothesis testing, train models with cost-sensitive evaluation using sklearn Pipelines, compare imbalance techniques with SHAP interpretability, and deploy a prediction API with drift detection and a model card.\n\n---\n\n### [Challenge 3: DevOps - Infrastructure as Code](./challenges/challenge-3-devops/) ([Track](./tracks/challenge-3-devops-track.md))\n\n**Team**: DevOps, Platform Engineers\n**Skills**: Terraform, Docker, Kubernetes, CI/CD\n**Copilot Focus**: Infrastructure patterns, documentation generation, best practices\n\nBuild infrastructure for a Node.js app across 5 stages: multi-stage Dockerfile with Docker Compose, Kubernetes with HPA and NetworkPolicy, Terraform for Azure (ACR, AKS) with variables and remote state, debug a broken Key Vault module and add observability, then create a CI/CD pipeline with blue/green deployment and a DR runbook.\n\n---\n\n### [Challenge 4: Frontend - Interactive UI Components](./challenges/challenge-4-frontend/) ([Track](./tracks/challenge-4-frontend-track.md))\n\n**Team**: Frontend Developers\n**Skills**: React, TypeScript, Component design, State management\n**Copilot Focus**: Component scaffolding, TypeScript types, CSS styling\n\nBuild a task dashboard across 5 stages: responsive layout with React Router, state management with Context/useReducer and undo support, drag-and-drop Kanban with keyboard shortcuts and themes, find and fix 5 accessibility violations in a pre-built component, then integrate with a REST API and achieve \u003e80% test coverage.\n\n---\n\n### [Challenge 5: QA \u0026 Test Automation](./challenges/challenge-5-qa/) ([Track](./tracks/challenge-5-qa-track.md))\n\n**Team**: QA Engineers, Quality Assurance Specialists, Manual Testers\n**Skills**: Test planning, test case design, bug reporting (no coding experience required)\n**Copilot Focus**: AI-assisted test generation, Playwright MCP exploration, Copilot-driven debugging\n\nTest the eShop application across 5 stages: explore the app with Copilot and Playwright MCP to build a test plan, use Copilot to debug and generate your first automated tests, expand coverage across browsers with Copilot-generated page objects, compare AI-driven vs human-guided testing approaches, then build reporting and a test strategy document.\n\n---\n\n### [Challenge 7: Copilot SDK -- Release Notes Agent](./challenges/challenge-7-copilot-sdk/) ([Track](./tracks/challenge-7-copilot-sdk-track.md))\n\n**Team**: Experienced developers (any role) who finished a standard track\n**Duration**: 8-12 hours (Advanced)\n**Skills**: Node.js, TypeScript, Copilot SDK, GitHub API, custom tool definitions\n**Copilot Focus**: Building *with* the Copilot agent runtime -- sessions, streaming, custom tools, MCP integration\n\nBuild a Release Notes Agent powered by the GitHub Copilot SDK. The agent fetches merged PRs, categorizes changes, generates a structured changelog through iterative conversation, and publishes a draft GitHub Release -- all using custom tools, streaming responses, and multi-turn sessions.\n\n\u003e ⚠️ **Challenge 7 is significantly harder and longer than the standard challenges.**\n\n---\n\n### [Challenge 8: Full-Stack Flight Delay Predictor](./challenges/challenge-8-flight-delay/) ([Track](./tracks/challenge-8-flight-delay-track.md))\n\n**Team**: Full-Stack Developers, Advanced Participants\n**Duration**: 8-12 hours (extended challenge)\n**Skills**: Python, pandas, scikit-learn, Flask/FastAPI, TypeScript, frontend frameworks\n**Copilot Focus**: End-to-end development -- data science in notebooks, API scaffolding, frontend generation, cross-domain debugging\n\nBuild a complete application that predicts flight delay probability. Explore a real FAA dataset, train an ML model, serve it through a REST API, and create a frontend where users select a day and airport to see their delay risk.\n\n---\n\n### [Challenge 9: Cross-Functional Team Sprint (CityPulse)](./challenges/challenge-9-team-sprint/) ([Track](./tracks/challenge-9-team-sprint-track.md))\n\n**Team**: Cross-functional team of 4-6 (Product Owner, Backend Dev, Frontend Dev, QA, DevOps, optional BA)\n**Duration**: 8 hours (team challenge)\n**Skills**: GitHub Spark, GitHub Issues/Projects, Express.js/FastAPI, React/Vue, Playwright, Docker, Azure, Terraform\n**Copilot Focus**: Every role uses Copilot -- PO for user stories and planning, developers for code generation, QA for test automation, DevOps for infrastructure\n\nBuild CityPulse, a civic engagement platform, from scratch as a cross-functional team running a simulated agile sprint. The PO ideates with GitHub Spark and manages the backlog via GitHub Issues while developers, QA, and DevOps work in parallel across two sprints -- building a REST API, a frontend UI, automated tests, CI/CD pipelines, and deploying to Azure. Ends with a team demo and retrospective.\n\n\u003e This challenge requires a team. It is not designed for solo participants.\n\n---\n\n### [Challenge 10: Technical Team Sprint (TrailMate)](./challenges/challenge-10-tech-sprint/) ([Track](./tracks/challenge-10-tech-sprint-track.md))\n\n**Team**: Technical team of 2-4 (Backend Dev, Frontend Dev, DevOps required; QA optional -- no PO or BA)\n**Duration**: 8 hours (team challenge)\n**Skills**: Express.js/FastAPI, React/Vue, Playwright, Docker, Azure, Terraform, GitHub Issues/Projects\n**Copilot Focus**: Every technical role uses Copilot -- developers for code generation, QA for test automation, DevOps for infrastructure\n\nBuild TrailMate, a trail management platform for a regional parks authority, from a provided functional specification. Unlike the Cross-Functional Team Sprint, there is no product discovery phase and no business stakeholders. The team reads the spec, writes a technical specification, breaks work into GitHub Issues, and self-organizes across two sprints -- building a REST API, a frontend UI, automated tests, CI/CD pipelines, and deploying to Azure. Ends with a team demo and retrospective.\n\n\u003e This challenge requires a team. It is not designed for solo participants.\n\n---\n\n### [Challenge 11: Legacy MUMPS Modernization](./challenges/challenge-11-mumps-banking/) ([Track](./tracks/challenge-11-mumps-modernization-track.md))\n\n**Team**: Solo or pair (any developer role)\n**Duration**: 8-12 hours (Advanced)\n**Skills**: Any modern language (PSL, Java, Python, C#, TypeScript), reverse engineering, testing, financial domain knowledge\n**Copilot Focus**: Legacy code comprehension with `/explain`, cross-language translation, characterization test generation, architecture documentation\n\nReverse-engineer and translate a core banking system written in MUMPS -- a language most developers have never seen. The system handles customer management, deposit accounts, teller transactions, consumer loans, interest calculation, and end-of-day batch processing across 12 routines and ~2,500 lines of code. Understand it, test it, extend it, and translate it to a modern language while preserving every business rule.\n\n---\n\n### [Challenge 12: Legacy Code Modernization](./challenges/challenge-12-legacy-modernization/) ([Track](./tracks/challenge-12-legacy-modernization-track.md))\n\n**Team**: Solo or pair (Java developers)\n**Duration**: 6-8 hours\n**Skills**: Java 8/17, Spring Boot, Maven, REST APIs, SQL\n**Copilot Focus**: Legacy code comprehension with `/explain`, security auditing, characterization testing, framework migration\n\nReverse-engineer and modernize the Acme Bank Account Manager -- an undocumented Java 8 / Spring Boot 1.5 banking application built by a contractor who left in 2018. The code has SQL injection vulnerabilities, deprecated libraries (Log4j 1.x, Apache HttpClient 4.x), no service layer, no tests, and business logic buried in controllers. Recover the business rules, audit for security issues, write characterization tests, and migrate to Spring Boot 3.x / Java 17+.\n\n---\n\n### [Challenge 13: Living Documentation](./challenges/challenge-13-living-docs/) ([Track](./tracks/challenge-13-living-docs-track.md))\n\n**Team**: Solo or pair (Java developers, tech leads)\n**Duration**: 6-8 hours\n**Skills**: Java, Javadoc, Mermaid diagrams, Markdown\n**Copilot Focus**: Bulk javadoc generation, architecture diagram creation, custom prompts for changelogs, custom agents for PR documentation review\n\nAutomate the documentation of the Widget Corp Inventory Manager -- a Java application with stale javadoc, a changelog that stopped being updated two versions ago, and zero architecture diagrams. Generate accurate javadoc, create Mermaid diagrams for architecture and data model, build a changelog prompt that works from code diffs, and create an agent that reviews PRs for documentation completeness.\n\n---\n\n### [Challenge 14: Pipeline Factory](./challenges/challenge-14-pipeline-factory/) ([Track](./tracks/challenge-14-pipeline-factory-track.md))\n\n**Team**: Solo or pair (DevOps, platform engineers, developers)\n**Duration**: 6-8 hours\n**Skills**: GitHub Actions, Node.js, Shell scripting, CI/CD concepts\n**Copilot Focus**: Workflow generation, `/fix` for debugging broken deployments, reusable workflow design, incident runbook prompts\n\nBuild CI/CD pipelines for TaskBoard, a kanban app that currently deploys via a shell script with commented-out scp commands. Create GitHub Actions workflows, debug 5 deliberate bugs in a broken staging deployment, build reusable workflow templates, and generate deployment gates with rollback mechanisms and incident runbooks.\n\n---\n\n### [Challenge 15: Backlog Generator](./challenges/challenge-15-backlog-generator/) ([Track](./tracks/challenge-15-backlog-generator-track.md))\n\n**Team**: Solo or pair (product owners, tech leads, scrum masters)\n**Duration**: 6-8 hours (no code required)\n**Skills**: Agile concepts (Epics, Stories, Acceptance Criteria), Jira/Confluence (optional)\n**Copilot Focus**: Custom prompts for spec-to-backlog conversion, custom agents for refinement, Atlassian Rovo MCP server for Jira/Confluence integration\n\nConvert three use case specifications of increasing complexity (Password Reset, Notification Preferences, Inventory Reorder) into structured backlogs. Build a reusable prompt that produces Epics, Stories, Tasks, and Test Cases following INVEST criteria. Create a refinement agent that reviews generated backlogs for gaps. Optionally push items directly to Jira using the Atlassian MCP server.\n\n---\n\n### [Challenge 16: Ops Assistant](./challenges/challenge-16-ops-assistant/) ([Track](./tracks/challenge-16-ops-assistant-track.md))\n\n**Team**: Solo or pair (support engineers, SREs, ops teams)\n**Duration**: 6-8 hours\n**Skills**: Log analysis concepts, incident management, basic Node.js (optional)\n**Copilot Focus**: Custom agents for log analysis, custom prompts for incident routing and runbook generation, error-to-plain-language translation\n\nBuild AI-assisted operations tooling for the Order Gateway -- a critical e-commerce service. Analyze two days of production logs containing payment timeouts, database deadlocks, connection pool exhaustion, and OutOfMemoryErrors. Create a log analysis agent that explains errors in plain language for non-technical support staff, build an incident routing prompt that maps errors to responsible teams, and generate troubleshooting runbooks from historical incident data.\n\n---\n\n### [Challenge 17: Spec-to-Ship Accelerator](./challenges/challenge-17-spec-to-ship/) ([Track](./tracks/challenge-17-spec-to-ship-track.md))\n\n**Team**: Solo or pair (tech leads, senior developers)\n**Duration**: 6-8 hours\n**Skills**: Full SDLC concepts, Node.js, GitHub Actions\n**Copilot Focus**: End-to-end prompt chain -- spec to backlog to technical analysis to code to tests to CI pipeline, custom agents for test specification\n\nCompress the full development lifecycle for a billing module on an existing multi-tenant SaaS platform. Start with a functional requirements document and an existing tenant management API. Build prompts that convert the spec into work items, generate a technical analysis against the existing codebase, implement the billing module from generated stories, create test specifications with a custom agent, and wire up a CI pipeline -- all producing reusable Copilot artifacts.\n\n---\n\n### [Challenge 18: COBOL Banking Modernization](./challenges/challenge-18-cobol-banking/) ([Track](./tracks/challenge-18-cobol-modernization-track.md))\n\n**Team**: Solo or pair (any developer role)\n**Duration**: 8-12 hours (Advanced)\n**Skills**: COBOL (no prior experience needed), Node.js/TypeScript or Java, React, reverse engineering, testing\n**Copilot Focus**: Legacy code comprehension with `/explain`, cross-language translation, characterization test generation, full-stack modernization\n\nReverse-engineer and modernize a core banking system written in COBOL -- the language that still runs the majority of the world's banking transactions. The system handles customer management, deposit accounts, teller transactions, consumer loans, interest calculation, and end-of-day batch processing. Understand the code, build characterization tests, extend it with new features, and translate it into a modern React + Node.js/Java web application while preserving every business rule.\n\n---\n\n### [Challenge 19: WCF Banking Modernization](./challenges/challenge-19-wcf-banking/) ([Track](./tracks/challenge-19-wcf-modernization-track.md))\n\n**Team**: Solo or pair (.NET developer)\n**Duration**: 6-10 hours (Intermediate to Advanced)\n**Skills**: C#, WCF/SOAP concepts, ASP.NET Core Web API, REST design, xUnit\n**Copilot Focus**: SOAP service contract comprehension, fault contract analysis, REST migration, characterization testing\n\nReverse-engineer a legacy WCF banking service (Meridian Savings Bank) built circa 2010-2012, now running on CoreWCF and .NET 8. Understand the service contracts, data contracts, and fault conditions, then port the business logic to a REST API using ASP.NET Core Web API. The service has real bugs to find and real decisions to make about whether to preserve or fix them during migration.\n\n---\n\n### [Challenge 20: PowerShell Automation](./challenges/challenge-20-powershell-automation/) ([Track](./tracks/challenge-20-powershell-automation-track.md))\n\n**Team**: Solo (sysadmin or IT Pro)\n**Duration**: 4-6 hours (Intermediate)\n**Skills**: PowerShell 7+, Pester 5, PSScriptAnalyzer, Az module, GitHub Actions\n**Copilot Focus**: Script comprehension, bug detection, error handling, test generation, module packaging, CI pipeline creation\n\nTake three inherited PowerShell scripts from the fictional Contoso IT team -- a stale account finder, a disk cleanup tool, and an Azure resource tagger -- and bring them up to production standard. Use Copilot to understand the code, fix bugs, add error handling and logging, write Pester tests, run static analysis, and wire everything into a GitHub Actions CI pipeline.\n\n---\n\n### Challenge 21: Azure Terraform Foundation ([Track](./tracks/challenge-21-azure-terraform-track.md))\n\n**Team**: Platform Engineers, DevOps Engineers, Cloud Engineers\n**Skills**: Terraform, Azure networking, managed identity, Key Vault, GitHub Actions\n**Copilot Focus**: Infrastructure review, plan explanation, module extraction, CI workflow generation\n\nBuild an Azure Terraform foundation across 5 phases: bootstrap remote state and naming rules, provision a small Azure platform around Container Apps, wire managed identity and Key Vault, refactor the configuration into reusable modules for multiple environments, then add CI guardrails and a drift response runbook.\n\n---\n\n## Learning Resources\n\n### Examples \u0026 Templates\n\n\u003e **[github/awesome-copilot](https://github.com/github/awesome-copilot)** - A curated collection of real-world examples including:\n\u003e - Custom instruction files (`.github/copilot-instructions.md`)\n\u003e - Custom agent templates (`.github/agents/`)\n\u003e - Reusable prompt files (`.github/prompts/`)\n\u003e - Best practices and patterns\n\n### GitHub Copilot Documentation\n\n- [Copilot Guide](./docs/copilot-guide.md)\n- [Prompt Engineering Guide](./docs/prompt-engineering.md)\n- [MCP Servers Guide](./docs/mcp-servers.md)\n\n### Quick Tips\n\n**Getting the Most from Copilot:**\n\n1. **Be Specific**: Detailed prompts yield better results\n2. **Provide Context**: Reference existing code and patterns\n3. **Iterate**: Refine suggestions through conversation\n4. **Use Chat Commands**: Use `/explain`, `/fix`, `/tests`, and natural language for documentation\n5. **Review Suggestions**: Always understand generated code\n6. **Keyboard Shortcuts**:\n - `Tab` - Accept suggestion\n - `Esc` - Dismiss suggestion\n - `Alt+]` - Next suggestion\n - `Alt+[` - Previous suggestion\n - `Ctrl+Shift+I` - Open Copilot Chat\n\n### Tips for Success\n\n1. **Write Clear Comments**\n\n   ```javascript\n   // ❌ Bad: \"do stuff\"\n   // ✅ Good: \"Validate email format and return true if valid, false otherwise\"\n\n   ```\n\n2. **Use Chat Freely** - Ask Copilot: \"What does this code do?\", \"How can I improve this?\"\n\n3. **Review Everything** - Understand all generated code, test thoroughly\n\n4. **Iterate** - First suggestion not perfect? Refine your prompt or try different approaches\n\n### Common Issues\n\n| Problem | Solution |\n|---------|----------|\n| Copilot not suggesting | Check status icon, ensure signed in, restart VS Code |\n| Wrong suggestions | Be more specific, provide more context, try chat instead |\n| Environment issues | Codespaces: rebuild container; Local: check tool versions |\n\n## Session Format\n\n### Track-Based Learning (Recommended)\n\n**Choose a track** based on your role and follow the curated path:\n\n- Each track provides a recommended sequence of challenges\n- Track-specific tips and guidance\n- Clear learning objectives\n- Estimated time for completion\n\nSee **[Tracks Overview](./tracks/README.md)** to choose your path.\n\n### Alternative: Individual Challenges\n\nPrefer to explore on your own?\n\n- Choose 2-3 challenges based on your interests\n- Each challenge includes starter code and objectives\n- Progressive difficulty with bonus tasks\n\n### Team Showcase (1-2 hours)\n\n- Present your solutions\n- Share interesting Copilot interactions\n- Discuss productivity gains and learnings\n- Compare experiences across different tracks\n\n### Best Practices Session (1 hour)\n\n- Review common patterns\n- Share tips and tricks discovered\n- Q\u0026A with Copilot experts\n\n## Success Metrics\n\nA successful RVAS delivery session produces:\n\n- **A demonstrable outcome** for each team -- working code, a shipped feature, modernized infrastructure, or documented automation.\n- **Articulated business impact** -- participants can state the outcome they drove and why it matters (faster delivery, reduced risk, lower toil).\n- **A path to adoption** -- the team can explain how they used Copilot to drive the outcome and has a concrete plan to apply the patterns to daily work, which is what turns a single session into sustained adoption.\n\nTrack activity metrics (Copilot usage, chat interactions) as supporting evidence, but judge success by the work result and the follow-on adoption plan.\n\n## Collaboration\n\n- Use GitHub Issues to ask questions\n- Share discoveries in Discussions\n- Help teammates learn new Copilot features\n- Document your journey in your challenge folders\n\n## Feedback\n\nAfter completing the session, please share:\n\n- What worked well\n- What could be improved\n- Productivity improvements you experienced\n- Features you found most valuable\n\n## Next Steps\n\nAfter the session:\n\n1. Apply Copilot to your daily work\n2. Explore advanced features and settings\n3. Create team-specific prompt collections\n4. Share knowledge with your organization\n5. Measure and track productivity improvements\n\n## Support \u0026 Resources\n\n### Quick Links\n\n- **[Choose Your Track](./tracks/README.md)** - Outcome-driven learning paths organized by role and outcome\n- **[Bring Your Own Challenge Kit](./byoc/README.md)** - Run an RVAS delivery session on your own codebase\n- **Challenge Set Builder** - Available on the published site; coaches can curate challenge sets and generate student URLs\n- **[Troubleshooting Guide](./TROUBLESHOOTING.md)** - Common issues and solutions\n- **[Facilitator Guide](./FACILITATOR_GUIDE.md)** - For RVAS delivery session organizers\n- **[Contributing Guide](./CONTRIBUTING.md)** - Help improve this content\n\n### Need Help?\n\n- **Which track?** See [Track Selection Guide](./tracks/README.md)\n- **Technical Issues**: Check [Troubleshooting Guide](./TROUBLESHOOTING.md)\n- **Copilot Questions**: Use Copilot Chat in VS Code\n- **General Help**: Review the `/docs` folder\n- **Found a Bug**: Create an issue in this repository\n\n---\n\n**Getting started:**\n\n1. [Choose Your Track](./tracks/README.md)\n2. Follow the [Setup Instructions](#step-2-set-up-environment) above\n3. [Verify Your Setup](#step-4-verify-your-setup)\n4. Start your first challenge!\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmicrosoft%2Ffrontier-ghcp-rvas","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmicrosoft%2Ffrontier-ghcp-rvas","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmicrosoft%2Ffrontier-ghcp-rvas/lists"}