Section 6: Wrap-Up and Q and A

Minutes 85 to 90. Two slides and exactly 5 minutes. There is no buffer here, so section 6 starts on time or it does not finish.

Objectives served

  • O1. Understand the core capabilities of GitHub Copilot
  • O2. Differentiate between Copilot Chat, Code Completions, and Agent Mode
  • O3. Apply basic prompt engineering techniques
  • O5. Evaluate and review AI-generated outputs responsibly
  • O6. Confidently begin incorporating AI-assisted development into their daily workflows

Run of show

Slide Minutes Activity
S21. What You Take Away 85 to 87 Recap, then write the exit ticket
S22. Next Steps and Questions 87 to 90 Point at the resources, then take questions

Key takeaways

  • It drafts. You decide what is kept.
  • Choose the surface: ask to understand, edit to change, agent to span files.
  • A prompt without acceptance tests is a wish.
  • The evidence is the diff and the actual test output, not the summary.

The exit ticket

Each participant records two things on the prepared form:

  1. One bounded task they will attempt tomorrow.
  2. How they will verify the result.

A task submitted with no verification step goes back, because the verification is the objective. Collect the tickets on the prepared form so that responses are retained, rather than on a shared screen where other people’s answers are visible. Paper index cards collected at the door are an adequate fallback.

Acceptance

  • Mechanical gate: the form records one bounded task and one verification step.
  • Judgment gate: the facilitator judges that the task is achievable in a single day.

Questions

Questions cluster on entitlement, on using Copilot with private code, and on review duty. Answer the first two by pointing at the resources page rather than by speculating.

If a question asks about using Copilot with customer or regulated material, say that it is out of scope for this session and that it is a data-handling decision with its own owner. Do not improvise a policy answer.

Next

Return to the home page or read the facilitator runbook.


This site uses Just the Docs, a documentation theme for Jekyll.