GitHub Copilot app Enablement Center
Accelerate your engineers, for all types of work
Your engineers hand the app a bug fix, a teammate's review, a flaky test investigation and a design doc, and all four run at the same time. They spend the day scoping work and reviewing results. This site shows your team how to get there.
One engineer's morning, five sessions in parallel (illustrative example)
- Fix for the checkout bug, pull request open
- Review of a teammate's pull request, comments drafted
- Flaky test traced to a race in the retry logic
- Design doc for the cache rewrite, first draft ready
- Sprint demo deck built from merged work
Where do you want to start?
How it works
The speed comes from running work in parallel
Each session gets its own workspace and branch. An engineer starts the next task while the last one runs, then reviews each result when it lands. One session can also split a job and start the others.
Several sessions at once
Give each task its own session. Review each one when it finishes, in any order.
Let the agent split the work
Ask for child sessions, or use /spawn and /fleet. Nested sessions sit under their parent.
Work across repositories
Select several projects or run /orchestrate to coordinate one change with a pull request per repository.
Keep it running on a schedule
Automations wake a session each day or week, so recurring work happens without anyone starting it.
Why now
AI is already part of how developers start
of new developers on GitHub use Copilot in their first week.
pull requests merged on GitHub in a year, a record and up 29% year over year.
Source: GitHub Octoverse 2025. A CoE turns that early habit into shared practice. See what that can look like →
All types of work
More than writing code
Most of an engineer's week goes to the work around the code. Bug investigations, design docs, triage, incident follow-up and the status update can each run in a session of their own. The same patterns work for the rest of the team.
Bug investigations
Hand off a vague bug report and get back a reproduction, a likely cause and a proposed fix.
Reviews
Read a teammate's pull request with a second pair of eyes, then post the comments you agree with.
Design docs and research
Compare approaches with a cited research report, then turn it into a design doc grounded in your code.
Docs
Fix stale READMEs and setup guides, and write release notes from what actually merged.
Triage and planning
Sort the issue backlog into themes and break an epic into issues the team can pick up.
Status updates and automations
Draft the weekly update from merged work, and let an automation run it every Friday.
Decks and Office files
Build the sprint demo deck in the PowerPoint canvas, or a Word or Excel file, without leaving the app.
Data analysis
Ask questions of logs, benchmarks or a CSV export and get a chart in the Excel canvas.
Start here
Pick your path
New to the app
A four-module learning path. Finish a real task in your first hour, then build the habits over a month.
Leading the rollout
Roles, cadence and metrics for running a Copilot app Center of Excellence.
Tracking progress
Work through Pilot, Expand, Scale and Optimize. Progress saves in your browser.
Your progressSetting it up
The admin guide: policies, models, MCP servers and plugins, then launch, training and scaling.
Looking for a prompt
Every prompt on the site in one place. Filter by role, feature or the metric you want to move.
Not sure where you are
Answer ten questions to find the rollout phase to focus on next.
Need templates
Admin briefing, launch emails, starter prompts, demo day formats and an ROI worksheet.
Choosing a tool
App, CLI, editor, automations or cloud agent. Start from the problem and pick the right one.
Use cases
Engineers first, then the whole team
Each role has a day-in-the-life walkthrough and prompts you can open straight in the app.
Engineer
Run several sessions at once across the whole job: code, reviews, bug investigations, design docs, triage and the weekly update.
23 use cases →Product manager
Turn feedback into specs, prototypes and release notes without waiting on an engineering slot.
11 use cases →Designer
Explore UI directions in code and review them in the integrated browser.
5 use cases →Marketing
Draft launch content, changelogs and demos grounded in what shipped.
6 use cases →Business & operations
Analyze data and build trackers, docs and decks in HR, finance and ops. No repository needed.
5 use cases →Sales
Prepare for accounts, build sales presentations and hear what customers are saying, without digging through tools.
6 use cases →Engineering manager
Track delivery, reduce toil and coach your team on agent workflows.
6 use cases →DevRel & support
Reproduce reports, write samples and answer questions faster.
9 use cases →Security & admin
Set policy, review configurations and keep sessions safe.
6 use cases →Rollout
From validation sprint to org-wide launch in a month
- Phase 1 · Weeks 1–2
Prove it (Pilot)
Run a short validation sprint that clears admin, security and support blockers for an org-wide launch.
12 checklist items → - Phase 2 · Weeks 3–4
Switch it on (Expand)
Turn the app on by default for everyone with a Copilot seat and get them to a first session.
13 checklist items → - Phase 3 · Months 2–3
Make it a habit (Scale)
Move everyone from a first session to weekly use, and make the app the default way teams start work.
10 checklist items → - Phase 4 · Ongoing
Compound it (Optimize)
Turn usage into measurable outcomes and keep improving.
5 checklist items →
See week-by-week playbooks for a team of 10 and an organization of 1,000 →