Pick the project you named in Lesson 1. The pack is the briefing you are tired of repeating.
What a smart new colleague would need.
Include: what this is, who it is for, decisions already made, constraints, and open questions. Leave out the archive.
Volatile facts (this week’s numbers, one customer’s last email) do not belong in a standing pack. Those you paste fresh.
Core principles
- Audience, goal, and what “done” looks like for this project.
- Decisions already made — so Copilot does not reopen them.
- Constraints: brand, legal, systems, people who must review.
- Open questions labeled as open. Copilot should not invent answers to them.
Check yourself
What should you keep out of a standing project pack?
Standing packs hold durable briefing. Volatile facts you paste into the chat so the file does not lie next week.
Do this in Copilot
Save one project pack under 300 words. If it is longer, you included an archive. Cut it.
Save as a separate file from About Me. Attach it only when that project is in play.
Draft the project pack
Help me write a project context pack for Copilot for this project: [PROJECT NAME]. Interview me one question at a time. Then write instructions under 300 words covering: what this is, who it is for, decisions already made, constraints, and open questions (labeled as open — do not invent answers). If I paste notes, use only what I provide: [OPTIONAL NOTES].
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Install and Compare →
Navigate: press j for next lesson,k for previous.