Lesson 1 of 12
Structured learning draftCapabilities with Copilot
In GitHub Copilot for Developers, the way a learner handles capabilities shapes how Copilot is used and evaluated. A capability is a task an AI system can perform under stated conditions, not a universal guarantee. This intermediate lesson focuses on a decision or output that another person can inspect.
Learning objectives
- Explain capabilities in the context of GitHub Copilot for Developers.
- Apply Copilot to a bounded practical task.
- Evaluate the result using explicit quality criteria.
Capabilities: from context to evidence
Capabilities connects bounded input to a reviewed output in GitHub Copilot for Developers.
Define the purpose, intended user and Copilot constraints.
Compare representative inputs and record where performance changes.
Compare the observed result with a normal case, boundary case and stated limitation.
A capability is a task an AI system can perform under stated conditions, not a universal guarantee. For Copilot, distinguish performing an operation from demonstrating that it suits the stated purpose. Compare representative inputs and record where performance changes. Record assumptions that could change the conclusion.
Apply capabilities deliberately
- State the GitHub Copilot for Developers task and the decision it supports.
- Prepare a small Copilot case with a known input and difficult boundary.
- Compare representative inputs and record where performance changes.
- Compare the observed result with the expected behaviour and explain differences.
- Save the evidence, limitation and next action in a review record.
A worked Copilot evidence path
A four-step worked example for applying capabilities to Copilot, including a boundary test and revision.
Preserve the original Copilot case and expected result.
Confirm the basic path behaves as expected.
Expose an assumption in the capabilities method.
Change the method, rerun both cases and record the limitation.
| Review point | Evidence |
|---|---|
| Purpose | The specific Copilot outcome and intended user |
| Method | The capabilities decision, input and version or context |
| Result | Observed output plus a checked boundary case |
| Limitation | What the result does not establish and the next safe action |
Common mistakes
- Using Copilot before defining what capabilities must achieve.
- Checking only the easiest GitHub Copilot for Developers example.
- Reporting a result without its input, assumptions or limitation.
Practice activity
Apply the lesson
For GitHub Copilot for Developers, complete a bounded Copilot task demonstrating capabilities. Keep the original input, numbered method, normal test, boundary test, observed results and a 100-word self-review naming one limitation and next improvement.
Check your understanding
In GitHub Copilot for Developers, which evidence best supports a capabilities result produced with Copilot?
Lesson summary
- For GitHub Copilot for Developers, capabilities means: A capability is a task an AI system can perform under stated conditions, not a universal guarantee.
- A credible Copilot result includes a checked boundary, not only a successful example.
- The next lesson builds on this capabilities evidence record.
Sources and further reading
- AI Risk Management Framework 1.0NIST - accessed 2026-08-21
- AI PrinciplesOECD - accessed 2026-08-21
Personal study note