Skip to content
GitHub Copilot Train-the-Trainer
Overview

Session M7-05: Orchestrate agents and workstreams

Slides in new tab Download PDF

Module: Product and Delivery Teams

Difficulty: Intermediate

Prerequisites: Live GitHub Copilot app orchestration access; Sessions M7-01 to M7-04 for the product route, or Sessions M1-01 to M1-03, M2-01 to M2-04 and M2-05 for the developer route

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

Last updated: October 15, 2026

Overview

Use parent-led orchestration for one delivery objective. Split four live GitHub issues into independent workstreams, then monitor the child sessions and review their results.

If you are following the developer route after Session M2-05, review a local readiness evaluator, its tests, and a synthetic PR snapshot instead. You do not need a GitHub MCP connection or product-track artifacts for that route. Both routes use the same two-hour lab.

Each workstream needs a question, input paths or issues, a stop condition, and a reviewer. GitHub Copilot keeps session status, links, timing, and usage on the orchestration surface.

Live orchestration access is required. There is no role-play or prepared-result route.

Learning objectives

In this session, you will:

  1. Split one objective into independent workstreams.
  2. Set approved inputs and hard stop conditions.
  3. Start and monitor child sessions through /orchestrate.
  4. Redirect, stop, accept, or reject work.
  5. Return a reviewed parent result backed by the selected route's sources.
  6. Separate local test success from PR readiness in the developer route.

Session M5-01 distinction

Session M5-01 uses an optional framework for persistent roles and routing. Session M7-05 uses built-in orchestration for temporary workstreams. The parent reviews every result and keeps decision authority.

Materials

Resource Location
Trainer guide trainer-content/README.md
Slides slides.md
Lab guide lab/README.md
Learner assets lab/starter/
Reference solution lab/solution/

Required preflight

Check the built-in orchestrate skill and /orchestrate command in the GitHub Copilot app. Product learners also need GitHub MCP read access to their parent and child issues. Developers need Python 3.10 or later and local project read access instead.

Stop if orchestration or the selected route's source access is unavailable. Fix access before the lab.

Product-state note

Checked against official GitHub documentation on October 15, 2026. Interface labels can change by plan, policy, and app version. Use the current session management surface. The orchestration requirement does not change.

Official references