Recipes
Everyday Recipes
Use these prompts as starting points. Replace the bracketed parts, paste the source material, and revise the output shape for your situation.
Keep the conversation going
Microsoft Support
Key Facts
- Prompt recipes are starting points; replace every bracket with real context before using them.
- Use strict output shapes when you need an answer you can copy into a document, email, or table.
- For factual tasks, add source material and a verification instruction to the recipe.
Recipes are useful because they remind you what to include. They are not magic scripts. The best version is the one you edit for your real audience, source material, constraints, and desired output.
Summarize a document
Use when you have text and need the point, not a rewrite.
Summarize the text below for [audience].
Focus on: decisions, risks, numbers, deadlines, and open questions.
Output: 7 bullets maximum.
If a detail is not in the text, do not invent it.
Text:
[paste text] Draft an email
Use when tone and relationship matter.
Draft an email to [recipient] about [topic].
Context: [relationship, situation, desired outcome].
Tone: [warm/direct/formal/apologetic].
Constraints: under [word count], no jargon, no overpromising.
Output: subject line plus email body. Edit for clarity
Use when you want improvement without changing meaning.
Edit the draft below for clarity.
Keep the meaning and facts unchanged.
Make it easier to scan.
Return:
1. Revised draft
2. Three most important edits you made
Draft:
[paste draft] Plan a project
Use when you need tasks, order, and risks.
Create a project plan for [goal].
Context: [timeline, people, budget, constraints].
Output: table with Phase, Task, Owner, Deadline, Risk.
Before the plan, ask up to 3 questions if missing details would change the plan. Learn a topic
Use when the explanation should match your background.
Teach me [topic].
My background: [what I already know].
Goal: [why I need to learn it].
Style: simple, concrete, no jargon until the end.
Output: explanation, example, common misconception, 3-question quiz. Compare options
Use when you need a decision aid, not a decision handed down.
Compare these options: [A], [B], [C].
Criteria: [cost, speed, risk, quality, maintenance].
Context: [your situation].
Output: table, then recommendation with assumptions.
Mark anything that needs verification. Turn notes into actions
Use after meetings, calls, or messy brainstorming.
Turn these notes into action items.
Output columns: Action, Owner, Due date, Dependency, Confidence.
If owner or date is missing, write "Unassigned" or "No date."
Do not add tasks that are not implied by the notes.
Notes:
[paste notes] Brainstorm ideas
Use when you want range before judgment.
Brainstorm [number] ideas for [goal].
Audience: [who it is for].
Constraints: [budget, time, tools, tone].
Give a mix of safe, unusual, and high-effort ideas.
After the list, pick the 3 strongest and explain why. How to edit a recipe
Replace every bracket with real information. Delete parts you do not need. Add one source block if facts matter. Make the output shape strict when you need to use the answer directly. Keep the first response if it is useful, and use follow-up prompts when it misses.
When not to use a recipe
Do not use a recipe to avoid thinking about the task. If the situation is sensitive, novel, or high-stakes, slow down. Start by asking the model what information it would need, then decide what to share. For legal, medical, financial, safety, or public factual claims, use AI for drafting and organization, not as the final authority.