Skip to content
GitHub Copilot Train-the-Trainer
Overview

Session M7-01: Work effectively in the GitHub Copilot app

Slides in new tab Download PDF

Module: Product and Delivery Teams

Difficulty: Beginner

Prerequisites: A GitHub account with GitHub Copilot access

Duration: 3 hours (1 hour trainer content + 2 hours lab)

Overview

Start the Delivery Decision Studio path by comparing answers with and without repository context. Save what you learn in an initiative context brief. You will check context usage, request an independent critique, and test whether a fresh session can use the brief without the original chat.

The fictional Service Request Portal provides the shared scenario. Learners may use approved, sanitized work from their own team.

Important

The GitHub Copilot app is required. Fix access, policy, or client problems before the lab.

Learning outcomes

By the end of this session, learners can:

  1. Find and use Chats, Projects, My work, Search, Automations, and Customize.
  2. Choose Interactive, Plan, or Autopilot mode for a task with a defined scope.
  3. Add files with @, reference issues with #, and open commands with /.
  4. Choose repository, issue, file, or uploaded-document context for a question.
  5. Inspect the skills, agents, MCP servers, plugins, and canvases available in their environment.
  6. Explain the difference between an MCP connection and a plugin package.
  7. Check context usage and decide whether to compact or start fresh.
  8. Review and revise a proposed Markdown change.
  9. Update a context brief when the owner approves new source information.
  10. Use independent critique before sharing the brief.

Session structure

Block Duration Material
Trainer content 1 hour Trainer guide
Lab 2 hours Lab guide

Materials

Resource Location
Slides slides.md
Starter initiative and brief template lab/starter/
Reference brief and context review lab/solution/

Boundaries

  • Use only synthetic or approved, sanitized material.
  • Treat Copilot output as a proposal until the learner checks its source.
  • Keep write actions reviewable and reversible.
  • Do not require programming, Git command-line work, or extension development.
  • Do not use customer data or source organization names.
  • Delivery Decision Studio is the learning path. Service Request Portal is the initiative.