The internet is drowning in "100 Copilot prompts" listicles. They don't work, and here's why: a prompt is not a magic spell you copy. It's a set of mechanics, and once you understand the five that matter, you can write your own prompts faster than you can search a listicle.
These mechanics follow directly from how Copilot works — retrieval first, reasoning second (if that's not your mental model yet, read the grounding guide first). Everything below assumes it.
Mechanic 1: Retrieval targeting
Copilot can only reason over what retrieval surfaces. The first job of your prompt is to make the right content findable, and retrieval matches your words against the content's words. Generic vocabulary retrieves generic chunks.
Two moves:
- Use proper nouns. Project names, document titles, people, customer names, the exact jargon your org uses. "The Helios migration" retrieves; "our cloud project" gambles.
- Pin sources when you know them. The
/ file picker, named people, named meetings. Pinning skips the retrieval lottery entirely — the source is guaranteed to be in the briefing pack.
BEFORE: What are the main risks in our vendor situation?
AFTER: Using /Q3-Vendor-Assessment and the emails from Priya Sharma
about the Northwind contract, list the top 5 vendor risks we
identified, with the mitigation owner for each.
The before version forces Copilot to guess which of your tenant's ten thousand documents "vendor situation" means. The after version hands it the exact briefing pack. Same model, wildly different odds.
If you can name the source, name it. Every unnamed source is a coin flip you didn't have to take.