Give Copilot a clearer brief
Describe the work, the available material and the result you need from Copilot.
Match the prompt to the Copilot you use
Microsoft Copilot, Microsoft 365 Copilot and GitHub Copilot serve different workflows. Name the actual product and task before generating an instruction. A coding request needs repository context; a document brief needs the material the chosen Copilot can access.
| Work | Useful context |
|---|---|
| Document summary | The selected document, audience and decisions needed |
| Meeting follow-up | Authorized notes, participants and action criteria |
| Code change | Repository scope, expected behavior and tests |
Turn meeting notes into an accountable follow-up
Paste or select only notes you are allowed to use. This example keeps proposed next steps separate from recorded commitments.
From the meeting notes I provide, draft a follow-up for the project team. Separate confirmed decisions, assigned actions and unresolved questions. For each action, include an owner and deadline only if the notes state them; otherwise write "Needs confirmation". Link or quote the supporting note where possible. Do not send the message. Keep the draft under 250 words.
The prompt does not create permissions
A prompt cannot unlock a Microsoft license, retrieve an inaccessible file or establish permission to send a message. Review names, dates and recipients before using the result.
The examples on this page are free to read. Prompeteer generation and Copilot product access remain subject to their respective plans and limits.
Common questions
Is this an official Microsoft product?
No. Prompeteer helps prepare prompts for supported tools. Microsoft and GitHub own their respective Copilot products.
Can the same prompt work in every Copilot?
The task may transfer, but available context and actions differ. Adapt the instruction to the specific Copilot and verify its permissions.
Sources and review
Reviewed