Module 4: GitHub MCP Integration
Duration: ~20 min total · 2 lessons
Specs are most powerful when they live where your work happens. Module 4 connects your spec-driven workflow to GitHub Issues — so your tasks become trackable work items, and GitHub Issues can feed context back into Copilot generation.
Lessons
| # | Title | Focus | Time |
|---|---|---|---|
| L4.1 | What Is MCP and Why It Matters | MCP concepts, GitHub MCP setup | ~8 min |
| L4.2 | The Write-Read Loop | Push tasks to Issues, read Issues as context | ~12 min |
What You'll Build
By the end of Module 4, you will have:
- GitHub MCP configured in your VS Code workspace (
.vscode/mcp.json). - Spec tasks pushed to GitHub Issues — your spec and your project tracker are in sync.
- Code generated using an Issue as context — so Copilot pulls structured requirements directly from GitHub.
Module Outcome
The spec-driven workflow from M3 extends into GitHub. You write tasks in the spec, push them to Issues, and generate from Issues. Changes to requirements flow back into the spec. The spec and the tracker are never out of sync.