Prompt library

From inputs to useful outputs

Everyday work

Turn notes, documents and busy schedules into clear actions, briefings and plans.

Refreshed 9 October 2026 · Original prompt templates

Explore practical prompting guides →

Prompts to try

11 examples

01

Files

Turn these meeting notes into the email I need to send today

Use these meeting notes to draft a follow-up email for [team] under 250 words. Include decisions actually agreed, actions with recorded owners and dates, and unanswered questions. Label missing owners or dates as needing confirmation. Keep proposals separate from commitments and do not invent consensus. End with what recipients need to confirm. Draft only; do not send.

Make it yours: Include the meeting date and remove irrelevant personal information.

A useful follow-up

Make a separate checklist of my own confirmed actions for tomorrow.

02

Files

Prepare a decision meeting rather than a status meeting

Use these updates to create an agenda for [meeting]. Separate items needing a decision from information to read beforehand. For each decision include the owner, options, evidence and deadline. Move routine status details into a short pre-read. Flag decisions lacking enough information to resolve.

Make it yours: Tell the model who can actually approve each decision.

A useful follow-up

Which agenda item should be resolved asynchronously before the meeting?

03

Files

Find conflicting commitments across plans

Compare these project plans for conflicts in dates, resources and dependencies. Reference each conflicting entry. Distinguish a confirmed clash from a capacity assumption needing clarification. Propose the smallest scheduling change and identify who must decide before it can be applied.

Make it yours: Specify whether resource availability is fixed or estimated.

A useful follow-up

Which conflict would create the most downstream delay?

04

Files

Create a handover another person can use

Turn these notes into a handover for [person or role]. Include current status, next actions, file locations, dependencies and known failure modes. Separate confirmed facts from open questions. Check whether someone without our conversation history can identify what to do first.

Make it yours: Include the access or prerequisites the recipient will need.

A useful follow-up

What critical context is assumed but not actually written down?

05

Files

Separate meeting agreement from suggestions

Classify these meeting notes into decisions, proposals, objections, open questions and actions. Reference the passage for each decision. Mark unclear agreement for confirmation. Do not turn a suggestion into a commitment or erase a consequential objection to shorten the summary.

Make it yours: Share only notes you are authorised to process.

A useful follow-up

Which item is described as agreed but lacks evidence of agreement?

06

Files

Expose missing ownership in an action register

Create an action register from these notes with deliverable, owner, deadline, dependency and source reference. Use 'not assigned' and 'not agreed' for missing information. Do not assign ownership to whoever mentioned the task. Draft the clarification questions separately.

Make it yours: Explain which dates are firm commitments and which are suggestions.

A useful follow-up

Which action cannot start because a decision or input is still missing?

07

Text

Prepare a decision-first meeting agenda

Use these unresolved items to propose an agenda for [meeting purpose]. For each item state the decision needed, preparation, responsible contributor and suggested time box. Distinguish discussion from written updates. Keep proposed timing visibly separate from agreed commitments.

Make it yours: State who can actually make the decisions in the meeting.

A useful follow-up

What can we remove from the agenda without delaying a decision?

08

Files

Draft a follow-up that invites correction

Draft a follow-up from this verified decision record. Separate confirmed decisions, actions and questions needing confirmation. Preserve disputed details and missing owners. Use a neutral tone and provide a clear way to correct the record. Return a draft for review; do not send it.

Make it yours: Include the intended recipients and which details are appropriate for them.

A useful follow-up

Which sentence implies consensus or approval that the notes do not establish?

09

Files

Turn a messy meeting into decisions and actions

A concise follow-up with an action table and unresolved decisions.

Use the attached meeting notes to create a follow-up for [team]. Separate agreed decisions, proposed ideas and unresolved questions. For every action show the deliverable, owner and deadline; mark any missing owner or date as unassigned rather than guessing. Keep the follow-up under [length]. Add a short list of contradictions in the notes for me to resolve.

Make it yours: Label the meeting date and redact personal material that is irrelevant to the task.

A useful follow-up

Which actions depend on another decision? Put those dependencies into the action table.

10

Text

Create a realistic week from competing priorities

A schedule with explicit capacity limits and a fallback plan.

Build a weekly plan from [tasks], [fixed commitments] and [available working hours]. Ask about unclear deadlines or priorities first. Estimate time as ranges, reserve [buffer] for interruptions and identify what cannot fit. Produce a day-by-day plan with a minimum viable version for a disrupted week. Explain which tasks you deferred and why.

Make it yours: Include energy patterns and travel time, not just calendar availability.

A useful follow-up

I lost half of Wednesday. Adjust the plan while preserving the two most important outcomes.

11

Files

Convert a long document into a useful briefing

A decision-focused brief grounded in the supplied document.

Read the attached [document] for [audience], who need to decide [decision]. Produce a briefing with the recommendation, supporting evidence, risks and open questions. Reference file sections or page numbers for factual claims. Keep assumptions visibly separate. End with three questions the reader should ask before acting.

Make it yours: Name the decision. A briefing for a buyer should differ from one for an implementation team.

A useful follow-up

Highlight any sentence in the brief that the source does not directly support.

Step-by-step workflows