AI Prompt Library
500 tested prompts for M365 Copilot, ChatGPT, Claude & more
4,200 prompts copied
☕ Support
💬 Copilot in Teams
▾
Channel Announcement Post
Draft a professional Teams channel announcement for a change, update, or new initiative
IntermediateDraft a Teams channel post announcing [CHANGE OR UPDATE]. Include: what is changing, when it takes effect, who is affected, what they need to do, and where to ask questions. Use a professional but approachable tone. Add relevant emoji for visual scanning. Keep it under 200 words.
▸
Chat Thread to Status Update
Convert a messy Teams chat thread into a clean status update for stakeholders
BeginnerTurn this Teams chat thread into a concise status update I can share with [AUDIENCE]. Include: current status, blockers, decisions made, and next steps. Format as a professional update, not a conversation summary. Keep it under 150 words.
▸
Compare Meetings — Progress Check
Compare promises from a previous meeting with what was actually delivered
AdvancedCompare what was committed in our [PREVIOUS MEETING DATE] meeting with what has been delivered as of today. For each action item: state the original commitment, current status (done, in progress, overdue), and who is responsible. Highlight anything overdue or at risk.
Summarise this standup conversation into a formatted update. For each team member capture: (1) What they completed yesterday, (2) What they are working on today, (3) Any blockers. Add a team summary at the top with overall progress and a list of blockers that need escalation.
▸
Extract Unresolved Questions
Pull out all unanswered questions and follow-ups from a meeting transcript
IntermediateReview this meeting transcript and list: (1) Questions that were asked but not answered, (2) Topics that need further discussion, (3) Decisions that were deferred, (4) Items where someone said "I will check" or "Let me get back to you." Present as a numbered list with the person responsible.
▸
Meeting Preparation Briefing
Get Copilot to prepare you for an upcoming meeting using recent context
AdvancedPrepare me for my upcoming meeting with [PERSON OR TEAM]. Summarise: (1) What we discussed in our last meeting, (2) Any outstanding action items, (3) Recent emails or chats between us, (4) Key topics I should raise. Present as a one-page briefing.
▸
Meeting Recap Email from Transcript
Turn a Teams meeting transcript into a professional recap email
BeginnerTurn this Teams meeting transcript into a recap email for [RECIPIENTS]. Include: (1) Meeting purpose and attendees, (2) Key discussion points (3-5 bullets), (3) Decisions made, (4) Action items table (task, owner, deadline), (5) Next meeting date if scheduled. Tone: professional, concise. Under 200 words.
▸
Meeting Summary with Action Items
Turn a Teams meeting transcript into a structured summary with decisions, actions, and owners
BeginnerSummarise this meeting into: (1) Key decisions made, (2) Action items with owners and deadlines in a table, (3) Open questions or unresolved issues, (4) Next steps. Keep each section to 3-5 bullet points maximum.
Summarise this retrospective discussion. Extract: top 3 things that went well, top 3 improvements, specific action items with owners, and overall team sentiment.
Create a Teams poll for [DECISION]. Include: clear question, 3-5 options, context, deadline for voting, and how to proceed based on results.
Review our recent team conversations and provide a sentiment check. Identify: (1) Overall team mood (positive, neutral, stressed), (2) Topics generating the most discussion or concern, (3) Team members who might need support (high workload signals, frustrated language), (4) Positive moments to celebrate. Note: this is for my awareness as a manager, not surveillance. Present diplomatically.
Summarise this Teams channel activity from the past week into a digest. Include: (1) Key announcements or decisions, (2) Questions asked and whether they were answered, (3) Files or resources shared, (4) Action items mentioned, (5) Unanswered questions that need follow-up. Format as a scannable digest for people who were too busy to follow the channel.
📧 Email Prompts
▸
Cold Outreach Email
Draft a compelling cold outreach email that gets opened and replied to
IntermediateDraft a cold outreach email to [RECIPIENT ROLE] at [COMPANY] about [YOUR OFFERING]. Structure: (1) Subject line — personalised, curiosity-driven, under 8 words, (2) Opening — reference something specific about their company or role (show you did research), (3) Value prop — one clear sentence on what you offer and why it matters to them, (4) Social proof — one brief example or metric from a similar company, (5) CTA — one specific, low-commitment ask (15-min call, not "let me know"). Keep the entire email under 120 words. No attachments, no links in first email.
▸
Customer Apology Email
Draft a sincere apology email that acknowledges the issue, takes responsibility, and rebuilds trust
BeginnerDraft an apology email to a customer regarding [ISSUE]. The email must: (1) Acknowledge the problem specifically — do not be vague, (2) Take responsibility without making excuses, (3) Explain what happened in simple terms, (4) Detail what we are doing to fix it right now, (5) Describe what we are doing to prevent it from happening again, (6) Offer appropriate compensation or goodwill gesture if applicable, (7) Provide a direct contact for follow-up. Tone: sincere, empathetic, professional. Keep under 200 words.
Draft an email delivering: [BAD NEWS]. Include: (1) State the news directly first, (2) Explain the reason briefly, (3) Acknowledge impact, (4) Outline what we are doing, (5) Next steps, (6) Offer to discuss. Tone: empathetic, direct, accountable.
▸
Email Thread Summariser
Summarise a long email thread into key points, decisions, and action items
BeginnerSummarise this email thread concisely. Include: (1) Topic — what this thread is about in one sentence, (2) Participants — who is involved and their roles, (3) Timeline — when it started and key dates mentioned, (4) Key Points — the main arguments or updates from each participant, (5) Decisions Made — any agreements or approvals, (6) Action Items — tasks with owners, (7) Current Status — where things stand right now, (8) My Required Action — what I specifically need to do next.
▸
Internal Announcement Email
Draft a clear, engaging internal announcement for company-wide or team communications
BeginnerDraft an internal announcement email about [TOPIC] for [AUDIENCE — all staff / department / leadership]. Structure: (1) Subject line — clear and informative, (2) Opening — what is happening and why it matters, (3) Key Details — the who, what, when, where in bullet points, (4) Impact — how this affects the audience specifically, (5) Action Required — what people need to do (if anything), (6) Timeline — key dates, (7) FAQ — 3 anticipated questions with answers, (8) Contact — who to reach out to for questions. Tone: [professional / excited / reassuring — depending on the news].
▸
Issue Escalation Email
Draft a clear, professional escalation email that gets results without burning bridges
IntermediateDraft an escalation email about [ISSUE] to [RECIPIENT/ROLE]. Structure it as: (1) Subject line that conveys urgency without alarm, (2) Brief context — what the issue is and when it started, (3) Impact — how this is affecting the business/team/customer right now, (4) Actions already taken — what has been tried so far, (5) Specific ask — exactly what you need from the recipient, (6) Deadline — when a response or action is needed by. Tone: factual, urgent but professional, solution-oriented. Avoid blame.
Draft an email negotiating [WHAT — pricing / terms / timeline / scope] with [RECIPIENT]. Be firm but fair. Present your position with reasoning, propose a compromise, and keep the relationship positive.
▸
Polite Decline Email
Professionally decline a request, invitation, or proposal while maintaining the relationship
BeginnerDraft a polite but clear email declining [REQUEST/INVITATION]. The email should: (1) Thank them for thinking of me/us, (2) Clearly state that I am unable to accept, (3) Give a brief, professional reason without over-explaining, (4) Offer an alternative if appropriate — suggest another person, different timing, or a smaller commitment, (5) End on a positive note that keeps the door open for future opportunities. Tone: respectful, warm, definitive. Keep under 120 words.
▸
Post-Meeting Follow-Up Email
Draft a professional follow-up email summarising what was discussed and next steps
BeginnerDraft a follow-up email after my meeting about [TOPIC] with [ATTENDEES]. Include: (1) Thank them for their time, (2) Summarise the key points discussed (3-4 bullets), (3) List the agreed action items with owners and deadlines, (4) Confirm the next meeting date if one was scheduled, (5) Attach or reference any documents mentioned. Tone: professional, warm, action-oriented. Keep it under 200 words.
▸
Priority Email Triage
Quickly triage and respond to your most important emails with AI-drafted replies
BeginnerReview my unread emails and identify the top 5 that need my attention most urgently. For each one: (1) Sender and subject, (2) Why it is urgent — deadline, escalation, decision needed, (3) Suggested response — a draft reply I can review and send, (4) Estimated time to handle. Sort by urgency with the most critical first.
▸
Professional Email Rewrite
Transform a casual or rough email draft into a polished, professional message
BeginnerRewrite this email in a professional tone that conveys urgency without being aggressive. Keep it under 150 words. Maintain the core message but make it suitable for a senior leadership audience. Preserve any specific dates, numbers, or action items mentioned.
Write a thank you to [RECIPIENT] for [WHAT]. Make it: (1) Specific about impact, (2) Genuine, (3) Under 100 words, (4) Include forward-looking statement. Avoid generic phrases.
Draft an email asking [PERSON] to be a reference for [OPPORTUNITY]. Include: why you are asking them specifically, what the opportunity is, what topics they might be asked about, and make declining easy.
Write an introduction connecting [PERSON A] and [PERSON B]. Include: (1) Context on why they should connect, (2) One sentence about each person, (3) Suggestion for what to discuss, (4) Make it easy to reply. Tone: warm, brief.
📧 Copilot in Outlook
I have [NUMBER] emails that need responses. For each email: read the context, draft a concise reply that addresses their question or request, and match the appropriate tone (formal for external, casual for team). Flag any emails that need more information from me before responding. Show all drafts for my review before sending.
▸
Brief Email Summary for My Manager
Create a quick summary of an email thread that your manager can read in 30 seconds
BeginnerWrite a brief overview of this email for my manager. Include: what it is about, what decision or action is needed from us, and the deadline if mentioned. Keep it to 3-4 sentences maximum. Tone: factual and concise.
▸
Draft a Polite Decline
Write a professional and empathetic decline email that maintains the relationship
BeginnerDraft a reply declining this request. Be polite and empathetic. Briefly explain why I cannot help with this right now, suggest an alternative if possible, and keep the door open for future collaboration. Tone: warm but clear. Keep it under 100 words.
Create [NUMBER — 5 / 10] email templates for common workplace scenarios in my role as [ROLE]. For each template: (1) Scenario description, (2) Subject line, (3) Email body with [PLACEHOLDERS], (4) Tone guidance, (5) When to use vs customise heavily. Cover: requests, follow-ups, introductions, thank-yous, and bad news delivery.
▸
Email Thread to Action Items
Extract every commitment and action item from a long email chain
IntermediateReview this email thread and extract all action items, commitments, and follow-ups. For each item list: what needs to be done, who committed to it, and any deadline mentioned. Present as a table. Flag anything that seems overdue.
Design inbox rules for my Outlook to automatically organise my email. I receive emails from: [DESCRIBE MAIN SOURCES — team, clients, newsletters, alerts, HR]. Create rules for: (1) Priority routing (VIP senders to focused inbox), (2) Auto-categorisation by project or topic, (3) Newsletter and notification management, (4) Alert handling. Include the rule logic and folder structure.
▸
Make My Reply More Professional
Let Copilot coach your email draft to be clearer, more polished, and appropriate
BeginnerRewrite my draft reply to be more professional and easier to read. Keep my key points but improve the tone, structure, and clarity. If anything sounds too blunt or too passive, fix it. Keep the same length.
Draft a decline for this meeting. Include: polite reason, ask for notes after, offer async input, suggest alternative time if topic is important.
▸
Reply Requesting Missing Details
Draft a professional follow-up asking for the specific information you need
IntermediateDraft a reply to this email asking for the missing information I need to move forward. I specifically need: [LIST WHAT YOU NEED]. Be polite but clear about what is blocking progress. Include a deadline if needed. Tone: professional and direct.
Find a [DURATION]-minute meeting slot for [ATTENDEES] in the next [TIMEFRAME — week / 2 weeks]. Preferences: (1) Avoid [DAY/TIME], (2) Prefer [MORNING/AFTERNOON], (3) Allow for time zone differences if applicable. Draft a meeting invite with: clear purpose, agenda (3 items max), and any pre-read materials to attach.
▸
Summarise Long Email Thread
Get a concise executive summary of a lengthy email conversation
BeginnerSummarise this email thread into: (1) The original request, (2) Key decisions made, (3) Current status, (4) What needs to happen next. Keep it under 100 words so I can quickly understand this thread.
Summarise my most important emails from this week. Group by: requires response, FYI updates, action items from others, upcoming deadlines. Skip newsletters.
🎥 Meeting Prompts
Prepare for my upcoming 1:1 meeting with [PERSON]. Create a structured agenda that includes: (1) Check-in — an icebreaker question and general wellbeing check, (2) Their Updates — space for them to share wins, challenges, and blockers, (3) My Updates — key information I need to share with them, (4) Review Actions — status of action items from our last 1:1, (5) Discussion Topics — [LIST ANY TOPICS], (6) Career Development — one question about their growth and goals, (7) Feedback — one piece of positive reinforcement and one constructive observation, (8) Action Items — space to capture new actions. Allocate time for a 30-minute meeting.
Help me prepare for a difficult meeting about [TOPIC]. Include: (1) My opening statement, (2) Key points to make, (3) Anticipated objections and responses, (4) Ground rules to set, (5) Desired outcome, (6) Plan if things go off track.
▸
Meeting Agenda Builder
Create a structured meeting agenda with time allocations and expected outcomes
BeginnerCreate a structured meeting agenda for a [DURATION]-minute [MEETING TYPE] meeting. Include: (1) Meeting objective — one clear sentence, (2) Attendees and their roles, (3) Agenda items with time allocations that add up to [DURATION] minutes, (4) For each item: topic, presenter, expected outcome (decision, discussion, or FYI), (5) Pre-read materials or preparation needed, (6) Leave 5 minutes for wrap-up and action items. Topic: [TOPIC].
Calculate the cost of this meeting: [NUMBER] attendees with average salary [AMOUNT/YEAR], meeting duration [MINUTES], happening [FREQUENCY]. Show: (1) Cost per meeting, (2) Annual cost, (3) Opportunity cost (what else could these people be doing), (4) Is this meeting worth the cost? (5) Suggestions to reduce cost (fewer attendees, shorter, async alternative).
Review this meeting [TRANSCRIPT/NOTES] and extract every decision made. For each: (1) Decision statement, (2) Who decided, (3) Rationale given, (4) Impact or implications, (5) Dissenting opinions if any, (6) Review or revisit date if mentioned. Present as a numbered decision log the team can reference.
Create a facilitation plan for a [TYPE — difficult conversation / brainstorm / decision meeting / conflict resolution] about [TOPIC]. Include: (1) Pre-meeting preparation, (2) Ground rules to set, (3) Opening statement, (4) Discussion structure and timing, (5) Techniques to manage dominant speakers, (6) How to handle disagreement, (7) Decision-making method, (8) Closing and action capture.
▸
Meeting Notes to Action Items
Extract clear action items with owners and deadlines from messy meeting notes
BeginnerReview these meeting notes and extract all action items. For each action item, provide: (1) Task — what needs to be done, (2) Owner — who is responsible, (3) Deadline — when it's due (if mentioned), (4) Priority — High, Medium, or Low based on context. Format as a clean table. If no deadline was mentioned, suggest a reasonable one based on the urgency implied.
▸
Meeting Preparation Briefing
Get a comprehensive briefing on attendees, context, and talking points before any meeting
IntermediateI have a meeting with [ATTENDEES] about [TOPIC] scheduled for [DATE/TIME]. Prepare a briefing that includes: (1) Recent email threads and Teams messages related to this topic, (2) Any shared documents or files relevant to the discussion, (3) Key talking points I should raise, (4) Open questions or unresolved items from previous conversations, (5) Suggested agenda with time allocations.
Generate 10 retrospective questions for a team that just completed [PROJECT/SPRINT]. Mix: celebration, improvement, process, team dynamics, and forward-looking questions. Avoid yes/no questions.
▸
Sprint Planning Document
Create a collaborative sprint planning document with goals, backlog items, and capacity
IntermediateCreate a sprint planning document for Sprint [NUMBER] ([DATE RANGE]). Include: (1) Sprint Goal — one clear objective, (2) Team Capacity — available days per team member accounting for leave/holidays, (3) Carried Over Items — unfinished work from last sprint, (4) New Backlog Items — prioritised list with story points/effort estimates, (5) Sprint Commitments — what we are committing to deliver, (6) Risks & Dependencies — anything that could block delivery, (7) Definition of Done — acceptance criteria for this sprint. Format as a collaborative document with checkboxes for tracking.
▸
Team Morale Pulse Check
Conduct a structured team wellbeing check using thoughtful questions and analysis
IntermediateHelp me run a team morale pulse check. Create: (1) A set of 8-10 anonymous survey questions covering workload, team dynamics, growth opportunities, communication, and overall satisfaction — use a mix of 1-5 scale and open-ended, (2) An introduction message explaining why we are doing this and that it is genuinely anonymous, (3) A framework for analysing the results — what scores indicate action needed, (4) Response templates for common scenarios: high morale (celebrate), mixed signals (investigate), low morale (urgent action plan), (5) Follow-up actions — specific interventions for each concern area. Tone: caring, genuine, non-corporate.
▸
Teams Meeting Recap
Get a structured recap of a Teams meeting with decisions, action items, and follow-ups
BeginnerCreate a comprehensive recap of the meeting that just ended. Include: (1) Meeting Title and Attendees, (2) Key Topics Discussed — summarise each agenda item, (3) Decisions Made — list every decision with who made it, (4) Action Items — table with Task, Owner, Deadline, (5) Open Questions — anything unresolved that needs follow-up, (6) Next Meeting — date and preliminary agenda items. Format this ready to share in the Teams channel.
📝 Copilot in Word
Create a business proposal template for [TYPE — consulting / project / partnership / grant]. Include: (1) Cover page, (2) Executive summary, (3) Problem statement, (4) Proposed solution, (5) Methodology and approach, (6) Timeline and deliverables, (7) Team and qualifications, (8) Pricing, (9) Terms and conditions, (10) Appendices. Format with proper headings and professional styling.
▸
Convert Notes to FAQ Document
Transform meeting notes or knowledge into a structured FAQ format
IntermediateConvert these notes into an FAQ document with clear questions and concise answers. Group related questions under headings. Start with the most commonly asked questions. Include 10-15 Q&A pairs. Each answer should be 2-3 sentences maximum.
▸
Draft a Standard Operating Procedure
Turn rough notes into a professional SOP document with proper structure
BeginnerDraft a standard operating procedure (SOP) for [PROCESS NAME] based on these notes. Include: (1) Purpose and scope, (2) Prerequisites, (3) Step-by-step procedure with numbered steps, (4) Common exceptions and how to handle them, (5) Who to contact for help. Use clear, non-technical language. Format with headings and bullet points.
▸
Executive Summary Generator
Condense a long document into a crisp executive summary with key takeaways
BeginnerSummarise this document into an executive summary for [AUDIENCE — leadership / board / client]. Include: (1) The headline finding or recommendation (one sentence), (2) 3-5 key takeaways as bullet points, (3) Recommended next steps. Keep the entire summary under 200 words. Prioritise decisions over details.
Write formal meeting minutes for [MEETING NAME] held on [DATE]. Include: (1) Meeting details (date, time, location, attendees, apologies), (2) Agenda items discussed with summary, (3) Motions or decisions with voting results if applicable, (4) Action items with owners and deadlines, (5) Next meeting date, (6) Approval section. Format as an official record.
▸
Make This Shorter and More Direct
Tighten up a wordy document while keeping all essential information
IntermediateMake this document more concise and direct. Cut unnecessary words, merge redundant sections, and remove filler phrases. Keep all essential information and key points. Target a [PERCENTAGE — 30% / 50%] reduction in word count. Use active voice throughout.
▸
Policy Plain English Rewrite
Rewrite a complex policy document in plain, accessible English
IntermediateRewrite this policy document in plain English: [PASTE OR DESCRIBE POLICY]. Keep all requirements and obligations exactly the same but: (1) Replace jargon with simple words, (2) Break long sentences into shorter ones, (3) Use bullet points instead of dense paragraphs, (4) Add headings for each major section, (5) Include a quick reference summary at the top. Target: readable by someone with no specialist knowledge.
Draft a formal business letter from [SENDER] to [RECIPIENT] regarding [PURPOSE]. Include proper formatting, clear purpose, supporting details, call to action.
Design the structure for a [REPORT TYPE — annual / quarterly / research / audit / project completion] report about [TOPIC]. Include: (1) Recommended sections with headings, (2) What to include in each section, (3) Target length per section, (4) Charts or visuals to include, (5) Appendices needed. Optimise the flow so the most important findings are early in the document.
▸
Review and Suggest Improvements
Get Copilot to review your draft and suggest tracked changes for clarity and tone
AdvancedReview this document and suggest improvements to clarity, tone, and structure. Focus on: (1) Sentences that are too long or confusing, (2) Passive voice that should be active, (3) Sections that could be reordered for better flow, (4) Missing information the reader would expect. Present your suggestions as specific edits, not general advice.
▸
Rewrite in Plain English
Simplify complex or jargon-heavy text for a non-technical audience
IntermediateRewrite this section in plain English for [AUDIENCE — non-technical staff / customers / new hires]. Remove jargon and acronyms (or explain them on first use). Keep the meaning exactly the same but make it easy to understand on first read. Aim for an 8th-grade reading level.
Create a handover document for my role as [ROLE]. Include: key responsibilities, important contacts, active projects, pending decisions, file locations, tips and gotchas.
📝 Summarising Prompts
▸
All-Hands Meeting Summary
Create a digestible summary of an all-hands or town hall meeting for those who could not attend
BeginnerCreate a summary of the all-hands meeting for distribution to the team. Include: (1) Key Announcements — the most important news and updates, (2) Company Performance — any metrics, results, or targets shared, (3) Strategic Updates — new initiatives, direction changes, or priorities, (4) People News — new hires, departures, promotions, recognitions, (5) Q&A Highlights — the most interesting questions asked and answers given, (6) Action Items — anything attendees were asked to do, (7) Upcoming Dates — events, deadlines, or meetings mentioned. Format as a scannable email-ready summary with headers and bullets. Keep it under 500 words.
Summarise [BOOK/REPORT TITLE] into: (1) One-sentence overview, (2) 5-7 key takeaways, (3) The main argument or thesis, (4) Most surprising or contrarian finding, (5) How it applies to [MY ROLE/CONTEXT], (6) Who should read this and why, (7) 3 quotes worth remembering. Keep the full summary under 500 words.
Summarise competitive intel from [SOURCES]. For each competitor: strengths, vulnerabilities, recent moves, customer sentiment vs us, recommended response. One-page competitive summary.
Compare these two versions of [DOCUMENT]. Identify: (1) What was added, (2) What was removed, (3) What was changed, (4) Impact of changes, (5) Your recommendation on which version is better and why.
▸
Lecture Notes Enhancer
Transform rough lecture or class notes into well-structured study material
BeginnerEnhance these lecture notes into comprehensive study material. For each topic covered: (1) Clean up and organise the content with proper headings, (2) Fill in any gaps — add context and explanations for incomplete points, (3) Highlight Key Concepts — bold the terms and ideas most likely to appear in an exam, (4) Add Examples — provide one real-world example for each major concept, (5) Create Quick-Reference Definitions for any technical terms, (6) Generate Study Questions — 3 questions per topic to test understanding, (7) Link Related Topics — show how concepts connect to each other. Format with clear headers and bullet points for easy scanning.
▸
Long Document Deep Analysis
Upload a massive document and get a thorough, structured analysis leveraging Claude's 200K context
AdvancedAnalyse this entire document thoroughly. Provide: (1) Document Overview — type, purpose, author, date, length, (2) Executive Summary — the core message in 5 sentences, (3) Section-by-Section Analysis — key points from each major section, (4) Critical Assessment — strengths and weaknesses of the arguments/content, (5) Key Data Points — all important numbers, statistics, and figures extracted, (6) Inconsistencies — any contradictions or gaps in the document, (7) Implications — what this document means for [YOUR CONTEXT], (8) Questions Raised — issues the document raises but does not answer, (9) Recommended Actions — what should be done based on this content. Be thorough — I uploaded the full document for a reason.
▸
Long Document Summariser
Condense a long document, report, or article into a clear executive summary
BeginnerSummarise this document in three levels: (1) TL;DR — one sentence capturing the core message, (2) Executive Summary — a 3-4 sentence paragraph covering the key points, (3) Detailed Summary — bullet points covering every major section with the most important facts and figures preserved. Flag anything that seems like a decision point or requires action.
Summarise this long [EMAIL / CHAT / DOCUMENT] thread into: (1) What started the conversation, (2) Key positions or opinions expressed, (3) Where people agree, (4) Where people disagree, (5) Current status or resolution, (6) Action items still open. Keep it under 150 words. Write for someone who needs to join this conversation now.
Condense this meeting transcript into: (1) Meeting purpose and outcome, (2) Key points discussed (5-7 bullets), (3) Decisions made, (4) Action items with owners, (5) Unresolved items for next time. Under 300 words.
▸
Project Status from Teams Channels
Compile a project status update from scattered Teams conversations and shared files
IntermediateReview the recent conversations in the [PROJECT NAME] Teams channel from the past [TIME PERIOD]. Compile a project status update that includes: (1) Key decisions made, (2) Tasks completed, (3) Current blockers or issues raised, (4) Upcoming deadlines mentioned, (5) Who is working on what. Format as a concise status report suitable for sharing with leadership.
Extract key findings from this report. Provide: (1) The headline conclusion, (2) Top 5 findings ranked by importance, (3) Data that surprised you, (4) Implications for our team, (5) Recommended next steps.
▸
Teams Channel Thread Summary
Get a quick summary of what has been discussed in a busy Teams channel
BeginnerSummarise the recent conversations in this Teams channel from the past [TIME PERIOD]. Include: (1) Key topics discussed, (2) Decisions that were made, (3) Questions that remain unanswered, (4) Action items assigned to specific people, (5) Any links or files that were shared. Group by topic rather than chronologically. Highlight anything I should respond to.
▸
Weekly Inbox Digest
Get a prioritised summary of your week's emails with action items and follow-ups
BeginnerSummarise my emails from the past week. Group them into: (1) Urgent — needs response today, (2) Action Required — needs response this week, (3) FYI — informational only. For each email list the sender, subject, and one-line summary. Highlight any emails where I was directly asked a question or given a deadline.
▸
YouTube Video Summariser
Get a structured summary of any YouTube video without watching the full thing
BeginnerSummarise this YouTube video: [PASTE URL OR DESCRIBE VIDEO]. Provide: (1) Title and Creator, (2) TL;DR — the main point in one sentence, (3) Key Takeaways — 5-7 most important points as bullets, (4) Timestamps — approximate times for each major topic change, (5) Quotes — any notable statements worth remembering, (6) Action Items — things the viewer is encouraged to do, (7) Who Should Watch This — is it worth the full watch for my role/interests? Rate overall quality and relevance (1-10).
📊 Copilot in Excel
Set up a budget tracker with monthly columns for budget and actual, auto-calculated variance, conditional formatting, YTD totals, forecast, and dashboard summary.
▸
Build a Complex Formula
Describe what you need in plain English and get the right Excel formula
AdvancedCreate a formula that [DESCRIBE WHAT YOU NEED — e.g., calculates the priority score based on severity (High=3, Medium=2, Low=1) multiplied by the number of days open, then sorts into Critical/High/Medium/Low tiers]. Explain how the formula works step by step so I can modify it later.
▸
Create an Insightful Chart
Ask Copilot to build the right chart for your data and explain what it shows
IntermediateCreate a chart that best shows [WHAT YOU WANT TO VISUALISE — trends over time / comparison between categories / distribution of values] from this data. Choose the most appropriate chart type. Add clear labels, a title, and a legend. Then explain in one sentence what the chart tells us.
▸
Create an SLA Overdue Formula
Build a formula that flags rows where deadlines have passed and highlights them
BeginnerCreate a formula for this table that flags rows where the [DEADLINE COLUMN] has passed and the [STATUS COLUMN] is not "Completed". Show "Overdue" in a new column. Then add conditional formatting to highlight overdue rows in red and items due within 3 days in amber.
Design a one-page Excel dashboard for [PURPOSE — sales tracking / project status / IT operations / team performance]. Include: (1) 4-6 KPI cards with current value and trend, (2) Main chart showing the primary metric over time, (3) Breakdown chart by [DIMENSION — region / category / team], (4) Data table with detail, (5) Refresh date. Specify chart types and layout.
▸
Data Summary with Top Insights
Get Copilot to analyse your spreadsheet and surface the most important findings
BeginnerAnalyse this data and give me: (1) The top 5 key insights or trends, (2) Any notable outliers or anomalies, (3) A summary of totals and averages for the key metrics. Explain each insight in plain English — I need to present this to [AUDIENCE — management / the team].
▸
Data Validation Rules Designer
Set up data validation to prevent errors in shared spreadsheets
IntermediateDesign data validation rules for this shared spreadsheet with columns: [LIST COLUMNS]. For each column specify: (1) Allowed data type, (2) Validation rule (dropdown list, range, format), (3) Input message for users, (4) Error message if invalid, (5) Whether blank is allowed. Goal: prevent data quality issues before they happen.
Create an employee directory template with name, role, department, location, email, phone, manager, start date, skills. Add filters and headcount calculation.
▸
Find Data Quality Issues
Identify duplicates, blanks, inconsistencies, and formatting problems in your data
IntermediateScan this table for data quality issues. Look for: (1) Duplicate rows, (2) Blank or missing values in required columns, (3) Inconsistent formatting (dates, currencies, text case), (4) Values that look like typos or outliers. List each issue with the row number and a suggested fix.
▸
Monthly Trend Analysis
Analyse data for month-over-month trends, seasonal patterns, and growth rates
AdvancedAnalyse this data by month and show me: (1) Month-over-month change (percentage), (2) The best and worst performing months, (3) Any seasonal patterns you can detect, (4) The overall trend direction (growing, declining, or flat). Add a trend line chart and forecast the next 3 months based on the pattern.
▸
Pivot Table Design Helper
Design the right pivot table layout for your analysis question
IntermediateI need to answer this business question from my data: [QUESTION — e.g. Which region had the highest sales growth last quarter?]. My data has these columns: [LIST COLUMNS]. Design: (1) The pivot table layout (rows, columns, values, filters), (2) What aggregation to use (sum, count, average), (3) Any calculated fields needed, (4) Recommended chart to visualise the result.
▸
What-If Scenario Comparison
Build side-by-side scenario comparisons with different assumptions
AdvancedBuild a what-if scenario comparison for [DECISION — hiring plan / budget allocation / pricing change / expansion]. Create 3 scenarios: (1) Conservative, (2) Base case, (3) Optimistic. For each: define assumptions, calculate outcomes, and show the difference. Include a sensitivity analysis on the [KEY VARIABLE]. Present as a side-by-side comparison table.
✏️ Writing Prompts
▸
Blog Post Outline Generator
Generate a structured outline for a blog post on any topic with SEO-friendly headings
BeginnerCreate a detailed blog post outline about [TOPIC]. Include: (1) A compelling title with a keyword focus, (2) An engaging introduction hook, (3) 5-7 H2 subheadings that flow logically, (4) 2-3 bullet points under each heading showing what to cover, (5) A conclusion with a call-to-action. Target audience: [AUDIENCE]. Tone: informative but conversational.
Convert these bullet points into narrative text: [PASTE]. Requirements: (1) Smooth transitions, (2) Logical flow, (3) Maintain all information, (4) Add connecting context, (5) [TONE]. Target: [WORDS] words.
Write an announcement email about [NEWS] to all staff. Be clear, direct, and reassuring. Include what, why, when, impact, and next steps. Under 200 words.
▸
Company Policy Draft
Draft a professional company policy document from scratch or update an existing one
IntermediateDraft a company policy document for [POLICY TOPIC]. Include these sections: (1) Purpose — why this policy exists, (2) Scope — who it applies to, (3) Definitions — key terms explained, (4) Policy Statement — the actual rules and requirements, (5) Procedures — step-by-step process for compliance, (6) Responsibilities — who enforces and who follows, (7) Exceptions — how to request exceptions, (8) Review Schedule — when this policy will be reviewed. Use clear, unambiguous language. Tone: professional, formal, legally sound.
▸
Cover Letter Writer
Write a compelling, personalised cover letter tailored to a specific job posting
BeginnerWrite a cover letter for the [JOB TITLE] position at [COMPANY]. My background: [BRIEF SUMMARY OF EXPERIENCE]. The job posting emphasises: [KEY REQUIREMENTS FROM THE POSTING]. Structure: (1) Opening — a compelling hook that shows genuine interest in THIS company (not generic), (2) Value Match — 2-3 paragraphs connecting my specific experience to their key requirements with concrete examples, (3) Cultural Fit — one paragraph showing I understand their values and mission, (4) Closing — confident, forward-looking, with a specific call to action. Keep under 400 words. Tone: professional, authentic, enthusiastic without being desperate. Avoid clichés like "passionate about" or "team player".
▸
Customer Proposal Customiser
Customise a generic proposal template for a specific customer based on their needs
IntermediateCustomise this proposal for [CUSTOMER NAME] based on their specific needs: [KEY REQUIREMENTS]. Adapt the following: (1) Executive Summary — tailor to their industry and pain points, (2) Proposed Solution — emphasise features most relevant to their requirements, (3) Pricing — adjust the pricing table for their selected options, (4) Timeline — modify milestones to match their stated deadlines, (5) Case Studies — include examples from their industry, (6) Next Steps — personalise the call to action. Maintain our professional tone but make the customer feel this was written specifically for them.
▸
Daily Executive Digest
Compile a morning briefing digest for your executive with calendar, emails, and action items
IntermediatePrepare a morning briefing for [EXECUTIVE NAME] for today. Include: (1) Today's Calendar — all meetings with attendees, topics, and any prep needed, (2) Urgent Emails — messages requiring response today, summarised in one line each, (3) Pending Approvals — anything waiting for their sign-off, (4) Key Deadlines — what is due today or this week, (5) FYI Items — important updates that do not require action, (6) Suggested Time Blocks — when they have free time for deep work or responses. Format as a scannable briefing they can review in 2 minutes.
▸
Executive Briefing Document
Create a polished executive briefing from scattered notes, emails, and data points
IntermediateDraft an executive briefing document about [TOPIC] for [AUDIENCE]. Structure it as: (1) Executive Summary — 3 sentences max, (2) Background — what led to this situation, (3) Current State — where things stand today with key metrics, (4) Options & Recommendations — 2-3 options with pros/cons, (5) Recommended Action — one clear recommendation with reasoning, (6) Next Steps — specific actions with owners and timelines. Keep the total under 2 pages. Tone: authoritative, concise, fact-based.
Write an email to [EXECUTIVE — CEO / CFO / CTO / VP] about [TOPIC]. Requirements: (1) Subject line that immediately conveys the ask, (2) First sentence states the bottom line, (3) Context in 2-3 sentences maximum, (4) Clear ask or decision needed, (5) Options if applicable (recommend one), (6) Timeline. Total length: under 150 words. Executives skim — every word must earn its place.
▸
Job Description Writer
Create an inclusive, compelling job description that attracts the right candidates
BeginnerWrite a job description for [JOB TITLE] in our [DEPARTMENT]. Include: (1) About Us — 2-3 sentences about the company and team culture, (2) The Role — clear description of what this person will do day-to-day, (3) Key Responsibilities — 6-8 bullet points starting with action verbs, (4) Required Skills — must-have qualifications and experience, (5) Nice to Have — preferred but not required skills, (6) What We Offer — benefits, growth opportunities, work-life balance, (7) Salary Range — [RANGE] if applicable. Use inclusive language. Avoid jargon and unnecessary requirements that might discourage diverse candidates.
Write a LinkedIn article about [TOPIC] from my perspective as a [ROLE] with [YEARS] years of experience. Structure: (1) Hook headline (under 100 chars), (2) Opening story or observation that draws the reader in, (3) Main insight with 3 supporting points, (4) Practical advice the reader can use today, (5) Closing thought or question to drive comments. Target: 800-1200 words. Tone: authoritative but conversational.
▸
LinkedIn Post Generator
Create an engaging LinkedIn post from meeting notes, achievements, or company updates
BeginnerWrite a LinkedIn post about [TOPIC]. Structure it using this format: (1) Hook — an attention-grabbing first line (question, bold statement, or surprising fact), (2) Story/Context — 2-3 short paragraphs explaining the insight (use line breaks for readability), (3) Key Takeaways — 3-5 bullet points with emoji anchors, (4) Call to Action — ask a question or invite engagement. Keep it under 200 words. Tone: authentic, insightful, conversational — not corporate or salesy. Use short paragraphs and line breaks for mobile readability.
Draft a meeting request to [RECIPIENT] about [TOPIC]. Include: why this meeting matters, what we will cover, proposed duration and times, what to prepare. Make accepting easy.
▸
Networking Follow-Up Email
Write a memorable follow-up after meeting someone at an event or conference
BeginnerDraft a follow-up email to [PERSON] I met at [EVENT] on [DATE]. Reference our conversation about [TOPIC]. Include: personal connection point, one value-add (article, introduction, resource), and a low-pressure CTA (coffee chat, LinkedIn connect). Under 100 words. Tone: genuine, not transactional.
▸
Performance Review Helper
Draft balanced, constructive performance review comments with specific examples
IntermediateHelp me write a performance review for [EMPLOYEE NAME/ROLE]. Based on these notes: [PASTE NOTES]. For each performance area provide: (1) Rating context — what level of performance was demonstrated, (2) Specific Examples — cite concrete achievements or behaviours (not generalities), (3) Impact — how their work contributed to team/company goals, (4) Growth Areas — constructive feedback framed positively with specific improvement suggestions, (5) Development Goals — 2-3 SMART goals for the next period. Tone: supportive, honest, growth-oriented. Avoid generic phrases like "meets expectations" without context.
Write a press release announcing [NEWS/EVENT/LAUNCH]. Follow AP style: (1) Compelling headline, (2) City, date, and company intro, (3) Lead paragraph answering who, what, when, where, why, (4) Supporting quote from [SPOKESPERSON], (5) Details and context, (6) Company boilerplate, (7) Media contact information. Keep to one page.
Draft an apology email to [RECIPIENT] for [SITUATION]. Acknowledge the issue, take responsibility, explain what happened briefly, state corrective action, commit to improvement.
▸
Project Proposal Writer
Create a compelling project proposal with business case, timeline, and resource requirements
IntermediateWrite a project proposal for [PROJECT NAME]. Include: (1) Problem Statement — what issue this project solves, (2) Proposed Solution — high-level approach, (3) Business Case — expected ROI, cost savings, or strategic value, (4) Scope — what is included and explicitly excluded, (5) Timeline — major milestones over [DURATION], (6) Resource Requirements — team members, budget, tools needed, (7) Risks & Mitigation — top 3 risks with mitigation plans, (8) Success Metrics — how we will measure success. Tone: persuasive yet realistic.
Write a project update for [PROJECT]. Include: current status (RAG), accomplishments this period, upcoming milestones, risks, and decisions needed. One page maximum.
Write a recommendation letter for [PERSON] applying for [ROLE/PROGRAMME]. Include: relationship context, specific strengths with examples, notable achievements, enthusiastic endorsement.
Rewrite this technical content for a non-technical audience: [PASTE CONTENT]. Rules: (1) Replace every acronym with a plain English equivalent (or define on first use), (2) Use analogies for complex concepts, (3) Break long sentences into two shorter ones, (4) Remove unnecessary qualifications and caveats, (5) Add examples for abstract ideas. Target: understandable by someone with no background in this field.
Rewrite this text with a [TARGET TONE — formal / casual / empathetic / urgent] tone: [PASTE TEXT]. Keep the exact same message but change the voice. Show before and after.
▸
Travel Itinerary Organiser
Compile scattered travel bookings into a clean, chronological itinerary document
BeginnerCreate a detailed travel itinerary from these booking confirmations. Organise chronologically and include: (1) Date/Time — local time at each location, (2) Flights — airline, flight number, departure/arrival times, terminal, seat, confirmation number, (3) Hotels — name, address, check-in/out times, confirmation number, (4) Ground Transport — car rental, transfers, taxi contacts, (5) Meetings/Events — what is scheduled and where, (6) Key Contacts — names and phone numbers for each leg, (7) Notes — time zone changes, visa requirements, weather forecast. Format as a day-by-day schedule.
▸
Weekly Status Report Generator
Transform scattered notes into a polished weekly status report for leadership
BeginnerCreate a professional weekly status report from these notes. Structure it as: (1) Highlights — top 3 accomplishments this week, (2) In Progress — what's currently being worked on with percentage completion, (3) Blockers — any issues or dependencies holding things up, (4) Next Week — planned priorities and goals, (5) Metrics — any relevant KPIs or numbers. Keep each bullet to one line. Tone: confident, clear, suitable for VP-level audience.
📽️ Copilot in PowerPoint
▸
Add Speaker Notes to Every Slide
Generate natural, presentation-ready speaker notes for each slide
IntermediateAdd speaker notes to each slide in this presentation. The notes should sound natural — like I am explaining each slide to the audience in conversation, not reading bullet points. Include transition phrases between slides. Keep each slide note to 3-5 sentences.
Create a [NUMBER — 6 / 8 / 10]-slide presentation from this document for [AUDIENCE — leadership / client / team]. Each slide should have a clear title, 3-4 bullet points maximum, and a suggestion for a supporting visual. Include an agenda slide and a summary/next-steps slide at the end.
Transform this data into a compelling presentation story: [DESCRIBE DATA/FINDINGS]. Create a [NUMBER]-slide deck that: (1) Opens with the headline finding, (2) Shows the data visually with the right chart types, (3) Explains what the data means in plain English, (4) Highlights surprises or counterintuitive findings, (5) Ends with clear recommendations. Each slide should make one point.
Create a [NUMBER]-slide monthly update for [TEAM/DEPARTMENT]. Include: (1) Headline achievement this month, (2) Key metrics dashboard, (3) Wins and highlights, (4) Challenges and how we handled them, (5) Team shoutouts, (6) Next month priorities, (7) Resources or support needed. Each slide: one message, visual over text.
Create a [NUMBER]-slide onboarding deck for new hires joining [TEAM/COMPANY]. Include: (1) Welcome and company mission, (2) Team structure and who is who, (3) What we do and why it matters, (4) Tools and systems overview, (5) Key processes and how we work, (6) Culture and values, (7) First week expectations, (8) Resources and contacts, (9) Q&A. Tone: welcoming, not overwhelming.
▸
Presentation Outline from Topic
Generate a slide outline with titles and talking points from just a topic
BeginnerCreate a slide outline for a [DURATION — 10 / 20 / 30]-minute presentation about [TOPIC] for [AUDIENCE]. For each slide provide: a clear title, 3 key talking points, and a suggested visual or diagram. Include an opening hook slide and a closing call-to-action slide.
Create a [NUMBER]-slide problem-solution deck for [TOPIC]. Structure: (1) Hook with the problem statement, (2) Scale of the problem with data, (3) Why current approaches fail, (4) Our proposed solution, (5) How it works (3 steps max), (6) Evidence and proof points, (7) Investment required, (8) Expected outcomes, (9) Next steps and CTA.
▸
Redesign Deck for Executive Audience
Transform a detailed deck into an executive-ready version with less text and stronger impact
AdvancedRedesign this presentation for an executive audience. Reduce text on each slide to headlines and key numbers only. Replace detailed explanations with high-impact statements. Add an executive summary slide at the front. Keep data charts but simplify labels. Remove any slides that do not directly support a decision.
Create a sales enablement deck for [PRODUCT/SERVICE]. Include: (1) Elevator pitch (30 seconds), (2) Target customer profile, (3) Key pain points we solve (with customer quotes), (4) Product overview (features mapped to benefits), (5) Competitive positioning (us vs alternatives), (6) Pricing and packaging, (7) Objection handling, (8) Case studies, (9) Next step CTA.
▸
Shorten This Deck
Condense a long presentation into fewer slides without losing the message
IntermediateShorten this [CURRENT NUMBER]-slide deck to [TARGET NUMBER] slides. Keep the key message, main data points, and call to action. Merge related slides, remove redundant content, and cut filler slides. The shortened version should still tell a complete story.
Create a presentation for [STAKEHOLDERS] about [TOPIC]. Structure: bottom line upfront, context, evidence, options with recommendation, risks, ask, timeline.
▸
Suggest Better Visual Layouts
Get Copilot to recommend improved layouts and visuals for each slide
AdvancedReview each slide in this presentation and suggest a better visual layout. For text-heavy slides, suggest diagrams, icons, or charts that could replace the text. For data slides, suggest the best chart type. Explain why each suggestion would improve audience comprehension.
Create a [NUMBER]-slide training deck on [TOPIC] for [AUDIENCE]. Include: (1) Learning objectives slide, (2) Content slides with visuals over text, (3) Discussion question slides between sections, (4) Hands-on exercise slides with instructions, (5) Quiz or knowledge check slides, (6) Summary and resources slide. Add speaker notes with facilitator guidance.
Create a weekly status template. Slides: week summary with RAG, accomplishments, in progress, risks and blockers, next week plan, help needed. Consistent layout.
📊 Data Analysis Prompts
▸
Budget Variance Analysis
Analyse actual vs budgeted figures and highlight significant variances with explanations
IntermediateAnalyse this budget data comparing actual spend versus budgeted amounts. For each line item: (1) Calculate the variance (actual minus budget) and variance percentage, (2) Flag any variances greater than 10% as significant, (3) Categorise variances as Favourable or Unfavourable, (4) Suggest possible reasons for the top 5 largest variances, (5) Provide a summary with total budget utilisation percentage. Format as a table with colour-coded indicators.
Analyse for correlations between [VARIABLES]. For each significant one: (1) State the relationship, (2) Strength, (3) Direction, (4) Possible explanations, (5) Caveats. Create a correlation matrix.
Define metrics for a [PURPOSE] dashboard. For each metric: name, definition, data source, calculation, target, frequency, owner, and why it matters. Limit to 8-10 KPIs.
Create a data cleaning plan for [DATASET]. Check for: duplicates, missing values, inconsistent formats, outliers, invalid entries, and typos. Prioritise fixes by impact on analysis.
▸
Data Cleanup Instructions
Get step-by-step instructions to clean messy spreadsheet data into analysis-ready format
IntermediateHelp me clean up this messy spreadsheet data. The issues I am seeing: [DESCRIBE PROBLEMS — duplicates, inconsistent formatting, missing values, merged cells, etc.]. Provide a step-by-step cleanup plan: (1) Remove Duplicates — how to identify and remove them, (2) Standardise Formats — fix date formats, number formats, text capitalisation, (3) Handle Missing Data — strategy for blank cells (fill, flag, or remove), (4) Split/Merge Columns — separate combined data into proper columns, (5) Validate Data — formulas to check for errors and outliers, (6) Final Structure — what the clean dataset should look like. Provide the exact Excel steps or formulas for each action.
▸
Employee Headcount Analysis
Analyse workforce data to identify trends in hiring, attrition, and team composition
IntermediateAnalyse this employee headcount data and provide: (1) Total headcount by department and location, (2) Hiring trends — new joiners per month over the past year, (3) Attrition analysis — leavers by department, tenure, and reason if available, (4) Diversity breakdown — gender, age bands, and tenure distribution, (5) Cost analysis — average salary by department and level, (6) Recommendations — flag departments with high attrition or understaffing risks. Present as a combination of tables and key insight bullets.
▸
Excel Data Trend Finder
Analyse spreadsheet data and identify the top trends, patterns, and anomalies
IntermediateAnalyse this data and identify: (1) The top 3 trends over the time period shown, (2) Any anomalies or outliers that stand out, (3) A comparison between the highest and lowest performing categories, (4) A brief recommendation based on the patterns. Present your findings with specific numbers and percentages. Use a clear, executive-summary style.
▸
Excel Formula Helper
Get the right Excel formula explained step by step for any calculation you need
BeginnerI need an Excel formula to [DESCRIBE WHAT YOU WANT TO CALCULATE]. My data is structured as: [DESCRIBE YOUR COLUMNS/LAYOUT]. Please provide: (1) The exact formula I should use, (2) A step-by-step explanation of how the formula works, (3) Where to place it in my spreadsheet, (4) Any helper columns needed, (5) Common errors to watch for, (6) An alternative formula approach if there is one. If the task is complex, break it into multiple simpler formulas rather than one giant nested formula.
▸
Expense Report Analyser
Analyse expense data to find patterns, flag anomalies, and identify cost-saving opportunities
IntermediateAnalyse this expense data and provide: (1) Total Spend Summary — by category, department, and time period, (2) Top Spenders — individuals or departments with highest expenses, (3) Trend Analysis — month-over-month spending patterns, (4) Anomaly Detection — flag any expenses that seem unusual (unusually high amounts, weekend expenses, duplicate claims), (5) Policy Compliance — identify expenses that may violate common corporate policies (excessive meals, unapproved travel class), (6) Cost-Saving Opportunities — 3-5 specific recommendations to reduce spending, (7) Benchmarks — compare against typical corporate spending ratios. Format as a clear report with tables.
▸
KPI Dashboard Data Prep
Transform raw data into KPI summaries with trends, targets, and RAG status indicators
IntermediateUsing this data, create a KPI dashboard summary. For each metric: (1) Current value, (2) Target value, (3) Variance from target as a percentage, (4) RAG status (Red if >10% below target, Amber if 5-10% below, Green if on or above target), (5) Trend direction compared to last period (↑ improving, → stable, ↓ declining). Present as a clean table. Then provide a narrative summary of the top 3 areas needing attention and top 3 areas performing well.
Analyse this data using a pivot approach. Group by [DIMENSION], measure [METRIC]. Show: totals, averages, percentages, and identify the top and bottom performers. Add a chart.
▸
Sales Pipeline Analysis
Analyse your sales pipeline data to identify top opportunities, risks, and forecast accuracy
AdvancedAnalyse this sales pipeline data and provide: (1) Total pipeline value by stage (Prospect, Qualified, Proposal, Negotiation, Closed Won/Lost), (2) Win rate by stage and by sales rep, (3) Average deal cycle time from first contact to close, (4) At-risk deals — opportunities that have been in the same stage for more than [X] days, (5) Revenue forecast for the next quarter based on current pipeline and historical win rates, (6) Top 5 recommendations to improve pipeline conversion.
Analyse these survey results. Provide: (1) Response rate and validity, (2) Key quantitative findings, (3) Open-ended theme analysis, (4) Segments that differ significantly, (5) Top 3 actionable insights, (6) Follow-up recommendations.
▸
What-If Scenario Analysis
Build a scenario analysis comparing optimistic, realistic, and pessimistic projections
AdvancedCreate a what-if scenario analysis for [DECISION/PROJECTION]. Build three scenarios: (1) Optimistic — best case with favourable assumptions, (2) Realistic — most likely case based on current trends, (3) Pessimistic — worst case with unfavourable assumptions. For each scenario provide: variable assumptions used, projected outcome (revenue, cost, timeline, or metric), probability estimate, key risks, and recommended actions. Create a comparison table and identify the break-even point or decision threshold. Conclude with a recommendation on which scenario to plan for.
📓 Copilot in OneNote
Set up a client meeting notes template in OneNote. Sections: (1) Client details and attendees, (2) Agenda items, (3) Discussion notes by agenda item, (4) Commitments we made, (5) Commitments they made, (6) Follow-up actions with owners and dates, (7) Next meeting date. Include a satisfaction indicator.
Create a one-page summary of these notes. Include only: the key decisions made, the most important takeaways, and the next steps with owners. Remove all discussion details — this summary should tell someone what happened in 30 seconds.
Based on these notes, draft an agenda for our next meeting. Include: (1) Overdue action items to review, (2) Open questions that still need answers, (3) New topics flagged for discussion, (4) Time estimate for each item. Suggest a total meeting duration.
▸
Extract Risks and Open Questions
Pull out all risks, concerns, and unanswered questions from your notes
IntermediateReview these notes and extract: (1) Risks or concerns mentioned by anyone, (2) Questions that were raised but not answered, (3) Assumptions that need to be validated, (4) Dependencies on other teams or decisions. Rate each risk as High/Medium/Low impact.
Create an interview notes template. Include: candidate details, questions with answer space, competency scoring 1-5, cultural fit indicators, red flags, recommendation.
Set up a learning journal in OneNote. Structure: (1) Weekly learning entries (date, what I learned, source, how I will apply it), (2) Book and article notes section, (3) Course notes with key takeaways, (4) Skills tracking (skill, level, target, progress), (5) Questions to explore, (6) Monthly reflection on growth.
▸
Notes to Action Item List
Turn messy meeting notes into a structured list of action items with owners
BeginnerConvert these meeting notes into a structured action item list. For each item include: the task, who is responsible, the deadline (if mentioned), and the priority (High/Medium/Low based on context). Present as a table sorted by priority.
Organise these notes into clear sections with headings. Suggested structure: (1) Key Decisions, (2) Action Items, (3) Discussion Points, (4) Open Questions, (5) Reference Links or Documents Mentioned. Move each piece of content to the right section.
Set up a decision log in OneNote for [PROJECT]. For each decision: date, decision statement, context (why now), options considered, chosen option, rationale, who decided, review date. Include a search-friendly index at the top.
▸
Research Collection Notebook
Organise research from multiple sources into a structured notebook
IntermediateSet up a research notebook in OneNote for [TOPIC]. Sections: (1) Research questions to answer, (2) Source notes (one page per source with citation, key points, credibility rating), (3) Synthesis page (themes across sources), (4) Gaps and questions, (5) Conclusions and recommendations.
Set up a strategy notes template: session objective, current state, vision discussed, options explored, pros and cons, decisions, open questions, action items.
▸
Weekly Status from Notebook Pages
Compile notes from multiple pages into a weekly status summary
IntermediateSummarise the notes from this week into a weekly status update. Include: (1) What was accomplished this week, (2) What is in progress, (3) Blockers or risks, (4) Plans for next week. Keep it concise — this is for my [AUDIENCE — manager / team / stakeholders].
📑 Presentation Prompts
▸
Change Management Presentation
Create a presentation to announce and guide teams through an organisational change
IntermediateCreate a change management presentation about [CHANGE/INITIATIVE]. Structure as: (1) Why Change — the business case and urgency, (2) What Is Changing — specific changes in clear, simple terms, (3) What Is NOT Changing — reassure on stability areas, (4) Timeline — phased approach with key dates, (5) Impact by Team — how different groups are affected, (6) Support Available — training, resources, help channels, (7) FAQ — top 5 anticipated concerns with honest answers, (8) Your Role — what the audience needs to do, (9) Feedback Channel — how to raise questions or concerns, (10) Vision — paint the positive future state. Tone: empathetic, transparent, confident.
▸
Client Pitch Deck
Build a persuasive client pitch presentation tailored to their industry and pain points
IntermediateCreate a client pitch presentation for [CLIENT NAME] in the [INDUSTRY] industry. Include: (1) Their Challenge — show you understand their pain points, (2) Our Solution — how we solve it specifically for them, (3) Key Differentiators — why us vs competitors, (4) Case Study — similar client success story with metrics, (5) Implementation Approach — high-level timeline, (6) Investment & ROI — pricing context with expected returns, (7) Team — who they will work with, (8) Next Steps — clear call to action. Tone: consultative, confident, tailored.
▸
Company Introduction Deck
Create a professional company overview presentation for prospects, partners, or new employees
BeginnerCreate a company introduction presentation for [AUDIENCE TYPE]. Include: (1) Who We Are — company mission, vision, and values in one impactful slide, (2) By the Numbers — key stats (revenue, employees, customers, years in business), (3) What We Do — products/services overview with clear value propositions, (4) Our Differentiators — what makes us unique vs competitors, (5) Client Success Stories — 2-3 brief case studies with metrics, (6) Our Team — leadership team highlights, (7) Awards & Recognition — credibility builders, (8) Next Steps — clear CTA for the audience. Keep to 12 slides max. Design notes: suggest colour scheme, imagery style, and layout for each slide.
▸
Data Storytelling Presentation
Transform raw data and charts into a compelling narrative presentation
AdvancedCreate a data storytelling presentation from this data. Structure as: (1) The Hook — start with a surprising finding or trend, (2) The Context — why this data matters and what we were measuring, (3) The Journey — walk through the data chronologically or by theme, building toward the insight, (4) The Insight — the key "aha moment" the data reveals, (5) The Implications — what this means for our business, (6) The Action — specific recommendations backed by the data, (7) The Ask — what you need from the audience. For each slide, suggest a chart type or visual that best tells that part of the story. Avoid data dumps — every number should serve the narrative.
▸
Document to Presentation Outline
Turn a long document or report into a concise slide deck outline
BeginnerConvert this document into a presentation outline with 10-12 slides. For each slide provide: (1) Slide title, (2) 3-4 key bullet points, (3) Suggested visual — chart, image, or diagram that would support the point. Start with an executive summary slide and end with key takeaways and next steps. Keep language concise — no full sentences on slides.
Create a [NUMBER]-slide executive deck for [DECISION]. Structure: bottom line, context, options, recommendation, risk, investment, timeline. Each slide answers one question. Minimal text.
▸
New Employee Onboarding Deck
Create a welcoming and informative onboarding presentation for new team members
BeginnerCreate a new employee onboarding presentation for the [DEPARTMENT] team. Include: (1) Welcome & Team Culture — who we are and how we work, (2) Team Structure — org chart and key contacts, (3) Tools & Systems — what software and platforms we use daily, (4) Key Processes — how we handle [COMMON WORKFLOWS], (5) Communication Norms — meeting cadence, chat etiquette, response time expectations, (6) First 30-60-90 Day Expectations, (7) FAQ — common new starter questions, (8) Resources & Links — where to find everything. Tone: welcoming, clear, friendly.
▸
Quarterly Business Review Deck
Create a QBR presentation with financials, achievements, challenges, and next quarter goals
IntermediateCreate a Quarterly Business Review presentation with these slides: (1) Title slide with quarter and date, (2) Executive Summary — 3 key takeaways, (3) Financial Performance — revenue, costs, margin vs target, (4) Key Achievements — top 5 wins this quarter, (5) Challenges & Lessons Learned, (6) Customer/Client Highlights, (7) Team & Resource Update, (8) KPI Scorecard with RAG status, (9) Next Quarter Priorities and Goals, (10) Appendix with detailed data. Keep each slide to 4-5 bullet points max. Tone: professional, data-driven.
Create a [NUMBER]-slide QBR deck for [DEPARTMENT]. Include: overview and metrics, highlights, challenges, financial performance, customer insights, learnings, next priorities, support needed. Headline insight on each slide.
▸
Speaker Notes Generator
Generate detailed speaker notes for each slide so you can present confidently without memorising
IntermediateWrite detailed speaker notes for each slide in this presentation. For each slide provide: (1) Opening line — how to introduce the slide naturally, (2) Key talking points — 3-4 sentences expanding on the bullet points with examples and data, (3) Transition — one sentence connecting to the next slide, (4) Timing — suggested time to spend on this slide. Total presentation should be [DURATION] minutes. Tone: conversational, confident, as if speaking to [AUDIENCE]. Include one anecdote or real-world example per 3 slides.
Create a [NUMBER]-slide deck introducing [TEAM] to [AUDIENCE]. Include: team mission, key people and roles, what we deliver, how we work, current priorities, how to engage with us.
Create a [NUMBER]-slide workshop deck for [TOPIC]. Include: welcome/objectives, 3-4 content sections, interactive exercises between sections, discussion questions, summary/takeaways, resources. Add facilitator notes.
🔄 Copilot in Loop
▸
Convert Comments to Action Items
Pull action items from Loop comments and assign owners
IntermediateReview the comments on this Loop page and extract all action items, requests, and follow-ups. For each item list: what needs to be done, who requested it, and who should own it. Present as a checklist the team can work through.
▸
Create a Shared Project Tracker
Set up a project tracker that the whole team can update in real time
BeginnerCreate a project tracker table from these tasks. Columns: Task Name, Owner, Due Date, Status (Not Started / In Progress / Done / Blocked), Dependencies, Notes. Add all tasks mentioned, assign owners where specified, and set realistic due dates based on the project timeline of [DURATION].
▸
Draft a Decision Log
Convert a discussion thread into a formal decision log with rationale
IntermediateTurn this discussion into a decision log. For each decision include: the decision made, the alternatives considered, the rationale for choosing this option, who made the decision, and the date. Format as a table that the team can reference later.
▸
Editable Team Status Update
Create a status update template the whole team can keep current
AdvancedCreate a team status update template with sections for each workstream: [LIST WORKSTREAMS]. Each section should have: Owner, Status (On Track / At Risk / Blocked), Key Updates (2-3 bullets), and Next Week Plans. Make it easy for each team member to fill in their section.
Create a risk tracker in Loop. Columns: Risk ID, Description, Category, Likelihood, Impact, Score, Mitigation, Owner, Status, Last Reviewed. Auto-sort by score.
Create a retrospective board for [PROJECT]. Sections: (1) What went well — team adds items live, (2) What to improve, (3) What puzzled us, (4) Vote on top items (each person picks 3), (5) Action items from top-voted (owner, deadline, success measure). Claude or Copilot: group themes as items come in.
Create a stakeholder communication hub in Loop for [PROJECT]. Include: (1) Stakeholder register (name, role, interest, influence), (2) Communication log (date, channel, message, response), (3) Upcoming communications calendar, (4) Approved messaging and talking points, (5) Feedback tracker.
▸
Summary for Late Joiners
Create a quick catch-up summary for people joining a Loop workspace late
IntermediateWrite a brief catch-up summary of this Loop page for someone joining this project now. Cover: (1) What this project is about, (2) What has been decided so far, (3) What is currently in progress, (4) What they need to know or do first. Keep it under 150 words.
Create a goals board for [QUARTER]. For each goal: statement, key results, progress, owner, status. Include celebration section for completions.
Create a team wiki in Loop for [TEAM]. Sections: (1) Team mission and goals, (2) Who does what (roles and responsibilities), (3) How we work (processes, tools, ceremonies), (4) Key resources and links, (5) FAQ for new joiners, (6) Glossary of team-specific terms. Everyone on the team can edit and keep current.
▸
Turn Brainstorm into Action Table
Convert a free-form brainstorm into a structured table with owners and next steps
BeginnerTurn this brainstorm into a table with columns: Idea, Owner, Priority (High/Medium/Low), Next Step, and Status. Group related ideas together. Remove duplicates. Put the highest-impact ideas first.
Create a weekly standup board. Columns per team member: What I did this week, What I am doing next week, Blockers. Include: team health check (1-5 mood rating), wins to celebrate section, and a help-needed board. Refresh weekly but keep history.
📋 Project Management Prompts
Create a lessons learned document for [PROJECT]. Structure: (1) Project overview (scope, timeline, outcome), (2) What went well (5-7 items with impact), (3) What could improve (5-7 items with root cause), (4) What we would do differently, (5) Recommendations for future projects, (6) Key metrics vs plan. Get input from: [TEAM MEMBERS]. Tone: constructive and forward-looking.
▸
Project Notebook Template
Create a structured project notebook with standardised sections for consistent tracking
BeginnerCreate a project notebook template for [PROJECT NAME] with these sections: (1) Project Charter — objective, scope, stakeholders, success criteria, (2) Meeting Notes — template for recurring meeting minutes, (3) Decision Log — table with Date, Decision, Rationale, Owner, (4) Action Item Tracker — Task, Owner, Due Date, Status, (5) Risk & Issue Log — structured risk register, (6) Key Contacts — stakeholder directory with roles and contact details, (7) Reference Documents — links to important files and resources, (8) Lessons Learned — ongoing capture of what went well and what to improve, (9) Status Dashboard — weekly RAG indicators template. Each section should have a brief description of what goes there.
▸
Project Plan from Brief
Turn a high-level project brief into a detailed project plan with phases, milestones, and owners
IntermediateCreate a detailed project plan from this brief. Include: (1) Project Overview — objective, scope, success criteria, (2) Phases — break the project into 3-5 logical phases, (3) Tasks — list tasks within each phase with estimated duration, (4) Milestones — key checkpoints with dates, (5) Dependencies — which tasks depend on others, (6) Resource Requirements — roles needed for each phase, (7) Risk Register — top 5 risks with likelihood, impact, and mitigation, (8) Communication Plan — who gets updated, how often, through what channel. Present as a structured document with tables.
Write a project scope document for [PROJECT]. Include: (1) Project objectives and success criteria, (2) In-scope deliverables (be specific), (3) Out-of-scope items (explicitly stated), (4) Assumptions, (5) Constraints, (6) Dependencies on other teams, (7) Acceptance criteria, (8) Change control process. This document prevents scope creep — be precise.
Design a project status dashboard for [PROJECT/PORTFOLIO]. Include: (1) Overall status indicator (RAG), (2) Timeline progress with milestone markers, (3) Budget tracker (planned vs actual), (4) Risk summary with top 3 risks, (5) Key metrics and KPIs, (6) Recent accomplishments, (7) Upcoming milestones (next 2 weeks), (8) Decisions needed. One-page format for weekly reporting.
Write a resource request for [PROJECT] requesting [WHAT — additional headcount / budget / tools / time]. Include: (1) Current resource allocation, (2) Gap analysis showing what cannot be delivered without the resource, (3) Impact of not getting the resource (delays, quality, risk), (4) Options (full request, partial, alternative), (5) ROI or payback, (6) Timeline needed. Present for [APPROVER — PMO / director / finance].
▸
Retrospective Facilitator
Run a structured team retrospective to identify what went well, what did not, and improvement actions
BeginnerCreate a retrospective document for [PROJECT/SPRINT/QUARTER]. Structure it using the Start-Stop-Continue framework: (1) START — things we should begin doing (new practices, tools, habits), (2) STOP — things we should stop doing (wasteful activities, bad habits), (3) CONTINUE — things that are working well and should keep going. For each section, provide 5 thought-provoking questions the facilitator should ask. Then include: (4) Top 3 Action Items — specific improvements with owners and deadlines, (5) Celebration — highlight one team achievement to recognise.
▸
Risk Register Creator
Identify and document project risks with impact assessment and mitigation strategies
IntermediateCreate a comprehensive risk register for [PROJECT/INITIATIVE]. For each risk provide: (1) Risk ID, (2) Risk Description — clear statement of what could go wrong, (3) Category — Technical, Resource, Schedule, Budget, External, (4) Likelihood — High/Medium/Low, (5) Impact — High/Medium/Low, (6) Risk Score — Likelihood × Impact, (7) Mitigation Strategy — specific actions to reduce the risk, (8) Contingency Plan — what to do if the risk materialises, (9) Owner — who monitors this risk. Identify at least 10 risks. Format as a table sorted by risk score (highest first).
Create a stakeholder map for [PROJECT]. For each stakeholder: (1) Name and role, (2) Interest level (High/Medium/Low), (3) Influence level (High/Medium/Low), (4) Current attitude (Supportive/Neutral/Resistant), (5) Engagement strategy, (6) Communication frequency. Categorise into quadrant: Manage Closely, Keep Satisfied, Keep Informed, Monitor.
▸
Stakeholder Update Email
Create a professional stakeholder update with RAG status, progress, and next steps
BeginnerDraft a stakeholder update for [PROJECT NAME] covering [TIME PERIOD]. Include: (1) RAG Status — Red, Amber, or Green with clear justification, (2) Executive Summary — 2-3 sentences on overall progress, (3) Key Accomplishments — what was delivered this period, (4) Upcoming Milestones — what is due next with dates, (5) Risks & Issues — any current blockers with mitigation actions, (6) Budget Status — on track / variance, (7) Decisions Needed — anything requiring stakeholder input, (8) Next Steps — priorities for the coming period. Keep it to one page. Tone: confident, transparent, concise.
🔬 Research Prompts
Research best practices for [TOPIC/AREA] in [INDUSTRY/CONTEXT]. Provide: (1) Top 5 proven best practices with evidence, (2) Which leading companies follow each practice, (3) Common mistakes to avoid, (4) Implementation difficulty for each, (5) Where to start (recommended sequence). Base on reputable sources and cite them.
▸
Contract Review Checklist
Systematically review a contract and flag potential issues, missing clauses, and risks
AdvancedReview this contract and create a checklist assessment. For each section evaluate: (1) Clarity — is the language clear and unambiguous? (2) Completeness — are any standard clauses missing? (3) Risk — flag any terms that are unfavourable or unusual, (4) Compliance — does it align with standard business practices? Check specifically for: termination clauses, liability limitations, indemnification, confidentiality, intellectual property ownership, payment terms, dispute resolution, and force majeure. Rate each area as ✅ Acceptable, ⚠️ Needs Review, or ❌ Concerning.
▸
Fact-Check a Claim
Verify whether a statement, statistic, or claim is accurate with cited sources
BeginnerFact-check this claim: "[PASTE CLAIM OR STATEMENT]". Provide: (1) Verdict — True, Partially True, Misleading, or False, (2) Evidence For — sources and data supporting the claim, (3) Evidence Against — sources and data contradicting the claim, (4) Context Missing — important nuance the claim leaves out, (5) Original Source — where this claim likely originated, (6) Current Status — is this still accurate as of today or has it been updated/corrected? Cite specific, credible sources for every point. Prioritise official data, peer-reviewed research, and reputable news outlets.
▸
Find and Summarise Company Policy
Quickly find and summarise any internal company policy or procedure document
BeginnerFind our company policy on [TOPIC] from SharePoint or shared documents. Summarise the key points in plain language, including: (1) What the policy requires, (2) Who it applies to, (3) Any exceptions or special cases, (4) Who to contact for questions, (5) When it was last updated. If multiple versions exist, use the most recent one.
▸
Industry Trend Analysis
Get a comprehensive analysis of current trends, disruptions, and opportunities in any industry
IntermediateProvide a comprehensive analysis of the current state of the [INDUSTRY] industry. Include: (1) Top 5 Trends — what is changing and why it matters, (2) Key Disruptions — technologies or business models disrupting the status quo, (3) Competitive Landscape — major players and their strategies, (4) Opportunities — where growth potential exists for new entrants or innovators, (5) Threats — regulatory, economic, or technological risks, (6) 12-Month Outlook — what to expect in the near future. Cite specific companies, products, or data points where possible.
Research current trends in [INDUSTRY]. Cover: top 5 trends, driving forces behind each, early adopters, implications for our business, and recommended actions for the next 12 months.
▸
Learn Any Topic Fast
Get a structured crash course on any topic, from beginner to competent in 10 minutes
BeginnerGive me a comprehensive crash course on [TOPIC]. Structure it as: (1) ELI5 — explain it in one simple analogy a 10-year-old would understand, (2) Core Concepts — the 5-7 key ideas I must understand, each in 2-3 sentences, (3) How It Actually Works — a more technical explanation with a step-by-step process, (4) Common Misconceptions — 3 things people get wrong about this topic, (5) Real-World Examples — 3 concrete examples of this in action, (6) Key Terminology — a mini-glossary of 8-10 essential terms, (7) What to Learn Next — recommended path to go deeper. Write in clear, simple English. Avoid jargon unless you define it first.
▸
Literature Review Summary
Summarise research from multiple sources into a structured review
AdvancedConduct a literature review on [TOPIC] using [NUMBER — 5 / 10] sources. For each source: (1) Citation, (2) Key findings, (3) Methodology, (4) Relevance to our question. Then synthesise: (1) What the consensus is, (2) Where experts disagree, (3) Gaps in current research, (4) Implications for our work. Present as an academic-style summary.
Research the market for [INDUSTRY/PRODUCT/SEGMENT]. Cover: (1) Market size and growth rate, (2) Key players and market share, (3) Customer segments, (4) Industry trends (3-5), (5) Regulatory considerations, (6) Barriers to entry, (7) Opportunities for new entrants. Cite sources and note confidence levels. Present as an executive brief.
▸
Source-Grounded Q&A Session
Upload documents to NotebookLM and get answers strictly based on your sources — no hallucination
BeginnerBased ONLY on the documents I have uploaded as sources, answer these questions: (1) [QUESTION 1], (2) [QUESTION 2], (3) [QUESTION 3]. For each answer: cite the specific source document and section where you found the information. If the answer is not in my sources, say "Not found in uploaded sources" rather than making something up. After answering, suggest 5 additional questions I should ask about these documents that I might not have thought of.
▸
Technology Comparison Brief
Compare two or more technologies, tools, or platforms with a structured analysis
BeginnerCreate a detailed comparison between [TECH A] and [TECH B]. Include: (1) Overview — one paragraph for each, (2) Feature comparison table with categories like pricing, ease of use, scalability, integrations, learning curve, (3) Best for — which use cases each excels at, (4) Limitations of each, (5) My recommendation with reasoning. Be objective and cite specific features, not marketing claims.
🔬 Researcher Agent
▸
Build a Decision Brief
Create a structured decision document with options, trade-offs, and a recommendation
AdvancedBuild a decision brief for [DECISION TOPIC]. Include: (1) Context and why this decision matters now, (2) Options considered (at least 3), (3) Pros and cons of each option with evidence, (4) Risks and mitigation strategies, (5) Your recommended option and reasoning, (6) Next steps if we proceed. Format for executive review.
Create a competitor watch brief for [COMPETITOR] covering the last [PERIOD]. Track: (1) Product announcements, (2) Pricing changes, (3) New partnerships, (4) Executive hires, (5) Customer wins or losses, (6) Analyst commentary, (7) What this means for us. Cite every finding.
Research emerging trends in [DOMAIN] for [YEAR]. Identify: (1) Top 5 trends with evidence, (2) Which are hype vs real adoption, (3) Key players driving each trend, (4) Timeline to mainstream, (5) Implications for [OUR CONTEXT], (6) Recommended actions. Distinguish predictions from confirmed developments.
▸
Explain a Topic in Plain English
Get a clear, jargon-free explanation of a complex topic with current state
BeginnerExplain [TOPIC] in plain English. Cover: (1) What it is and why it matters, (2) How it works at a high level, (3) The current state — what is available now vs. coming soon, (4) Common misconceptions, (5) How it affects [ROLE — IT admins / end users / security teams]. Write for someone who is smart but not an expert in this area.
▸
Policy Impact Analysis
Research how a new policy or regulation will affect your organisation
AdvancedResearch [NEW POLICY/REGULATION] and assess impact on [ORGANISATION TYPE]. Cover: (1) What the policy requires, (2) Effective date and enforcement timeline, (3) Who is affected, (4) Compliance requirements, (5) Cost and effort to comply, (6) Penalties for non-compliance, (7) How peers are responding. Cite official sources.
Research [POLICY] and assess impact. Cover: requirements, effective date, who is affected, compliance needs, cost to comply, penalties, peer responses. Cite sources.
▸
Research Regulatory Guidance
Find and summarise the latest regulatory guidance on a compliance topic
AdvancedResearch the latest guidance on [REGULATION OR STANDARD — GDPR / HIPAA / ISO 27001 / Essential Eight] as it applies to [CONTEXT — cloud services / Microsoft 365 / data storage]. Summarise: (1) Key requirements, (2) Recent changes or updates, (3) How Microsoft 365 helps meet these requirements, (4) Gaps that need additional controls, (5) Recommended next steps. Cite official sources.
▸
Research Timeline of Developments
Build a chronological timeline of key developments on a topic
IntermediateCreate a timeline of major developments for [TOPIC] over the [TIME PERIOD — last 12 months / last 3 years]. For each entry include: the date, what happened, why it matters, and a source link. Highlight any upcoming dates or announced plans. Flag where information is based on announcements vs. confirmed releases.
Find external evidence supporting the ROI of [INITIATIVE — Copilot / cloud migration / automation / AI adoption]. Look for: (1) Published case studies with specific numbers, (2) Analyst reports (Forrester TEI, Gartner), (3) Customer testimonials, (4) Industry benchmarks, (5) Academic research. Compile as a sourced evidence appendix for a business case.
▸
Source-Backed Research Summary
Get a comprehensive research summary with citations and source links
BeginnerResearch [TOPIC] and provide a source-backed summary. Include: (1) Current state overview (3-4 paragraphs), (2) Key facts with source citations, (3) Areas where sources disagree or information is uncertain, (4) 3-5 recommended next steps or further reading. Prioritise recent and authoritative sources.
▸
Vendor Comparison Brief
Compare multiple vendors or solutions with a structured evaluation matrix
IntermediateCompare [VENDOR A], [VENDOR B], and [VENDOR C] for [USE CASE]. Evaluate each on: (1) Key features, (2) Pricing model, (3) Security and compliance certifications, (4) Integration with Microsoft 365, (5) Strengths and weaknesses, (6) Best suited for. Present as a comparison table with a recommendation at the end. Cite your sources.
📈 Analyst Agent
Analyse this A/B test: Control [A METRICS] vs Variant [B METRICS]. Determine: (1) Statistical significance (p-value), (2) Confidence interval, (3) Effect size, (4) Sample size adequacy, (5) Winner recommendation with caveats, (6) Whether to continue testing.
▸
Analyse Dataset for Top Insights
Ask the Analyst agent to find the most important patterns and trends in your data
BeginnerAnalyse this data and give me the top [NUMBER — 3 / 5] insights. For each insight explain: what the data shows, why it matters, and what I should do about it. Include a supporting chart or visualisation for the most impactful finding. Write for [AUDIENCE — management / the team / a technical audience].
Compare our metrics against industry benchmarks. Our data: [PASTE KEY METRICS]. Industry: [INDUSTRY]. For each metric: (1) Our value, (2) Industry benchmark, (3) Percentile ranking, (4) Gap analysis, (5) Whether the gap matters and what to do about it. Flag where we significantly lag or lead.
▸
Break Down Results by Dimension
Slice your data by categories to find where performance varies
IntermediateBreak down the results in this data by [DIMENSIONS — region, product, customer type, department]. For each segment show: total, average, percentage of whole, and trend direction. Highlight the best and worst performing segments. Create a chart comparing the top segments.
Group users from this data into cohorts by [CRITERIA — sign-up month / first purchase / plan tier]. Track [METRIC — retention / revenue / engagement] over [PERIODS]. Show: cohort table, trend chart, strongest vs weakest cohort, and 3 actionable insights.
▸
Create a Visual Data Report
Turn raw data into a visual report with charts, tables, and narrative
IntermediateCreate a visual report from this data for [AUDIENCE — leadership / the board / the team]. Include: (1) An executive summary of key findings in 3 bullets, (2) 2-3 charts showing the most important trends, (3) A summary table with key metrics, (4) Recommendations based on the data. Make the report clear enough to present without additional explanation.
Take these analysis results: [DESCRIBE FINDINGS]. Turn them into a data story for [AUDIENCE]. Include: (1) The headline insight (one sentence), (2) Why it matters (so what), (3) The evidence (charts and numbers), (4) What caused it, (5) What to do about it. Write for people who do not love data.
Combine data from [SOURCES] into executive dashboard. Calculate top-line KPIs with trends, department breakdown, 12-month charts, anomaly detection, next quarter forecast.
▸
Find Anomalies and Outliers
Detect unusual patterns, outliers, and data quality issues in your dataset
IntermediateScan this dataset for anomalies and outliers. Look for: (1) Values that are unusually high or low compared to the rest, (2) Sudden changes or spikes in trends, (3) Missing or suspicious data patterns, (4) Inconsistencies between related columns. For each finding, explain why it is unusual and suggest whether it is an error or a genuine anomaly worth investigating.
▸
Forecast Next Period
Project future values based on historical patterns and state assumptions
AdvancedBased on this historical data, forecast [METRIC] for the next [PERIOD — 3 months / 6 months / quarter]. Show: (1) The predicted values with confidence range, (2) The method and assumptions used, (3) Key factors that could change the forecast, (4) A chart with the historical trend and projected values. State your confidence level.
▸
Identify Key Drivers
Find what factors are driving a metric up or down and quantify their impact
AdvancedAnalyse this data and identify the biggest drivers behind [METRIC — revenue growth / ticket volume / churn rate]. For each driver: quantify its impact, explain the mechanism, and suggest what we can do about it. Rank drivers by impact size. Create a chart showing the contribution of each driver.
Classify feedback as positive, neutral, or negative. Show: sentiment distribution, positive themes, negative themes, sentiment trend, priority action areas.
💡 Brainstorming & Strategy Prompts
▸
AI Debate Partner
Use AI to challenge your ideas and find weaknesses in your arguments before presenting them
IntermediateI want to present this idea/proposal: [DESCRIBE YOUR IDEA]. Act as a critical but constructive debate partner. (1) First, summarise my idea to confirm you understand it correctly, (2) Then present the 5 strongest arguments AGAINST my idea — play devil's advocate convincingly, (3) For each counter-argument, suggest how I could address or rebut it, (4) Identify any logical fallacies or weak assumptions in my reasoning, (5) Suggest 3 improvements that would make my idea stronger, (6) Rate the overall strength of my idea on a scale of 1-10 with specific reasoning. Be tough but fair — I want to be prepared for real critics.
Compile and prioritise this feature wishlist: [LIST FEATURES/IDEAS]. For each: (1) User story format, (2) Which user persona benefits, (3) Business value (revenue/retention/efficiency), (4) Technical complexity estimate, (5) Dependencies. Group into: Must Have, Should Have, Could Have, Will Not Have (MoSCoW). Present as a release planning table.
Take these ideas: [LIST IDEAS]. Score each on: (1) Impact potential (1-10), (2) Feasibility with current resources (1-10), (3) Time to implement, (4) Risk level, (5) Strategic alignment. Calculate a priority score. Present as a ranked table with a clear recommendation for which 3 to pursue first and which to park.
▸
Problem Reframing Exercise
Reframe a problem from multiple perspectives to find new solutions
AdvancedHelp me reframe this problem: [DESCRIBE PROBLEM]. Look at it from: (1) The customer perspective, (2) The competitor perspective, (3) A completely different industry, (4) 10x scale (what if the problem was 10x bigger or smaller?), (5) Reverse — what if we caused this problem deliberately? For each reframe, suggest one insight or solution that would not be obvious from the original framing.
▸
Problem-Solving Framework
Break down a complex problem into root causes, options, and a recommended solution
IntermediateHelp me solve this problem: [DESCRIBE PROBLEM]. Walk me through it using this framework: (1) Problem Definition — restate the problem clearly in one sentence, (2) Root Cause Analysis — identify 3-5 possible root causes using the "5 Whys" technique, (3) Impact Assessment — who is affected and how severely, (4) Options — generate 3-4 possible solutions, each with pros, cons, effort level, and estimated time to implement, (5) Recommendation — which option you recommend and why, (6) Implementation Plan — first 3 steps to get started, (7) Success Metrics — how we will know the problem is solved.
Help me reverse-brainstorm [PROBLEM/CHALLENGE]. Instead of solving it, list 10 ways to make this problem dramatically worse. Then for each, reverse engineer the opposite into a potential solution. Present as a table: Way to Make it Worse then Reversed Solution then Feasibility.
Analyse [DECISION/TOPIC] using the Six Thinking Hats framework: (1) White Hat — facts and data only, (2) Red Hat — emotions and gut feelings, (3) Black Hat — risks and cautions, (4) Yellow Hat — benefits and optimism, (5) Green Hat — creative alternatives, (6) Blue Hat — process and next steps. Present each perspective clearly then synthesise into a balanced recommendation.
▸
Strategic Options Generator
Generate and evaluate multiple strategic options for a business decision or initiative
IntermediateI need to make a decision about [DECISION/INITIATIVE]. Generate 4-5 strategic options, ranging from conservative to ambitious. For each option provide: (1) Name — a clear label, (2) Description — what this option involves, (3) Investment Required — time, money, resources, (4) Expected Outcome — best case scenario, (5) Risks — what could go wrong, (6) Timeline — how long to implement, (7) Reversibility — how easy is it to change course. Then create a comparison matrix and provide your recommended option with reasoning.
▸
SWOT Analysis Generator
Create a thorough SWOT analysis for any business initiative, product, or strategic decision
BeginnerCreate a SWOT analysis for [SUBJECT]. For each quadrant provide at least 5 items: (1) Strengths — internal advantages and competitive edges, (2) Weaknesses — internal limitations and gaps, (3) Opportunities — external factors we can capitalise on, (4) Threats — external risks and competitive pressures. Then provide: (5) Strategic Priorities — the top 3 actions based on the SWOT (match Strengths to Opportunities, address Weaknesses that amplify Threats), (6) Quick Wins — 2-3 things we can do immediately. Be specific and actionable — avoid generic statements.
Create a SWOT analysis for [TOPIC/PROJECT/INITIATIVE]. For each quadrant provide 4-5 specific, actionable points: (1) Strengths — internal advantages we have, (2) Weaknesses — internal gaps to address, (3) Opportunities — external factors we can leverage, (4) Threats — external risks to mitigate. End with 3 strategic recommendations based on the analysis.
🤖 Copilot Cowork
▸
Build a Client Proposal End-to-End
Have Cowork research, draft, and package a complete client proposal
AdvancedBuild a proposal for [CLIENT NAME] for [PROJECT/SERVICE]. Steps: (1) Research recent correspondence with this client from emails and Teams, (2) Draft the proposal in Word using our [TEMPLATE] with their specific needs, (3) Create a pricing comparison in Excel with [OPTIONS — 3 tiers], (4) Build a 4-slide summary deck in PowerPoint for the pitch meeting, (5) Draft a cover email to [CLIENT CONTACT] with the proposal attached.
▸
Compile Weekly Status Report
Have Cowork gather updates from emails, Teams, and files into a single status report
IntermediateCompile my weekly status report for [WEEK/PERIOD]. Gather: (1) Action items completed from my emails and Teams chats, (2) Key decisions made in meetings this week, (3) Blockers or escalations raised, (4) Plans for next week based on my calendar. Write it up in Word as a formatted status report and email it to [MANAGER/TEAM] by end of day Friday.
Repurpose this [CONTENT] into: LinkedIn post, executive summary in Word, 3-slide deck, email to stakeholders, Teams channel post. Consistent messaging.
Compile a report on [CUSTOMER] across all touchpoints. Gather emails, meetings, support tickets, contract status. Produce a health summary in Word and 3-slide deck.
Research [TOPIC] and produce: (1) Detailed research document in Word with sources, (2) One-page executive brief, (3) 3-slide PowerPoint summary, (4) Draft email to [RECIPIENTS] with brief attached. Check in after research before final outputs.
▸
End-of-Day Wrap-Up
Have Cowork summarise your day, update your task list, and prep tomorrow
BeginnerGive me an end-of-day summary. Include: (1) What I accomplished today based on sent emails, completed tasks, and meetings attended, (2) Action items I committed to but have not done yet, (3) Tomorrow's calendar preview with prep needed, (4) Any emails that still need a response. Present as a clean daily wrap-up I can review in 2 minutes.
▸
Full Meeting Preparation Package
Have Cowork research, brief, and prepare everything you need before a big meeting
IntermediatePrepare me for my meeting with [PERSON/COMPANY] on [DATE]. Research: recent emails and chats between us, their last shared documents, any open action items. Create: (1) A one-page briefing document in Word, (2) 3-5 talking points, (3) Any data they might reference from our shared files. Add 15 minutes of prep time to my calendar before the meeting.
▸
New Hire Onboarding Coordinator
Have Cowork set up everything a new team member needs across multiple systems
IntermediateHelp me onboard [NEW HIRE NAME] joining as [ROLE] on [START DATE]. Create: (1) A welcome email with first-week schedule, (2) An onboarding checklist in a Loop page the team can update, (3) A 30/60/90 day plan in Word, (4) Calendar invites for their orientation meetings, key 1:1s, and team introductions. Send the welcome email on [DATE — day before they start]. Check in with me before sending anything external.
▸
Organise Travel Itinerary
Have Cowork compile all travel details into one organised itinerary
BeginnerCompile my travel itinerary for [TRIP — destination / dates]. Search my emails for: flight confirmations, hotel bookings, meeting invites, and any relevant documents. Create a day-by-day itinerary in Word with: travel details, meeting times and locations, contact information, and links to important documents. Add travel blocks to my calendar and set reminders for check-in times.
▸
Prepare a Quarterly Business Review
Have Cowork autonomously build a complete QBR across Excel, PowerPoint, Word, and Outlook
AdvancedPrepare my Q2 business review for [AUDIENCE — leadership / board / client]. Pull the latest numbers from [EXCEL FILE OR DATA SOURCE], create a 6-slide PowerPoint with key metrics, trends, and recommendations. Draft a one-page executive summary in Word. Then draft an email inviting [STAKEHOLDERS] to the review meeting and attach the deck. Check in with me before sending anything.
▸
Project Kickoff Package
Have Cowork create a complete project kickoff bundle — charter, timeline, RACI, and kick-off email
AdvancedCreate a project kickoff package for [PROJECT NAME]. Include: (1) A project charter in Word with objectives, scope, success criteria, and risks, (2) A timeline in Excel with phases, milestones, and owners, (3) A RACI matrix for [TEAM MEMBERS], (4) A 5-slide kickoff deck in PowerPoint, (5) A kickoff meeting invite for [DATE] with the charter attached. Base the scope on [SOURCE — these notes / this brief / this email thread].
▸
Protect My Focus Time
Have Cowork reschedule low-priority meetings and block deep work time in your calendar
IntermediateReview my calendar for the next two weeks. Reschedule any low-priority or optional meetings to free up at least 2 hours of uninterrupted focus time every day. Keep all meetings with [PRIORITY CONTACTS — my manager / clients / direct reports]. Send polite reschedule requests to affected attendees. Block the freed time as Focus Time in my calendar.
Perform a quarterly cleanup: (1) Find unfinished files for review, (2) Identify unread email subscriptions, (3) Flag inactive Teams channels, (4) Check expired sharing permissions, (5) Summarise unused licences. Present a cleanup checklist.
▸
Triage My Email Backlog
Have Cowork sort, summarise, and draft responses for your unread emails
BeginnerI have [NUMBER] unread emails from the past [PERIOD — week / 3 days / while I was on leave]. Triage them: (1) Categorise by urgency (respond today, respond this week, FYI only, can delete), (2) Summarise each urgent email in one sentence, (3) Draft responses for the top [NUMBER — 5 / 10] most urgent. Show me the drafts for approval before sending.
🤝 Customer Service Prompts
▸
Customer Complaint Response
Draft a professional response to a customer complaint that resolves the issue and retains the customer
BeginnerDraft a response to this customer complaint: [PASTE COMPLAINT]. The response must: (1) Address the customer by name, (2) Acknowledge their frustration specifically — show you read and understood their complaint, (3) Apologise sincerely without deflecting blame, (4) Explain what caused the issue in simple terms (no jargon), (5) Detail the resolution — what you are doing to fix it, (6) Provide a timeline for resolution, (7) Offer appropriate compensation or goodwill if warranted, (8) Invite them to contact you directly for follow-up. Tone: empathetic, professional, solution-focused. Keep under 200 words.
▸
Customer Feedback Analyser
Analyse customer feedback, reviews, or survey results to extract actionable insights
IntermediateAnalyse this customer feedback data and provide: (1) Sentiment Overview — percentage positive, neutral, negative, (2) Top 5 Praise Points — what customers love most, (3) Top 5 Pain Points — what customers complain about most, (4) Trending Themes — patterns that appear across multiple pieces of feedback, (5) Quick Wins — 3 improvements that would address the most common complaints with minimal effort, (6) Strategic Recommendations — 2-3 bigger changes that could significantly improve satisfaction, (7) Verbatim Highlights — the most impactful positive and negative quotes. Present with specific numbers where possible.
Create an onboarding email sequence for a new customer who just purchased [PRODUCT/SERVICE]. Email 1 (Day 0): Welcome and quick start. Email 2 (Day 3): Key feature highlight. Email 3 (Day 7): Tips for getting the most value. Email 4 (Day 14): Check-in and support offer. Each email: warm, helpful, under 150 words, with one clear action.
Write a win-back email for [CUSTOMER/SEGMENT] who [CANCELLED / STOPPED USING / WENT QUIET] [TIMEFRAME] ago. Include: (1) Acknowledge they have been away (no guilt), (2) Share what has improved since they left, (3) Offer a specific reason to return, (4) Include a limited-time incentive if appropriate, (5) Make it easy to come back (one-click CTA). Tone: welcoming, not desperate.
▸
Empathetic Customer Response
Write a response that acknowledges frustration and offers a solution
IntermediateWrite a response to this frustrated customer: [PASTE CUSTOMER MESSAGE]. Structure: (1) Acknowledge their frustration specifically, (2) Apologise sincerely without being defensive, (3) Explain what happened (briefly, no excuses), (4) State exactly what we will do to fix it, (5) Offer something extra to restore trust, (6) Provide a direct contact for follow-up. Tone: empathetic, accountable, solution-focused.
▸
FAQ Generator
Generate a comprehensive FAQ document from product info, support tickets, or customer conversations
BeginnerGenerate a comprehensive FAQ document about [PRODUCT/SERVICE/TOPIC]. Include at least 15 questions and answers organised into these sections: (1) Getting Started — basics and setup, (2) Features & Usage — how to use key features, (3) Troubleshooting — common problems and fixes, (4) Billing & Account — pricing, plans, cancellation, (5) Security & Privacy — data handling and compliance. Each answer should be 2-3 sentences, written in plain language. Include a "Still need help?" section at the end with contact information.
▸
Feature Request Response
Professionally respond to a feature request you cannot implement now
BeginnerWrite a response to a customer requesting [FEATURE]. We [CANNOT BUILD THIS / HAVE IT ON ROADMAP FOR Q[X] / NEED MORE DETAILS]. Include: (1) Thank them for the suggestion, (2) Acknowledge the value of their idea, (3) Be honest about the status, (4) Explain what we can offer as an alternative, (5) Invite them to our feedback programme. Tone: appreciative and transparent.
Write a response to this [POSITIVE / NEGATIVE / MIXED] public review: [PASTE REVIEW]. Guidelines: (1) Thank them for the feedback, (2) Address specific points they raised, (3) For negative items: acknowledge and explain what we are doing about it, (4) For positive items: reinforce and share appreciation, (5) Invite them to contact us directly for resolution. Tone: professional, gracious, genuine. Keep under 100 words.
▸
Refund Request Handler
Process a refund request with appropriate tone and policy adherence
IntermediateHandle this refund request: [CUSTOMER SITUATION]. Our refund policy: [POLICY SUMMARY]. Draft a response that: (1) Acknowledges the request, (2) Reviews eligibility against policy, (3) If approved: confirms the refund amount and timeline, (4) If denied: explains why compassionately with alternatives, (5) Offers additional support. Tone: fair, empathetic, policy-adherent.
Create a service recovery plan for [SERVICE FAILURE — outage / data issue / billing error] that affected [NUMBER] customers. Include: (1) Immediate actions (first 24 hours), (2) Customer communication sequence, (3) Root cause investigation steps, (4) Compensation or goodwill gesture (appropriate to severity), (5) Follow-up plan, (6) Prevention measures, (7) Success metrics for recovery. Balance speed with thoroughness.
Design a support dashboard. Metrics: ticket volume, resolution time, CSAT, first contact resolution, backlog age, top categories, team utilisation. Include targets and traffic lights.
▸
Turn Complaints into Feedback
Transform customer complaints into actionable product feedback
IntermediateAnalyse these customer complaints: [PASTE]. Group by theme, identify root causes, quantify frequency, assess severity, and create a prioritised feedback report for the product team.
🟠 Claude Cowork
▸
Collaborative Competitive Intelligence Brief
Have the team contribute competitive insights while Claude builds a structured analysis
AdvancedBuild a competitive intelligence brief for [COMPETITOR/MARKET]. Team members will contribute observations from: customer conversations, product usage, news articles, and industry events. As insights come in: (1) Categorise by theme (product, pricing, go-to-market, strengths, weaknesses), (2) Rate confidence level of each insight (confirmed, likely, rumour), (3) Identify patterns across contributions, (4) Summarise as a one-page competitive brief with actionable recommendations.
▸
Collaborative Document Co-Author
Draft a document together with Claude while team members contribute and edit in real time
IntermediateHelp our team co-author a [DOCUMENT TYPE — strategy document / project brief / policy / report] about [TOPIC]. Start with an outline based on these goals: [GOALS]. As team members add their sections and comments, integrate their input, maintain consistent tone and formatting, resolve any conflicting suggestions, and flag areas where more input is needed.
Help resolve a disagreement about [TOPIC]. Each person states their position. Identify common ground, name the core disagreement, present both sides, propose compromises.
▸
Incident War Room Coordinator
Use Claude Cowork as a live incident tracker during a critical issue with multiple responders
AdvancedWe have a [SEVERITY — P1 / P2] incident: [INCIDENT DESCRIPTION]. Help coordinate: (1) Maintain a live timeline of events as team members report updates, (2) Track who is working on what, (3) Log all actions taken and their results, (4) Draft stakeholder communications at [INTERVAL — every 30 minutes / hourly], (5) When resolved, compile a post-incident report with timeline, root cause, and prevention actions. Keep everything factual and time-stamped.
▸
Live Meeting Decisions Tracker
Use Claude Cowork during a meeting to capture decisions, actions, and disagreements in real time
BeginnerWe are in a meeting about [TOPIC]. As we discuss, track: (1) Decisions made (with who decided and rationale), (2) Action items (with owner and deadline), (3) Open questions that need follow-up, (4) Points of disagreement and how they were resolved. Present as a clean table the whole team can see and verify during the meeting. Update in real time as we discuss.
▸
Multi-Reviewer Document Review
Have multiple reviewers comment on a document while Claude synthesises feedback
IntermediateWe need [NUMBER] team members to review this [DOCUMENT TYPE]. As each reviewer adds their comments and suggestions: (1) Track all feedback by reviewer, (2) Identify where reviewers agree (easy fixes), (3) Highlight where reviewers disagree (needs discussion), (4) Suggest a resolution for each conflict based on the document goals, (5) Create a clean revised version incorporating the agreed changes.
Facilitate a blameless post-mortem for [INCIDENT]. Each person adds their timeline. Merge into unified timeline. Identify contributing factors. Define prevention actions.
Facilitate a 2-hour design sprint for [CHALLENGE]. Structure: (1) Problem definition (10 min), (2) How Might We questions (15 min), (3) Rapid ideation — 8 ideas in 8 minutes, (4) Dot voting, (5) Solution sketching (20 min), (6) Critique, (7) Next steps. Keep energy high.
▸
Sprint Retrospective Facilitator
Use Claude to run a structured team retrospective with anonymous input and actionable outcomes
IntermediateFacilitate a retrospective for our team covering [SPRINT/PERIOD]. Structure: (1) Collect input in three columns — What went well, What could improve, What to try next, (2) Group similar feedback into themes, (3) Let the team vote on the most important items (each person picks their top 3), (4) For the top-voted items, define a specific action, owner, and success measure, (5) Compare with last retro actions — did we follow through? Keep the tone constructive and forward-looking.
▸
Strategy Alignment Workshop
Use Claude to help a team align on strategy by structuring debate and finding common ground
AdvancedFacilitate a strategy alignment session for our team on [STRATEGIC QUESTION — e.g. Should we expand into market X?]. Structure: (1) Have each team member state their position and reasoning, (2) Identify areas of agreement and disagreement, (3) Present the strongest arguments for each position, (4) Propose a compromise or hybrid approach, (5) Draft a decision with rationale that the team can endorse. Remain neutral and ensure all voices are heard.
▸
Team Brainstorm Facilitator
Use Claude Cowork to facilitate a structured team brainstorming session in real time
BeginnerWe are brainstorming [TOPIC/CHALLENGE] as a team. Help us by: (1) Capturing every idea from the team without judgment, (2) Grouping similar ideas into themes, (3) For each theme, list pros, cons, and feasibility, (4) Summarise the top 5 ideas ranked by impact and effort, (5) Create an action plan for the winning idea. Team members will add ideas in the document — organise them as they come in.
Help us build a team charter. Each person contributes to: (1) Mission, (2) Values (2 each), (3) Working agreements, (4) Decision-making process, (5) Conflict resolution, (6) Success measures. Claude: synthesise, identify conflicts, propose unified charter.
▸
Team Knowledge Base Builder
Collaboratively build a knowledge base with Claude organising and structuring contributions
IntermediateHelp our team build a knowledge base for [TOPIC/PROJECT/PROCESS]. Team members will add their expertise, tips, and procedures. As content comes in: (1) Organise into logical categories and sections, (2) Standardise formatting and tone, (3) Cross-reference related entries, (4) Flag gaps where we need more documentation, (5) Create a table of contents. Make it easy for a new team member to navigate.
▸
Workshop Content Creator
Collaboratively design workshop content with agenda, exercises, and materials
IntermediateHelp us design a [DURATION — half-day / full-day] workshop on [TOPIC] for [AUDIENCE — new hires / leadership / cross-functional team]. Collaboratively build: (1) Agenda with time blocks and facilitator notes, (2) 3-4 interactive exercises with instructions and materials needed, (3) Discussion questions for each section, (4) Pre-work for participants, (5) Evaluation survey questions. Team members will contribute their expertise for different sections.
🎨 Image Generation Prompts
Create an image prompt that visualises [ABSTRACT CONCEPT — digital transformation / team collaboration / innovation / data security / growth]. The image should: (1) Use visual metaphor not literal representation, (2) Style: [STYLE — corporate / modern / artistic], (3) Colour mood: [MOOD — energetic / calming / powerful / futuristic], (4) Work as a hero image for a [USE — presentation / report / website]. Provide 3 different metaphor approaches.
Create a blog header image for an article titled "[ARTICLE TITLE]". The image should: (1) Visually represent the topic without being too literal, (2) Use a [STYLE] aesthetic — options: abstract geometric, isometric illustration, soft watercolour, modern flat design, cinematic photo, (3) Colour mood: [warm/cool/vibrant/muted], (4) Aspect ratio: 16:9 landscape for web, (5) Include visual metaphors related to the article topic, (6) Be clean enough to work as a thumbnail at small sizes. Do NOT include any text, words, or letters in the image.
Create an image prompt for a blog header about [TOPIC]. The image should: (1) Be eye-catching and relevant to the topic, (2) Work at 1200x630 (OG image size), (3) Use [STYLE — photorealistic / illustration / abstract / minimal], (4) Avoid text (will be overlaid separately), (5) Use colours that complement [BRAND COLOURS]. Provide prompt and negative prompt.
Generate image prompts for a set of [NUMBER — 6 / 8 / 12] matching icons for [PURPOSE — website / app / presentation / documentation]. Theme: [THEME]. Each icon should: (1) Follow the same visual style, (2) Use a consistent colour palette, (3) Work at small sizes (64x64 to 256x256), (4) Have a clean transparent background, (5) Represent: [LIST CONCEPTS]. Provide: detailed prompt and style modifiers.
▸
Presentation Visual
Generate a clean, professional visual or diagram for a presentation slide
IntermediateCreate a visual for a presentation slide about [TOPIC]. Requirements: (1) Style: clean, modern, professional — suitable for a corporate presentation, (2) Visual type: [CHOOSE — infographic-style diagram / abstract concept illustration / isometric scene / icon-based layout], (3) Colour scheme: [COLOURS or "corporate blue and white"], (4) The visual should clearly communicate [KEY CONCEPT], (5) Clean background (white or transparent-friendly), (6) Simple enough to be understood in 3 seconds from the back of a room. Do NOT include any text, numbers, or labels — those will be added in PowerPoint.
▸
Professional Avatar Creator
Generate prompts for professional AI avatars or profile pictures
BeginnerCreate an image prompt for a professional avatar in [STYLE — corporate headshot / illustrated / geometric / pixel art] style. Specifications: (1) Head and shoulders composition, (2) Neutral or professional background, (3) [CHARACTERISTICS — if applicable], (4) Warm, approachable expression, (5) Square format (1:1 ratio). Provide variations for different platforms (LinkedIn, Teams, Slack).
▸
Professional Product Photo
Generate a clean, professional product photo with studio-quality lighting
IntermediateA professional product photograph of [PRODUCT] on a clean white surface with soft studio lighting. Shot with a 85mm lens at f/2.8 for shallow depth of field. The product is centred in frame with subtle shadow underneath. Background is a smooth gradient from white to light grey. Commercial photography style, 4K resolution, photorealistic.
Create a social media banner image for [PLATFORM — LinkedIn/Twitter/YouTube/Facebook]. The design should feature: (1) A [STYLE — modern minimalist / bold gradient / professional corporate] aesthetic, (2) Main theme: [TOPIC/MESSAGE], (3) Colour palette: [BRAND COLOURS or describe mood], (4) Include subtle visual elements related to [INDUSTRY/TOPIC], (5) Leave clean space on the [left/right/centre] for text overlay, (6) Dimensions optimised for [PLATFORM] banner format. Style: clean, professional, eye-catching at small size. Do NOT include any text or words in the image — text will be added separately.
Create image generation prompts for a [NUMBER]-post social media series about [TOPIC] for [PLATFORM]. Each image should: (1) Follow a consistent visual style, (2) Use brand colours [COLOURS], (3) Work at [DIMENSIONS — 1080x1080 / 1200x628 / 1080x1920], (4) Leave space for text overlay. Provide: detailed prompt, negative prompt, and text placement guide.
👥 People & HR
Create a 30/60/90-day onboarding plan for a new [ROLE] joining [TEAM/DEPARTMENT]. Include: (1) Week 1: orientation, tools setup, key contacts, (2) Days 1-30: learning goals and shadowing, (3) Days 31-60: first deliverables and independence, (4) Days 61-90: full ownership and review. Add success metrics for each phase and a buddy/mentor assignment.
Help me prepare for a difficult conversation with [EMPLOYEE NAME] about [SITUATION — performance issue / behaviour concern / role change / redundancy]. Draft: (1) Opening statement that is direct but empathetic, (2) Key facts and specific examples, (3) Impact of the situation, (4) Clear expectations going forward, (5) Support offered. Tone: respectful, factual, and solution-focused.
Create a D&I report. Include: demographics, hiring diversity, promotion rates by group, pay equity, employee sentiment, progress vs goals, action plan.
▸
Employee Engagement Survey Designer
Create a focused employee engagement survey with analysis framework
IntermediateDesign a [NUMBER — 10 / 15 / 20]-question employee engagement survey for [DEPARTMENT/COMPANY]. Cover: (1) Job satisfaction, (2) Manager relationship, (3) Growth opportunities, (4) Work-life balance, (5) Company culture. Use a mix of 1-5 scale questions and open-ended questions. Include a scoring framework and benchmark targets.
Analyse these exit interview responses from [NUMBER] departing employees. Identify: (1) Top 5 reasons for leaving, (2) Common themes and patterns, (3) Which departments or roles are most affected, (4) Specific actionable recommendations to improve retention, (5) Quick wins vs long-term changes. Present as an executive summary with a data table.
▸
Interview Question Generator
Create role-specific interview questions with scoring rubrics
IntermediateGenerate 10 interview questions for a [ROLE] candidate. Include: 3 technical/skill questions, 3 behavioural (STAR format), 2 situational, and 2 culture-fit questions. For each question provide: what good looks like, what a red flag looks like, and a 1-5 scoring guide.
Write a job description for [ROLE] at [COMPANY/TEAM]. Include: (1) An engaging role summary (not a requirement list), (2) Key responsibilities (5-7 bullets), (3) Must-have skills (keep to 5), (4) Nice-to-have skills (3 max), (5) What we offer (benefits, culture, growth). Use inclusive language. Remove unnecessary requirements that could discourage diverse candidates.
▸
Performance Review Draft
Write a balanced performance review with specific examples and growth areas
IntermediateWrite a performance review for [EMPLOYEE NAME] in the role of [ROLE]. Based on these achievements: [ACHIEVEMENTS] and these areas for improvement: [AREAS]. Include: (1) Overall assessment, (2) Key strengths with specific examples, (3) Growth areas with actionable suggestions, (4) Goals for next period. Tone: constructive, specific, and fair.
▸
Resume Fit Scorer
Score a candidate resume against a job description with strengths and gaps
IntermediateReview this resume and compare it to the job description for [ROLE]. Score the candidate 1-10 on: (1) Technical skills match, (2) Experience level, (3) Culture fit indicators, (4) Red flags or gaps. Provide a 3-sentence summary and recommend: Strong Yes, Yes, Maybe, or No.
Research the current salary range for [ROLE] in [LOCATION/MARKET]. Consider: (1) Experience levels (junior, mid, senior), (2) Industry variations, (3) Remote vs on-site differences, (4) Total compensation including benefits. Present as a table with low, median, and high ranges. Note your sources and confidence level.
Create a succession plan for [ROLES]. For each: current holder, criticality, ready-now successors, ready-in-1-year, development plans, vacancy risk, interim coverage.
Suggest 5 icebreaker activities for a [TYPE — team meeting / workshop / all-hands / virtual event] with [NUMBER] participants. Each icebreaker should: take under 5 minutes, work for both introverts and extroverts, not require preparation from participants, and relate to [THEME — team bonding / creativity / learning / fun]. Include instructions for each.
🖥️ IT Administration
Prepare a Change Advisory Board (CAB) submission for [CHANGE DESCRIPTION]. Include: (1) Change description and business justification, (2) Risk assessment (likelihood and impact), (3) Implementation plan with rollback procedure, (4) Testing completed, (5) Communication plan, (6) Affected systems and users, (7) Maintenance window requested. Rate overall risk as Low/Medium/High.
▸
End User Troubleshooting Guide
Create a self-service troubleshooting guide for common IT issues
BeginnerCreate a self-service troubleshooting guide for [ISSUE — VPN problems / printer issues / password resets / Teams audio issues / Outlook sync]. Structure as: (1) Symptom description (what the user sees), (2) Quick fixes to try first (ordered easiest to hardest), (3) Screenshots or descriptions of what to click, (4) When to contact IT support, (5) Information to have ready when calling. Write for non-technical users.
Create a capacity report for [INFRASTRUCTURE]. Include: usage vs capacity, growth trend, projected exhaustion date, top consumers, optimisation tips, procurement timeline.
▸
IT Change Communication for End Users
Write a user-friendly notification about an upcoming IT change
BeginnerWrite an end-user communication about [IT CHANGE — system upgrade / maintenance window / new tool rollout / policy change]. Include: (1) What is changing in plain English, (2) When it happens, (3) How it affects them specifically, (4) What they need to do (if anything), (5) Where to get help. Tone: friendly, clear, and reassuring. Keep it under 200 words.
▸
IT Incident Report Template
Draft a structured incident report for a service disruption
IntermediateWrite an IT incident report for [INCIDENT DESCRIPTION]. Include: (1) Incident summary and timeline, (2) Impact assessment (users affected, services down, duration), (3) Root cause analysis, (4) Resolution steps taken, (5) Preventive measures for the future, (6) Lessons learned. Format for both technical and executive audiences.
▸
IT Policy Document Draft
Create an IT policy document with proper structure and enforcement guidelines
IntermediateDraft an IT policy for [POLICY TOPIC — acceptable use / BYOD / password / remote access / data classification]. Include: (1) Purpose and scope, (2) Policy statements with clear rules, (3) Roles and responsibilities, (4) Exceptions process, (5) Enforcement and consequences, (6) Review schedule. Write in plain English that non-technical staff can understand.
▸
M365 Licence Optimisation Report
Analyse Microsoft 365 licence usage and recommend cost savings
AdvancedCreate a licence optimisation report for our Microsoft 365 tenant. Analyse: (1) Licences assigned vs actively used (last 90 days), (2) Users with premium licences who only use basic features, (3) Shared mailboxes or service accounts with unnecessary licences, (4) Recommended downgrades or removals, (5) Estimated monthly savings. Present as a table with user counts and cost impact.
▸
M365 Tenant Health Summary
Generate a monthly health summary of your Microsoft 365 environment
AdvancedCreate a monthly health summary report for our Microsoft 365 tenant. Cover: (1) Service health incidents this month, (2) User growth and licence utilisation, (3) Security alerts and recommendations from Secure Score, (4) Storage usage trends, (5) Top support tickets, (6) Upcoming changes from Message Centre. Present as a dashboard-style summary with red/amber/green ratings.
Draft patch communications for [UPDATE]. Include: pre-patch notification, day-of reminder, during-maintenance updates, completion confirmation, known issues.
Write a security awareness email to all staff about [THREAT — phishing / MFA fatigue / social engineering / credential theft / QR code scams]. Include: (1) What the threat is in simple terms, (2) A real example of how it works, (3) How to spot it (3-4 warning signs), (4) What to do if they encounter it, (5) What to do if they already clicked. Tone: urgent but not alarming.
▸
Third-Party Vendor Access Review
Audit and document third-party vendor access to your environment
AdvancedCreate a vendor access review document for [VENDOR NAME]. Document: (1) What systems and data they can access, (2) Authentication method (SSO, VPN, direct), (3) User accounts and privilege levels, (4) Last access review date, (5) Business justification for continued access, (6) Compliance requirements (SOC2, ISO, etc.), (7) Recommendation: maintain, reduce, or revoke access.
▸
User Offboarding Checklist
Create a comprehensive IT offboarding checklist for departing employees
BeginnerCreate an IT offboarding checklist for an employee leaving [DEPARTMENT]. Include: (1) Account disablement steps (Entra ID, M365, VPN, apps), (2) Data backup and transfer procedures, (3) Device recovery checklist, (4) Licence reclamation, (5) Access review for shared resources, (6) Communication to relevant teams. Order by urgency — what must happen on day 1 vs within 30 days.
💼 Sales & Business Development
Write a cold outreach email to [PERSONA — CTO / IT Director / CFO] at [COMPANY] about [PRODUCT/SERVICE]. Hook them with a relevant insight about their industry or company. Keep it to 3 short paragraphs: (1) Personalised hook, (2) How we help companies like theirs (one specific outcome), (3) Low-pressure CTA (not asking for a meeting — offering value). Under 100 words total.
Create a battle card comparing [OUR PRODUCT] vs [COMPETITOR]. Include: (1) Feature comparison table, (2) Where we win (3 strengths), (3) Where they win (be honest), (4) How to handle it when prospect mentions competitor, (5) Key differentiators in one sentence, (6) Customer switching stories. Format for quick reference during a call.
Write a deal summary for [COMPANY NAME]. Include: (1) Deal value and expected close date, (2) Current stage and next step, (3) Key stakeholders and their positions (champion, decision maker, blocker), (4) Competitive situation, (5) Risks to closing, (6) What we need to win. Keep it to one page for pipeline review.
Create discovery questions for a call with [PROSPECT TYPE] evaluating [SOLUTION]. Include: (1) Rapport opener, (2) Current state questions, (3) Impact questions, (4) Vision questions, (5) Process questions, (6) Next steps. Order broad to specific.
Research [COMPANY NAME] and prepare a sales briefing. Include: (1) Company overview and recent news, (2) Industry challenges they likely face, (3) Their current tech stack if publicly known, (4) Key decision makers to engage, (5) Potential pain points our solution addresses, (6) Conversation starters based on their recent announcements.
Create a QBR outline for [CUSTOMER]. Include: relationship summary, usage metrics, ROI achieved, support summary, roadmap highlights, expansion opportunities, action items. Slide outline with talking points.
▸
Quarterly Business Review Deck Outline
Structure a QBR presentation for an existing customer
AdvancedCreate a QBR presentation outline for [CUSTOMER NAME]. Include: (1) Relationship summary and key contacts, (2) Usage and adoption metrics, (3) ROI achieved vs promised, (4) Support ticket summary, (5) Product roadmap highlights relevant to them, (6) Expansion opportunities, (7) Action items and next steps. Format as a slide outline with talking points.
Create 2 email variants for A/B testing. Target: [PERSONA]. Variant A: pain-point focused. Variant B: benefit-led. Same CTA. Include hypothesis and tracking metrics.
▸
Sales Follow-Up Email Sequence
Create a multi-touch follow-up sequence after a demo or meeting
BeginnerCreate a 5-email follow-up sequence after a [DEMO/MEETING] with [PROSPECT NAME] at [COMPANY]. Email 1: Same day thank you + recap. Email 2: Day 3 value-add content. Email 3: Day 7 case study share. Email 4: Day 14 check-in with urgency. Email 5: Day 21 final outreach. Each email under 100 words. Tone: helpful, not pushy.
Create responses for these common sales objections for [PRODUCT/SERVICE]: (1) It is too expensive, (2) We are happy with our current solution, (3) We do not have budget right now, (4) I need to check with my team, (5) Can you send me more information, (6) We tried something similar before and it did not work. For each: acknowledge the concern, reframe with value, and suggest a next step.
Draft a sales proposal for [COMPANY NAME] for [PRODUCT/SERVICE]. Include: (1) Executive summary addressing their specific needs, (2) Proposed solution with key features mapped to their challenges, (3) Implementation timeline, (4) Pricing options with a recommended tier, (5) Case study reference from a similar client, (6) Next steps and call to action.
Analyse recent deals. For each: details, decision factors, competitor, what worked or failed, customer feedback. Synthesise: top win reasons, top loss reasons, recommendations.
💰 Finance & Accounting
▸
Budget Planning Template
Create a departmental budget template with categories and formulas
IntermediateCreate a budget planning template for [DEPARTMENT] for [FISCAL YEAR]. Include: (1) Revenue categories with line items, (2) Operating expenses by category (personnel, software, travel, training), (3) Capital expenditure section, (4) Monthly and quarterly breakdowns, (5) Variance tracking columns (budget vs actual), (6) Summary dashboard row with key ratios. Add formulas for totals, percentages, and year-over-year comparison.
▸
Cost Reduction Opportunity Analysis
Identify areas where spending can be reduced or optimised
AdvancedAnalyse our spending data and identify cost reduction opportunities. Review: (1) Subscriptions and recurring costs (look for unused or duplicate tools), (2) Vendor consolidation potential, (3) Process automation savings, (4) Licence right-sizing, (5) Contract renegotiation opportunities. For each opportunity estimate: annual savings, implementation effort, and risk. Rank by ROI.
▸
Expense Variance Analysis
Analyse actual vs budget spending and explain the differences
IntermediateAnalyse the expense variance between budget and actual for [PERIOD]. For each line item that varies by more than [THRESHOLD — 5% / 10% / ]: (1) State the variance amount and percentage, (2) Classify as favourable or unfavourable, (3) Explain the likely cause, (4) Recommend whether it is a one-time variance or a trend, (5) Suggest corrective action if needed. Summarise total impact.
▸
Internal Audit Preparation Checklist
Prepare for an upcoming internal or external audit
IntermediateCreate an audit preparation checklist for [AUDIT TYPE — financial / IT / compliance / SOC2]. Include: (1) Documents to prepare and organise, (2) Access and permissions to set up for auditors, (3) Key contacts and their responsibilities, (4) Common findings from previous audits to pre-check, (5) Timeline from 4 weeks before to audit day, (6) Post-audit follow-up actions. Assign owners to each item.
▸
Invoice Reconciliation Helper
Compare invoices against purchase orders and flag discrepancies
BeginnerCompare these invoices against the purchase orders and flag: (1) Amount mismatches (over-billing or under-billing), (2) Missing line items, (3) Incorrect quantities, (4) Duplicate invoices, (5) Invoices without a matching PO. Present discrepancies in a table with invoice number, PO number, expected amount, actual amount, and status. Calculate total discrepancy value.
Create a monthly financial summary for [MONTH/PERIOD]. Include: (1) Revenue vs target (with percentage achievement), (2) Key expense categories and notable changes, (3) Profitability metrics, (4) Cash flow highlights, (5) Top 3 financial risks, (6) Outlook for next month. Present as a one-page executive summary with a traffic light dashboard. Use plain English.
Using the last [PERIOD — 12 / 24] months of revenue data, create a forecast for the next [PERIOD — 3 / 6 / 12] months. Include: (1) Trend analysis, (2) Seasonal adjustments if patterns exist, (3) Best case, expected, and worst case scenarios, (4) Key assumptions stated clearly, (5) Confidence level for each scenario. Present as a table with a trend chart.
Calculate ROI for [INITIATIVE]. Include: total investment, quantified benefits, payback period, 3-year NPV, IRR, break-even, sensitivity analysis, risk-adjusted ROI. Present with recommendation.
▸
Travel Expense Policy Summary
Create a clear expense policy summary employees can actually follow
BeginnerSummarise our travel and expense policy into a clear one-page guide for employees. Include: (1) What is covered (flights, hotels, meals, transport), (2) Spending limits per category, (3) Approval requirements, (4) Receipt and documentation rules, (5) Reimbursement timeline, (6) Common mistakes to avoid. Use a table format. Write so clearly that new employees can follow it on day one.
Compare [VENDORS] for [SERVICE]. Include: licence costs, implementation, training, maintenance, hidden costs, 3-year TCO, per-user cost, contract flexibility. Side-by-side table.
📢 Marketing
Design an A/B test plan for [WHAT TO TEST — email subject lines / landing page headlines / CTA buttons / ad copy]. Include: (1) Hypothesis, (2) Variable A vs Variable B descriptions, (3) Success metric, (4) Sample size needed, (5) Test duration, (6) Expected outcome, (7) Decision criteria for the winner. Keep the test focused on one variable.
Create a blog post outline for [TOPIC] targeting the keyword [KEYWORD]. Include: (1) SEO-optimised title (under 60 chars), (2) Meta description (under 155 chars), (3) H2 and H3 heading structure, (4) Key points for each section, (5) Internal linking opportunities, (6) CTA at the end. Target word count: [LENGTH — 1000 / 1500 / 2000] words.
Create a campaign brief for [CAMPAIGN NAME] targeting [AUDIENCE]. Include: (1) Campaign objective and KPIs, (2) Target audience persona, (3) Key message and value proposition, (4) Channels and tactics, (5) Timeline and milestones, (6) Budget allocation, (7) Success metrics. Format as a one-page brief.
Analyse the content strategy of [COMPETITOR]. Review their: (1) Blog topics and posting frequency, (2) Social media presence and engagement, (3) SEO keywords they rank for, (4) Content formats (video, guides, webinars), (5) Gaps we can exploit. Present as a comparison table with opportunities for us to differentiate.
Build [NUMBER — 2 / 3] customer personas for [PRODUCT/SERVICE]. For each persona include: (1) Name, role, and demographics, (2) Goals and motivations, (3) Pain points and challenges, (4) How they discover solutions, (5) Objections they might have, (6) Channels where they spend time, (7) A quote that captures their mindset. Base on [DATA SOURCE — surveys / interviews / market research].
Create a case study outline for [CUSTOMER] who achieved [RESULT] using [PRODUCT]. Include: headline with result, customer profile, problem, why they chose us, implementation, results with metrics, customer quote. Include interview questions.
Draft an email to [CUSTOMER NAME] requesting a testimonial or case study about their experience with [PRODUCT/SERVICE]. Include: (1) Warm opening referencing their success, (2) Why their story matters, (3) What the process involves (10-min call or written Q&A), (4) How we will use it (website, sales materials), (5) Easy opt-out. Tone: grateful and low-pressure.
Write a [NUMBER — 3 / 5 / 7]-email nurture sequence for [PRODUCT/SERVICE] targeting [AUDIENCE]. For each email: subject line (under 50 chars), preview text, body (under 150 words), and CTA. Space emails [FREQUENCY — 3 days / weekly] apart. Theme: educate first, then convert.
Create a promotion plan for [EVENT NAME] on [DATE]. Include: (1) Event landing page copy, (2) 3-email invitation sequence (save the date, register now, last chance), (3) 5 social media posts with countdown, (4) Internal promotion for employees, (5) Post-event follow-up email. Include registration CTA in every piece.
Create a product launch plan for [PRODUCT/FEATURE]. Include: (1) Launch messaging framework (headline, subhead, 3 key benefits), (2) Press release draft, (3) Blog post outline, (4) Social media post series (5 posts across platforms), (5) Internal announcement for sales team, (6) Email to existing customers. All materials should use consistent messaging.
Create an SEO content brief for an article targeting [PRIMARY KEYWORD]. Include: (1) Target keyword and related terms, (2) Search intent analysis, (3) Competitor content review (top 3 results), (4) Recommended word count, (5) Heading structure with H2s and H3s, (6) Key points to cover, (7) Internal and external linking suggestions, (8) Featured snippet opportunity.
🎧 Customer Support
▸
CSAT Follow-Up Message
Draft a follow-up message based on customer satisfaction feedback
IntermediateDraft a follow-up message to [CUSTOMER] who gave a [SCORE — 1-2 negative / 3 neutral / 4-5 positive] CSAT score after their support interaction about [ISSUE]. For negative: empathise, ask what went wrong, offer to make it right. For positive: thank them, ask for a testimonial. Tone: genuine, not scripted.
Draft a proactive check-in email for [CUSTOMER] who is [DAYS] days into onboarding with [PRODUCT]. Include: (1) Warm personal check-in, (2) Ask how their experience has been, (3) Share a tip they probably have not discovered, (4) Offer a quick call if they need help, (5) Link to helpful resource. Tone: caring, not salesy. Under 100 words.
Draft an escalation update for [CUSTOMER] about [ISSUE] that has been escalated to [TEAM]. Include: (1) Acknowledgement that we understand the urgency, (2) What we are doing (specific actions), (3) Who is working on it (by role, not name), (4) Expected next update time, (5) What they can do in the meantime (workaround). Tone: professional, empathetic, and confident.
▸
Knowledge Base Article Writer
Write a searchable knowledge base article from a resolved ticket
BeginnerWrite a knowledge base article for [ISSUE TITLE]. Include: (1) Problem description (what the user sees), (2) Cause (why it happens), (3) Solution (step-by-step fix), (4) Prevention (how to avoid it), (5) Related articles, (6) Keywords for searchability. Write at a level a non-technical user can follow. Include when to contact support if the fix does not work.
▸
Quarterly Support Performance Review
Analyse support team metrics and trends for the quarter
AdvancedCreate a quarterly support performance review for [PERIOD]. Analyse: (1) Ticket volume and trends, (2) Average resolution time, (3) CSAT scores by category, (4) First contact resolution rate, (5) Top 10 issue categories, (6) Escalation rate, (7) Team productivity metrics. Highlight: improvements, areas of concern, and recommendations. Present with charts and a narrative summary.
Create handoff notes for the [INCOMING SHIFT — morning / evening / weekend] support team. Include: (1) Active high-priority tickets with status, (2) Pending customer callbacks, (3) Known issues or outages, (4) Escalations in progress, (5) Important context the next shift needs, (6) Staffing notes (who is available for what). Format for a 5-minute standup review.
Create an SLA performance report for [PERIOD]. Include: (1) SLA targets vs actual for each metric, (2) Breach count and root causes, (3) Trend vs previous periods, (4) At-risk SLAs for next period, (5) Improvement actions, (6) Customer satisfaction correlation with SLA performance.
Create [NUMBER — 10 / 15] support response templates for common [PRODUCT/SERVICE] support scenarios. For each template: (1) Scenario description, (2) Response text with [PLACEHOLDERS] for personalisation, (3) Tone guidance, (4) When to use vs not use this template, (5) Follow-up action if needed. Cover: greeting, common issues, billing, feature requests, and closing.
▸
Support Ticket Trend Analysis
Analyse support ticket patterns to prevent recurring issues
IntermediateAnalyse support tickets from [PERIOD]. Identify: (1) Top 10 issue categories by volume, (2) Trending up vs down vs stable, (3) Average resolution time by category, (4) Tickets that could be prevented with documentation, (5) Tickets that need a product fix, (6) Staffing implications. Recommend 3 actions to reduce ticket volume.
▸
Tone-Matched Response Templates
Create support response templates for different customer emotions
IntermediateCreate response templates for these customer emotional states: (1) Angry and frustrated, (2) Confused and lost, (3) Anxious and worried, (4) Happy but has a question, (5) Disappointed after a promise broken. Each template: acknowledge emotion, match energy appropriately, provide solution, next step. Include tone guidance.
🔧 IT Troubleshooting
Write a blameless post-incident report for [INCIDENT]. Include: (1) Executive summary (2 sentences), (2) Timeline of events with timestamps, (3) Impact assessment (users, revenue, SLA), (4) Root cause analysis, (5) What went well in the response, (6) What could be improved, (7) Action items with owners and deadlines. Tone: factual, constructive, forward-looking.
Create a diagnostic decision tree for [ISSUE TYPE — network connectivity / application crash / login failure / slow performance / email delivery]. Structure as: If symptom A → check B → if yes → do C, if no → check D. Include: expected outcomes at each step, escalation triggers, and resolution confirmations. Write for a Level 1 support technician.
Help me diagnose email delivery failure. Scenario: [DESCRIBE — emails not received / going to spam / bouncing / delayed]. Check: (1) Message trace in Exchange Admin, (2) SPF/DKIM/DMARC alignment, (3) Transport rules that might redirect, (4) Recipient mailbox issues, (5) IP reputation, (6) Content filtering triggers. Provide step-by-step diagnosis with Exchange admin paths.
▸
End User Self-Service Fix Guide
Write a simple troubleshooting guide for non-technical users
BeginnerWrite a self-help troubleshooting guide for [ISSUE] that a non-technical user can follow. Structure: (1) What you are experiencing (symptom description), (2) Try this first (easiest fix), (3) If that did not work, try this (next steps), (4) Still stuck? Contact IT (what info to provide). Use simple language, include where to click, and add helpful screenshots descriptions.
▸
Escalation Handoff Summary
Prepare a complete handoff when escalating to higher-level support
IntermediateWrite an escalation summary for [ISSUE] being escalated to [TEAM — Level 2 / vendor / engineering]. Include: (1) Issue description and business impact, (2) Users affected and timeline, (3) All troubleshooting steps attempted and results, (4) Relevant logs, error messages, or screenshots, (5) Current hypothesis, (6) Urgency and SLA deadline. Format for quick consumption.
Help me triage this IT incident: [DESCRIBE THE ISSUE]. (1) Classify severity (P1-P4) based on user impact, (2) Identify the most likely affected system or service, (3) List 5 diagnostic checks to run immediately, (4) Suggest the probable root cause, (5) Recommend whether to escalate or resolve at this level, (6) Draft a status update for affected users.
Create a known error database entry for [ISSUE]. Include: (1) Error title and ID, (2) Symptoms the user sees, (3) Affected systems and versions, (4) Root cause explanation, (5) Workaround steps, (6) Permanent fix status and ETA, (7) Related incidents. Format for searchability in a knowledge base.
Create a troubleshooting guide for login failures in [SYSTEM — M365 / VPN / application]. Cover: (1) Password issues (expired, locked, forgotten), (2) MFA problems (lost device, token expired), (3) Conditional Access blocks, (4) Account disabled, (5) SSO failures, (6) Browser and cache issues. For each: symptoms, diagnosis steps, resolution, and prevention.
Help me diagnose this network issue: [SYMPTOMS]. Walk through: (1) Client-side checks (IP, DNS, gateway), (2) Internal network checks (switches, VLAN, firewall rules), (3) External connectivity (ISP, DNS resolution, latency), (4) Application-specific checks, (5) Recent changes that might correlate. Provide commands to run at each step.
Guide for Outlook issues: not opening, not receiving email, calendar not syncing, missing shared mailbox, slow performance, missing folders. Try first, try next, contact IT.
▸
Performance Issue Diagnosis
Systematically diagnose slow system or application performance
IntermediateHelp me diagnose slow performance in [SYSTEM/APPLICATION]. Walk me through: (1) Quick checks (CPU, memory, disk, network baseline), (2) Identifying the bottleneck, (3) Correlation with recent changes or events, (4) User-side vs server-side diagnosis, (5) Top 5 most common causes for this type of slowness, (6) Recommended monitoring to set up. Environment: [DETAILS].
Conduct a root cause analysis for [INCIDENT DESCRIPTION]. Use the 5 Whys method: (1) State the problem, (2) Ask why 5 times drilling deeper each time, (3) Identify the true root cause, (4) Distinguish symptoms from causes, (5) Recommend corrective actions to prevent recurrence, (6) Assign owners and timelines. Keep blameless — focus on systems not people.
Guide for SharePoint issues: cannot access site, sync not working, file locked, version conflict, permission errors, search not finding docs. Symptoms, steps, prevention.
Create a troubleshooting guide for Teams audio: (1) Cannot hear others, (2) Others cannot hear me, (3) Echo, (4) Audio cutting out, (5) Wrong device. For each: ordered fix steps, settings locations, when to contact IT. Write for non-technical users.
⚙️ Automation & Workflows
Design an approval workflow for [PROCESS]. Include: (1) Form fields, (2) Routing rules (by amount, type, department), (3) Escalation if unapproved within [TIME], (4) Notifications (submitted, approved, rejected, escalated), (5) Audit trail. Power Automate actions specified.
Design an automated workflow that generates a [FREQUENCY — daily / weekly / monthly] [REPORT TYPE] report. Include: (1) Data sources to pull from, (2) Calculations and transformations needed, (3) Report format and layout, (4) Distribution list and delivery method, (5) Schedule and timing, (6) Error notification if report fails, (7) Archive and retention policy.
Calculate the ROI for automating [PROCESS]. Include: (1) Current manual effort (hours per week, people involved, error rate), (2) Automation development cost (hours to build), (3) Ongoing maintenance estimate, (4) Time savings per week after automation, (5) Break-even point, (6) Annual ROI percentage, (7) Non-financial benefits (accuracy, speed, satisfaction). Present as a one-page business case.
Write a standard operating procedure for [AUTOMATED PROCESS]. Include: (1) Purpose and business context, (2) How the automation works (plain English), (3) Normal operation — what to expect, (4) How to monitor it, (5) What to do when it fails (manual fallback steps), (6) How to modify or update it, (7) Owner and review schedule. Write for someone inheriting this automation.
Design a chatbot conversation flow for handling [USE CASE — IT password resets / leave requests / FAQ / order status]. Include: (1) Welcome message and intent detection, (2) Main conversation branches, (3) Questions to ask and in what order, (4) Integration points (API calls, database lookups), (5) Handoff to human agent triggers, (6) Fallback and error messages. Map as a decision tree.
Design a data pipeline from [SOURCE] to [DESTINATION] for [PURPOSE]. Include: (1) Data extraction method, (2) Transformation rules, (3) Loading strategy (full vs incremental), (4) Schedule, (5) Error handling and alerting, (6) Data quality checks, (7) Monitoring dashboard. Consider volume, freshness, and reliability.
Design an automated onboarding workflow triggered when HR adds a new hire. Steps: (1) Create accounts and assign licences, (2) Add to groups and distribution lists, (3) Send welcome email with setup instructions, (4) Create onboarding task list, (5) Schedule orientation meetings, (6) Assign buddy, (7) Day-30 check-in reminder to manager.
Analyse this manual process: [DESCRIBE PROCESS]. Map it for automation: (1) Current steps with time per step, (2) Which steps can be automated vs need human judgment, (3) Recommended automation tool (Power Automate, script, API), (4) Trigger event, (5) Data flow between steps, (6) Exception handling, (7) Estimated time savings. Present as a process flow.
Design monitoring alert rules for [SYSTEM/APPLICATION]. For each alert define: (1) What to monitor (metric/log pattern), (2) Threshold or condition, (3) Severity level (info/warning/critical), (4) Who gets notified, (5) Expected response action, (6) Suppression rules to prevent alert storms. Target: actionable alerts only — every alert should require a response.
Design a Power Automate flow for [USE CASE — approval workflow / email notification / data sync / form processing]. Include: (1) Trigger type, (2) Each action step with configuration, (3) Conditions and branches, (4) Error handling and retry logic, (5) Notification to stakeholders, (6) Testing checklist. Specify which connectors are needed.
Design auto-response rules for [SCENARIO]. Include: triggers, templates by sender type, escalation rules, follow-up sequence, exclusion rules to prevent loops.
Design a notification system for [TOOL/PROCESS] that reduces noise. Include: (1) Notification categories by urgency, (2) Channel routing rules (email for urgent, Teams for FYI, digest for low), (3) Frequency caps, (4) Quiet hours, (5) User preference settings, (6) Escalation for unacknowledged critical alerts.
Design an integration between [SYSTEM A] and [SYSTEM B] for [BUSINESS OUTCOME]. Include: (1) Data fields to sync and direction, (2) Sync frequency (real-time, scheduled, on-demand), (3) Authentication method, (4) Error handling and conflict resolution, (5) Data transformation rules, (6) Testing approach, (7) Monitoring and alerting. Consider security and data privacy.
📣 Internal Communications
Draft a change management communication for [CHANGE — new system / process update / policy change / tool migration]. Include: (1) What is changing and why, (2) What stays the same (reassurance), (3) Timeline with key dates, (4) Training and support available, (5) FAQ for common concerns, (6) Feedback channel. Tone: supportive, clear, proactive.
Draft a company-wide announcement about [NEWS — new policy / leadership change / office move / product launch / restructure]. Include: (1) What is happening (clear, direct), (2) Why this matters, (3) How it affects employees, (4) Timeline, (5) What they need to do, (6) Where to ask questions. Tone: transparent, confident, and empathetic. Under 250 words.
Draft crisis communications for [SITUATION — service outage / data incident / safety issue / PR crisis]. Create: (1) Initial acknowledgement (within 1 hour — short, factual), (2) Detailed update (within 4 hours — what we know, what we are doing), (3) Resolution communication (when resolved — what happened, what we learned). Each version for: internal staff, customers, and media (if needed).
Create an urgent FAQ for [CRISIS] targeting [AUDIENCE]. Include: (1) What happened, (2) 15-20 anticipated questions by frequency, (3) Approved answers, (4) Default response for unlisted questions, (5) Spokesperson contacts. Update as new info becomes available.
Write a one-page executive briefing on [TOPIC] for [AUDIENCE — CEO / board / leadership team]. Structure: (1) Bottom line up front (one sentence), (2) Context (why this matters now), (3) Key facts or data (3-5 bullet points), (4) Options with pros and cons, (5) Recommended action, (6) Talking points if they need to communicate this further.
Create [NUMBER] FAQ for [TOPIC] for [AUDIENCE]. Cover: basic questions, how it affects them, technical questions, concerns, next steps. 2-3 sentences per answer.
Create an FAQ document for [TOPIC/CHANGE/PRODUCT] targeting [AUDIENCE]. Include [NUMBER — 10 / 15 / 20] questions covering: (1) Basic what and why questions, (2) How it affects them specifically, (3) Technical or process questions, (4) Concerns and objections, (5) Support and next steps. Each answer: clear, concise, empathetic. 2-3 sentences maximum per answer.
Create an internal newsletter for [AUDIENCE — all staff / department / leadership]. Include: (1) Catchy subject line, (2) Short intro with the key message, (3) 3-4 sections with headlines, brief content, and links, (4) Employee spotlight or shout-out, (5) Upcoming dates and events, (6) CTA or fun element. Keep total reading time under 3 minutes.
Write a stakeholder update for [PROJECT NAME] for [PERIOD]. Structure: (1) Status summary (On Track / At Risk / Blocked), (2) Key accomplishments this period, (3) Upcoming milestones, (4) Risks and mitigation actions, (5) Decisions needed from stakeholders, (6) Budget status. Keep it to one page. Use traffic light indicators for quick scanning.
Write a speaking script for a [DURATION — 10 / 15 / 20]-minute town hall segment about [TOPIC]. Include: (1) Opening hook that connects to the audience, (2) Key messages (3 maximum), (3) Data or stories to support each message, (4) Anticipated questions with suggested answers, (5) Closing with clear call to action. Mark pause points and emphasis words. Tone: [TONE — inspiring / transparent / urgent].
🗺️ Strategy & Planning
Write a business case for [INITIATIVE/INVESTMENT]. Include: (1) Executive summary, (2) Problem statement with data, (3) Proposed solution, (4) Options considered (including do nothing), (5) Cost breakdown (one-time and recurring), (6) Expected benefits (quantified where possible), (7) Timeline, (8) Risks, (9) Recommendation. Format for [AUDIENCE — board / leadership / finance].
Build a decision framework for [DECISION]. Include: (1) Decision statement, (2) Decision criteria with weights, (3) Options to evaluate, (4) Scoring template, (5) Risk assessment per option, (6) Stakeholder input needed, (7) Timeline and decision deadline, (8) Communication plan for the decision. Help us make this decision objectively.
Create an agenda for a [DURATION]-minute [MEETING TYPE — team meeting / planning session / review / workshop]. Include: (1) Meeting purpose (one sentence), (2) Pre-read or preparation required, (3) Agenda items with time allocation, discussion lead, and expected outcome (decision, input, or FYI), (4) Parking lot section, (5) Action items template. Total time must equal [DURATION].
Generate OKRs for [TEAM/DEPARTMENT] for [PERIOD — Q1/Q2/H1/annual]. Create [NUMBER — 3 / 4] objectives, each with 3-4 key results. Objectives should be ambitious and qualitative. Key results should be specific, measurable, and have a clear target number. Align with company goal: [COMPANY GOAL]. Include a confidence rating (30/50/70 percent) for each KR.
Build a quarterly plan for [TEAM/DEPARTMENT] for [QUARTER]. Include: (1) Top 3-5 priorities aligned to [COMPANY GOALS], (2) Key deliverables with owners and deadlines, (3) Dependencies on other teams, (4) Resource requirements, (5) Risks and contingencies, (6) Success metrics, (7) Review cadence. Format as a one-page plan the team can reference daily.
Structure a [DURATION]-hour quarterly review for [TEAM]. Agenda: results vs goals, wins, challenges, next quarter priorities, resource needs, action items. Include pre-work.
Create mitigation plans for [RISKS]. For each: description, triggers, preventive actions, contingency plan, early warnings, owner, review cadence, budget needed. Prioritise by score.
Create a risk register for [PROJECT/INITIATIVE]. Include columns: (1) Risk ID, (2) Description, (3) Category, (4) Likelihood (1-5), (5) Impact (1-5), (6) Risk score, (7) Mitigation plan, (8) Contingency plan, (9) Owner, (10) Status. Pre-populate with [NUMBER — 10 / 15] likely risks based on [PROJECT TYPE]. Sort by risk score descending.
Evaluate these strategic initiatives: [LIST INITIATIVES]. For each assess: (1) Strategic alignment score (1-10), (2) Expected impact, (3) Resource requirements, (4) Time to value, (5) Risk level, (6) Dependencies. Rank by weighted score. Present as a prioritisation matrix with a recommendation for what to pursue this [PERIOD].
Create a strategic review framework for [BUSINESS AREA] covering [PERIOD]. Include: (1) Mission and strategy recap, (2) Performance vs goals, (3) What worked and why, (4) What did not work and root causes, (5) Market and competitive changes, (6) Resource utilisation, (7) Priorities for next period, (8) Key bets and experiments to run.
Help me plan capacity for [TEAM] for [PERIOD]. We have [NUMBER] team members with these roles: [ROLES]. Available working hours: [HOURS/WEEK per person] minus meetings, admin, and leave. Map our committed projects: [LIST PROJECTS] against available capacity. Identify: over-allocation, under-allocation, and hiring needs. Present as a visual capacity chart.
Plan a [DURATION]-day team offsite for [TEAM]. Include: (1) Objectives (what we want to walk away with), (2) Agenda with session timing, (3) Strategic sessions (vision, priorities, OKRs), (4) Team building activities, (5) Working sessions with clear outputs, (6) Social programme, (7) Pre-work for participants, (8) Follow-up actions framework.
▸
Team Retrospective Facilitator
Run a structured team retrospective with actionable outcomes
IntermediateFacilitate a retrospective for [TEAM] covering [PERIOD/SPRINT]. Structure: (1) Set the stage with a one-word check-in, (2) Gather data in three columns (What went well, What to improve, Ideas to try), (3) Group themes and vote on top 3, (4) Define specific actions for each with owner and deadline, (5) Review actions from last retro — were they completed? End on a positive note.
🛡️ Cybersecurity
▸
Cybersecurity Risk Register
Build a risk register for tracking and managing security risks
IntermediateCreate a cybersecurity risk register for [ORGANISATION/PROJECT]. Include columns: (1) Risk ID, (2) Risk description, (3) Category (technical, human, process), (4) Likelihood (1-5), (5) Impact (1-5), (6) Risk score, (7) Current controls, (8) Residual risk, (9) Treatment plan, (10) Owner, (11) Review date. Pre-populate with the top 10 common risks for [INDUSTRY].
▸
Data Breach Notification Draft
Draft internal and external breach notification communications
AdvancedDraft breach notification communications for a [BREACH TYPE — data leak / unauthorized access / ransomware] affecting [NUMBER] records. Create: (1) Internal notification to leadership (immediate), (2) Employee communication (within 24 hours), (3) Customer notification (compliant with [REGULATION — GDPR / Privacy Act / state law]), (4) Media statement (if needed). Each communication should be factual, empathetic, and include next steps.
Draft an incident response plan for [INCIDENT TYPE — ransomware / data breach / phishing compromise / account takeover]. Include: (1) Detection indicators, (2) Immediate containment steps, (3) Eradication procedures, (4) Recovery timeline, (5) Communication plan (internal and external), (6) Post-incident review process, (7) Roles and responsibilities matrix.
▸
MFA Rollout Communication Plan
Create a communication plan for rolling out multi-factor authentication
IntermediateCreate a communication plan for rolling out MFA to [NUMBER] users over [TIMEFRAME]. Include: (1) Executive announcement email, (2) Step-by-step setup guide for users, (3) FAQ addressing common concerns, (4) Support escalation path, (5) Timeline with pilot group and full rollout dates, (6) Follow-up email for non-compliant users. Tone: supportive, not threatening.
Create phishing awareness training content for [AUDIENCE — all staff / IT team / executives]. Include: (1) What phishing is and why it matters (with stats), (2) 5 real-world phishing examples with red flags highlighted, (3) How to identify suspicious emails (checklist), (4) What to do if you click a link, (5) Quiz questions to test understanding. Tone: engaging, not condescending.
Create a [NUMBER — 10 / 15 / 20]-question security awareness quiz for [AUDIENCE — all employees / IT staff / managers]. Mix: (1) Multiple choice, (2) True/false, (3) Scenario-based questions. Cover: phishing, password hygiene, social engineering, data handling, physical security, and reporting procedures. Include answer key with explanations.
Design a security metrics dashboard. Include: Secure Score trend, incident count, vulnerability remediation, phishing results, compliance status, top risks, investment ROI.
Create security onboarding content. Cover: policies summary, password and MFA setup, spotting phishing, data classification, acceptable use, reporting incidents, quiz.
Draft an information security policy for [POLICY AREA — acceptable use / remote work / BYOD / data classification / password / incident reporting]. Include: (1) Purpose and scope, (2) Policy statements with clear rules, (3) User responsibilities, (4) Monitoring and enforcement, (5) Exceptions process, (6) Compliance requirements referenced. Write for a non-technical audience.
Design a tabletop exercise for [SCENARIO]. Include: narrative with escalating phases, inject cards, discussion questions, roles to test, evaluation criteria, facilitation guide, post-exercise report template. Duration: [HOURS].
Create a threat assessment for [ORGANISATION TYPE — SMB / enterprise / government]. Cover: (1) Top 5 threats for our industry in [YEAR], (2) Likelihood and impact rating for each, (3) Current controls we likely have, (4) Gaps and recommended mitigations, (5) Priority actions ranked by risk reduction per effort. Present as an executive summary with a risk matrix.
Create a user access review template for [SYSTEM/APPLICATION]. Include: (1) All user accounts with their roles and permissions, (2) Last login date, (3) Business justification for access, (4) Manager approval column, (5) Actions needed (keep, reduce, remove), (6) Compliance evidence trail. Flag accounts with: no login in 90 days, excessive permissions, or no manager assigned.
Summarise this vulnerability scan report for [AUDIENCE — CISO / IT leadership / board]. Include: (1) Total vulnerabilities by severity (critical, high, medium, low), (2) Top 5 critical findings with business impact, (3) Trend vs previous scan, (4) Remediation priority list with effort estimates, (5) Overall security posture rating. Remove technical jargon — focus on risk and business impact.
🎨 Creative & Design
Create a brand voice guide for [BRAND]. Include: (1) Brand personality traits (3-5 adjectives), (2) Voice characteristics (what we sound like), (3) Tone variations by context (social, email, support, formal), (4) Vocabulary do and don't list, (5) Example sentences showing right vs wrong, (6) Grammar and formatting preferences. Make it practical enough for any team member to follow.
Create a [TIMEFRAME — monthly / quarterly] content calendar for [BRAND/PROJECT] on [CHANNELS — blog / LinkedIn / Instagram / YouTube]. Include: (1) Weekly themes aligned to [GOALS], (2) Specific post ideas with headlines, (3) Content type (article, video, carousel, story), (4) Posting schedule by day, (5) Key dates and events to leverage. Target: [POSTS PER WEEK] posts per week.
Write a case study about [CUSTOMER/PROJECT]. Structure: (1) The Challenge — what problem they faced, (2) The Solution — what we did and how, (3) The Results — specific metrics and outcomes, (4) Quote from the customer, (5) Key takeaway. Keep it to one page. Tone: factual and credible, not salesy. Base on: [SOURCE DATA].
Write a design brief for [PROJECT — logo / website / presentation / marketing material]. Include: (1) Project overview and objectives, (2) Target audience, (3) Key message to convey, (4) Tone and style direction, (5) Must-have elements, (6) Deliverables and formats, (7) Timeline and milestones, (8) Inspiration references. Keep concise enough for a designer to act on.
Design the content for an infographic about [TOPIC]. Include: (1) Headline that grabs attention, (2) 5-7 key data points or facts, (3) Flow and visual hierarchy (top to bottom), (4) Section headings, (5) Sources for all statistics, (6) Call to action at the bottom. Keep text minimal — each section should be understood in 3 seconds.
Generate [NUMBER] name ideas for [WHAT]. Requirements: easy to pronounce, available as domain, no negative meanings, fits [BRAND] personality. Style: [STYLE]. For top 5, explain why each works.
▸
Podcast Episode Outline
Plan a podcast episode with segments, questions, and talking points
IntermediateCreate an outline for a [LENGTH — 20 / 30 / 45]-minute podcast episode about [TOPIC]. Include: (1) Cold open hook (30 seconds), (2) Introduction and context (2 minutes), (3) Main segments with talking points and transitions, (4) Guest interview questions (if applicable), (5) Key takeaways, (6) CTA and outro. Note timing for each segment.
Help me structure a presentation about [TOPIC] using storytelling. Create: (1) Opening hook that grabs attention, (2) The problem or challenge (make audience feel it), (3) The journey or approach, (4) The solution or insight, (5) Evidence and proof points, (6) The transformation or result, (7) Call to action. For each section suggest visuals and delivery notes.
Develop a campaign for [GOAL] on [PLATFORMS]. Include: campaign name, big idea, visual direction, content pillars, 5-7 post examples, engagement mechanic, metrics.
Write a script for a [LENGTH — 1 / 2 / 5]-minute video about [TOPIC] for [AUDIENCE]. Include: (1) Hook in the first 5 seconds, (2) Scene-by-scene breakdown with timing, (3) On-screen text suggestions, (4) B-roll or visual recommendations, (5) Call to action at the end. Tone: [TONE — professional / casual / energetic / educational]. Format as a two-column table (visuals | dialogue).
Design materials for [WORKSHOP]. Create: agenda poster, exercise cards, discussion prompts, feedback form, completion certificate. Consistent branding with [BRAND].
💻 Coding & Development
Generate API documentation for [API NAME]. For each endpoint include: (1) HTTP method and path, (2) Description of what it does, (3) Request parameters with types and required/optional, (4) Request body schema with examples, (5) Response schema with examples, (6) Error codes and meanings, (7) Authentication requirements. Format as Markdown.
Review this code and provide feedback on: (1) Bugs or logic errors, (2) Security vulnerabilities, (3) Performance issues, (4) Readability and naming, (5) Missing error handling, (6) Test coverage gaps. For each issue: explain the problem, show the fix, and rate severity (critical, important, minor). [PASTE CODE]
Write a migration script for [CHANGE]. Include: up migration, down migration (rollback), data preservation, validation queries, estimated execution time. Include safety checks.
Debug this error: [PASTE ERROR MESSAGE OR STACK TRACE]. (1) Explain what the error means in plain English, (2) Identify the most likely root cause, (3) Provide a fix with code, (4) Explain why the fix works, (5) Suggest how to prevent this error in the future. Language: [LANGUAGE — Python / JavaScript / C# / PowerShell].
Design error handling for [COMPONENT — API endpoint / background job / file processor / user form] in [LANGUAGE]. Include: (1) Input validation, (2) Try-catch structure, (3) Specific exception types to handle, (4) Logging strategy, (5) User-friendly error messages, (6) Retry logic for transient failures, (7) Graceful degradation. Show complete code.
▸
PowerShell Script from Description
Generate a PowerShell script from a plain English task description
IntermediateWrite a PowerShell script that [DESCRIBE TASK — e.g. finds all inactive users in Entra ID who have not signed in for 90 days and exports them to CSV]. Include: (1) Required modules and permissions, (2) Parameter block with defaults, (3) Error handling with try-catch, (4) Progress output, (5) CSV or report output, (6) Comments explaining each section. Target: PowerShell 7+.
Generate a README.md for [PROJECT NAME]. Include: (1) Project description and purpose, (2) Features list, (3) Quick start guide with installation steps, (4) Usage examples with code snippets, (5) Configuration options, (6) Contributing guidelines, (7) License information, (8) Badge suggestions (build status, coverage, version). Based on: [DESCRIBE THE PROJECT].
Analyse this code and suggest refactoring improvements: [PASTE CODE]. Focus on: (1) Reducing complexity, (2) Removing duplication, (3) Improving naming, (4) Applying [PATTERN — SOLID principles / DRY / design patterns], (5) Breaking large functions into smaller ones. Show before and after code for each suggestion.
Build a regex pattern that matches [DESCRIBE WHAT YOU NEED — e.g. email addresses / phone numbers / dates in DD/MM/YYYY format / URLs]. Provide: (1) The regex pattern, (2) A plain English explanation of each part, (3) Test cases that should match, (4) Test cases that should NOT match, (5) Any edge cases to watch for. Language: [LANGUAGE].
Design a REST API for [PURPOSE]. Include: resource naming, endpoints with methods, request/response schemas, authentication, errors, pagination, rate limiting, versioning.
Write a SQL query that [DESCRIBE WHAT YOU NEED — e.g. finds all customers who ordered more than 3 times in the last month but have not ordered in the last 7 days]. Database: [TYPE — SQL Server / PostgreSQL / MySQL]. Tables: [LIST TABLE NAMES AND KEY COLUMNS]. Include: the query, explanation of each clause, and performance considerations.
Write unit tests for this [LANGUAGE] code: [PASTE CODE]. Include: (1) Happy path tests, (2) Edge cases (null, empty, boundary values), (3) Error handling tests, (4) Tests for each public method. Use [FRAMEWORK — Jest / pytest / xUnit / NUnit]. Include descriptive test names that explain what is being tested.
🎓 Training & Learning
▸
Certification Study Plan
Create a structured study plan for a professional certification
IntermediateCreate a study plan for [CERTIFICATION — AZ-900 / PMP / CISSP / AWS]. Include: (1) Exam overview and passing score, (2) Weekly study schedule for [WEEKS] weeks, (3) Topics by priority and weight, (4) Resources (official study guide, practice tests, videos), (5) Practice test strategy, (6) Exam day tips. Based on [AVAILABLE HOURS] study hours per week.
Create a study plan for [CERTIFICATION]. Include: exam overview, weekly schedule for [WEEKS], topics by weight, resources, practice test strategy, exam day tips.
Build a competency framework for [ROLE]. For each: name, definition, behavioural indicators at 4 levels, assessment methods, development resources. Cover 8-12 competencies.
Design a course outline for [TOPIC] targeting [AUDIENCE — beginners / intermediate / advanced]. Include: (1) Learning objectives (3-5), (2) Module breakdown with topics and duration, (3) Key concepts per module, (4) Hands-on exercises or activities, (5) Assessment methods, (6) Prerequisites, (7) Recommended resources. Total duration: [HOURS] hours.
Design a learning path for someone wanting to learn [SKILL/TOPIC] from [CURRENT LEVEL — beginner / some experience] to [TARGET LEVEL — competent / expert]. Include: (1) Phases with clear milestones, (2) Resources for each phase (courses, books, practice), (3) Estimated time per phase, (4) Projects to build at each stage, (5) How to measure progress, (6) Common pitfalls to avoid.
Plan a [DURATION — 30 / 45]-minute lunch and learn on [TOPIC] for [AUDIENCE]. Include: (1) Catchy title and promotion blurb, (2) Learning objectives (2-3), (3) Agenda with timing, (4) Interactive element (demo, poll, Q&A), (5) Key takeaways (3 max), (6) Resources for further learning. Keep it informal and engaging — people are giving up their lunch break.
Create [NUMBER — 5 / 10] microlearning modules on [TOPIC]. Each module should: (1) Take under 5 minutes to complete, (2) Cover exactly one concept, (3) Include a real-world example, (4) End with one action the learner can try immediately, (5) Include a one-question check. Format for delivery via email, Teams message, or learning platform.
Create a training curriculum for new [ROLE] hires at [COMPANY/TEAM]. Cover weeks 1-4: (1) Week 1: Company orientation, tools, and culture, (2) Week 2: Role-specific training and shadowing, (3) Week 3: Guided practice with mentor support, (4) Week 4: Independent work with daily check-ins. For each week include: learning goals, activities, resources, and success criteria.
Design a peer learning programme. Include: structure, topic selection, session format, facilitator rotation, knowledge capture, recognition, success metrics.
Create a 5-minute knowledge check on [TOPIC] that a manager can run during a team meeting. Include: (1) 5 quick-fire questions (30 seconds each), (2) Answer reveals with brief explanations, (3) A bonus challenge question for experts, (4) Key takeaway to reinforce. Format for verbal delivery — no written test needed.
Conduct a skill gap analysis for [TEAM]. Steps: (1) List required skills for the team's goals, (2) Rate current team capability (1-5) for each skill, (3) Identify gaps (required vs current), (4) Prioritise gaps by business impact, (5) Recommend development actions for each (training, hiring, mentoring). Present as a gap analysis matrix.
Conduct a skill gap analysis. List required skills, rate current capability 1-5, identify gaps, prioritise by impact, recommend development actions per gap.
Create a post-training feedback survey for [TRAINING NAME]. Include: (1) 3-4 rating questions (content relevance, delivery quality, practical value), (2) 2 open-ended questions (best part, what to improve), (3) Net Promoter Score question, (4) One question about confidence to apply what was learned, (5) Suggestions for future topics. Keep it under 3 minutes to complete.
Create a [NUMBER — 10 / 15 / 20]-question quiz for [TRAINING TOPIC]. Include: (1) Mix of question types (multiple choice, true/false, scenario-based), (2) Questions at different Bloom taxonomy levels (remember, understand, apply, analyse), (3) Answer key with explanations for wrong answers, (4) Passing score recommendation. Difficulty: [LEVEL].
Create [NUMBER] role-play scenarios for practicing [SKILL]. Each: (1) Situation setup, (2) Character briefs for participants, (3) Hidden objectives, (4) Evaluation criteria, (5) Debrief questions. Increase difficulty progressively.
Create a facilitator guide for a [DURATION]-hour workshop on [TOPIC]. Include: (1) Room setup and materials needed, (2) Minute-by-minute agenda, (3) Facilitator scripts for key moments, (4) Discussion questions with expected responses, (5) Activity instructions with timing, (6) Troubleshooting tips for common issues, (7) Wrap-up and evaluation.
⏱️ Productivity & Focus
Help me set goals for [YEAR]. Role: [ROLE]. Priorities: [LIST]. Create: (1) 3-5 SMART goals, (2) Quarterly milestones, (3) Supporting habits, (4) Obstacles and mitigation, (5) Tracking plan. Balance development with deliverables.
Analyse my day: [DESCRIBE]. Identify: context switch count, cost per switch (23 min), total lost time, avoidable switches, batching strategy, redesigned schedule.
▸
Decision Journal Entry
Document a decision with context and reasoning for future reference
IntermediateHelp me document this decision for my decision journal. Decision: [WHAT I DECIDED]. Create an entry with: (1) The decision and date, (2) Context and constraints at the time, (3) Options I considered, (4) Why I chose this option, (5) What I expect to happen, (6) How I will know if it was the right call, (7) Review date to assess the outcome.
Help me plan a deep work session to accomplish [TASK]. Duration: [HOURS] hours. Create: (1) Pre-session setup checklist (notifications off, materials ready), (2) Session structure with breaks (Pomodoro or custom), (3) Specific milestones to hit during the session, (4) Definition of done for this session, (5) Post-session review questions. What to have ready before starting.
Plan a deep work session for [TASK]. Duration: [HOURS]. Include: pre-session setup, session structure with breaks, milestones, definition of done, post-session review.
Help me decide what to delegate from my current task list: [LIST TASKS]. For each task evaluate: (1) Must I personally do this? Why?, (2) Who on my team could do this?, (3) What support or authority would they need?, (4) What does a successful handoff look like? Create delegation briefs for the top [NUMBER — 3 / 5] tasks I should hand off.
Organise my task list into an Eisenhower matrix: [LIST ALL TASKS]. Categorise each as: (1) Urgent + Important → Do now, (2) Important + Not Urgent → Schedule, (3) Urgent + Not Important → Delegate, (4) Not Urgent + Not Important → Eliminate. For the Do Now quadrant, suggest an order based on deadlines and dependencies.
Help me design my ideal work day based on my energy patterns. I am most alert at [PEAK TIME] and lowest energy at [LOW TIME]. My typical meetings are at [MEETING TIMES]. Design: (1) When to do deep/creative work, (2) When to do admin/email, (3) When to schedule meetings, (4) Break timing, (5) Exercise or movement blocks, (6) End-of-day wind-down routine.
Design my ideal day based on energy. Peak at [TIME], low at [TIME]. Assign: deep work, admin, meetings, breaks, exercise, wind-down. Optimise for performance.
Create a personalised inbox management strategy for me. I receive approximately [NUMBER] emails per day. My biggest email challenges: [CHALLENGES]. Design: (1) Rules for what to respond to immediately vs batch, (2) Folder or label structure, (3) Templates for common responses, (4) Daily email processing schedule, (5) Rules I can automate. Goal: process all email in under [TIME] minutes per day.
Audit my calendar for the past [WEEKS — 2 / 4] weeks. Categorise each recurring meeting as: (1) Essential — I must attend, (2) Optional — I could send a delegate or read notes, (3) Redundant — overlaps with another meeting, (4) Unnecessary — should be an email. For each non-essential meeting, draft a polite opt-out message or suggest a shorter format. Calculate hours I could reclaim per week.
Design a morning routine for a [ROLE] who starts work at [TIME]. Include: (1) Pre-work ritual (15 min), (2) Planning block (10 min — review calendar, set daily top 3), (3) Deep work block (60-90 min on most important task), (4) Communication check (15 min — email and Teams triage), (5) First meeting prep. Base on research about peak productivity times.
Help me plan my week. My priorities are: [LIST TOP PRIORITIES]. My meetings this week: [KEY MEETINGS]. My deadlines: [DEADLINES]. Create: (1) Top 3 outcomes to achieve by Friday, (2) Daily focus blocks (what to work on each day), (3) Meetings I should prepare for, (4) Tasks I should delegate or defer, (5) One thing to learn or improve this week. Keep realistic with 6 productive hours per day.
📱 Social Media
Create a community engagement playbook for [BRAND/COMMUNITY] on [PLATFORM]. Include: (1) Community guidelines, (2) Daily engagement routine (respond, initiate, amplify), (3) Content that sparks discussion, (4) How to handle negative comments, (5) Member recognition programme, (6) Growth targets and metrics, (7) Crisis response for community issues.
Repurpose this content into social media posts: [PASTE OR DESCRIBE CONTENT — blog post / presentation / webinar / report]. Create: (1) 3 LinkedIn posts (different angles), (2) 5 Twitter/X posts (key quotes and stats), (3) 2 Instagram carousel ideas, (4) 1 short video script (60 seconds). Each should drive back to the original content.
Research and recommend a hashtag strategy for my [PLATFORM] content about [TOPIC/NICHE]. Provide: (1) 5 high-volume hashtags for reach, (2) 5 medium-volume for relevance, (3) 5 niche hashtags for community, (4) 3 branded hashtags to create, (5) Hashtags to avoid (overused or spammy). Include estimated reach for each tier.
▸
LinkedIn Profile Optimiser
Improve your LinkedIn profile for discoverability and credibility
BeginnerReview and improve my LinkedIn profile for [GOAL — job search / thought leadership / business development / networking]. Rewrite: (1) Headline (under 120 chars, keyword-rich), (2) About section (hook, story, value, CTA), (3) Experience descriptions (achievement-focused, not duty-focused), (4) Skills to add or remove, (5) Recommendations to request. Current profile: [PASTE CURRENT CONTENT].
▸
LinkedIn Thought Leadership Post
Write a LinkedIn post that drives engagement and builds authority
BeginnerWrite a LinkedIn post about [TOPIC] for my audience of [AUDIENCE — IT professionals / business leaders / tech community]. Structure: (1) Bold opening line (hook), (2) Personal insight or experience (3-4 sentences), (3) Practical takeaway or framework, (4) Call to engagement (question or invitation to share). Under 200 words. Include relevant hashtag suggestions.
Create a social media coverage plan for [EVENT NAME] on [DATE]. Include: (1) Pre-event teaser posts (1 week before), (2) Day-of posting schedule with templates for key moments, (3) Live-posting guidelines (what to capture, format, hashtags), (4) Post-event summary thread, (5) Follow-up engagement plan. Platform: [PLATFORM]. Include a shot list for photos.
Generate [NUMBER — 10 / 15] short-form video ideas for [TOPIC/NICHE] on [PLATFORM — TikTok / Reels / Shorts]. For each: (1) Concept in one sentence, (2) Hook (first 3 seconds), (3) Format (tutorial / story / reaction / tips), (4) Length (15s / 30s / 60s), (5) Trending audio or style to leverage. Focus on ideas that showcase expertise without being boring.
Generate [NUMBER] short-form video ideas for [NICHE] on [PLATFORM]. Each: concept, hook (first 3 seconds), format, length, trending style. Showcase expertise engagingly.
▸
Social Media Performance Review
Analyse social media metrics and recommend improvements
IntermediateAnalyse these social media metrics for [PERIOD]: [PASTE METRICS — followers, impressions, engagement rate, top posts]. Provide: (1) Performance summary vs previous period, (2) Top 3 performing posts and why they worked, (3) Bottom 3 and what to learn, (4) Audience growth analysis, (5) Recommendations for next period (content types, posting times, topics). Present as an executive summary.
Create a [NUMBER — 5 / 7]-post series about [TOPIC] for [PLATFORM — LinkedIn / Twitter / Instagram]. Each post should: (1) Build on the previous one, (2) Work standalone if someone only sees one, (3) Include a hook, core message, and CTA, (4) Use platform-appropriate format and length. Include a series title and posting schedule.
Build a thought leadership plan for [TOPIC/NICHE] on [PLATFORM]. Include: (1) Positioning statement (what I am known for), (2) Content pillars (3-4 themes), (3) Weekly posting cadence, (4) Content mix (original, curated, engagement), (5) Growth tactics, (6) 90-day content calendar with post ideas, (7) Metrics to track.
Help me write thoughtful replies to these comments on my [PLATFORM] post about [TOPIC]: [PASTE COMMENTS]. For each reply: (1) Acknowledge their point specifically, (2) Add value with an insight or resource, (3) Ask a follow-up question to continue the conversation. Never be generic — each reply should show I actually read their comment.
Generate [NUMBER — 10 / 15] scroll-stopping opening hooks for posts about [TOPIC]. Types: (1) Contrarian opinion, (2) Surprising statistic, (3) Personal story starter, (4) Question that makes people think, (5) Bold prediction. Each hook should make someone stop scrolling in under 2 seconds.
⚖️ Legal & Compliance
Summarise this AUP into a one-page guide: what you CAN do, what you CANNOT do, grey areas, monitoring notice, consequences, how to report. Understandable in 3 minutes.
▸
Compliance Checklist Generator
Create a compliance checklist for a regulation or standard
IntermediateCreate a compliance checklist for [REGULATION — GDPR / SOC2 / ISO 27001 / HIPAA / PCI-DSS / Essential Eight]. Include: (1) Requirement description, (2) Evidence needed, (3) Current status (compliant, partial, gap), (4) Owner, (5) Remediation steps for gaps, (6) Review frequency. Focus on requirements relevant to [ORGANISATION TYPE]. Pre-populate status as Not Assessed.
Review this contract and provide: (1) Summary of key terms (parties, scope, duration, value), (2) Obligations for each party, (3) Termination conditions, (4) Liability and indemnification clauses, (5) Payment terms, (6) Renewal or auto-renewal provisions, (7) Red flags or unusual clauses, (8) Missing clauses that should be included. Note: this is for initial review — legal counsel should approve.
Review this DPA: (1) Data processed, (2) Purposes, (3) Controller vs processor duties, (4) Sub-processors, (5) Cross-border transfers, (6) Breach notification timeframes, (7) Audit rights, (8) Data return on termination. Flag deviations from standard clauses.
Review this DPA: data processed, purposes, controller vs processor, sub-processors, cross-border transfers, breach notification, audit rights, data return. Flag deviations.
Review this agreement for IP provisions: (1) Who owns work product, (2) Background IP treatment, (3) Licence grants, (4) Assignment of rights, (5) Third-party IP usage, (6) Open source obligations, (7) Moral rights waiver, (8) IP warranties. Flag any provisions that limit our ownership of deliverables.
Review IP provisions: who owns work product, background IP, licence grants, assignment rights, third-party IP, open source, moral rights, warranties. Flag ownership limitations.
Prepare a legal brief for [INCIDENT TYPE — data breach / unauthorized access / compliance violation]. Include: (1) Factual summary of what occurred, (2) Data types and individuals affected, (3) Applicable regulations and notification requirements, (4) Timeline of required actions (notification deadlines), (5) Potential legal exposure, (6) Recommended immediate legal steps. This is for internal counsel preparation.
Summarise this NDA highlighting: (1) What is considered confidential, (2) What is excluded, (3) Duration of confidentiality obligations, (4) Permitted disclosures, (5) Return or destruction of information requirements, (6) Which party has more restrictive obligations, (7) Governing law. Flag anything unusual or one-sided. Note: for awareness only — consult legal for binding advice.
Compare these two versions of [POLICY NAME] and provide: (1) Summary of all changes (additions, removals, modifications), (2) Impact assessment of each change on [STAKEHOLDERS], (3) Changes that increase obligations or restrictions, (4) Changes that relax requirements, (5) Recommended questions to ask the policy owner. Present as a change log table.
Draft a privacy notice for [PRODUCT/SERVICE/WEBSITE]. Cover: (1) What data we collect, (2) How we use it, (3) Legal basis for processing, (4) Data sharing and third parties, (5) Data retention periods, (6) User rights (access, deletion, portability), (7) Cookie usage, (8) Contact details for privacy queries. Comply with: [REGULATION — GDPR / Privacy Act / CCPA]. Use plain language.
Summarise the ToS for [TOOL/SERVICE] focusing on: (1) Data ownership, (2) How they use our data, (3) Liability limits, (4) Termination and data portability, (5) Acceptable use, (6) SLA commitments, (7) Price change provisions, (8) Red flags for enterprise use. Keep under one page.
Summarise the terms of service for [TOOL/SERVICE] focusing on: (1) Data ownership and intellectual property, (2) How they use our data, (3) Liability limitations, (4) Termination and data portability, (5) Acceptable use restrictions, (6) SLA and uptime commitments, (7) Price change provisions, (8) Red flags for enterprise use. Keep it under one page.
Conduct a vendor risk assessment for [VENDOR NAME] providing [SERVICE]. Evaluate: (1) Data they will access or process, (2) Security certifications (SOC2, ISO 27001), (3) Data processing agreement status, (4) Sub-processor disclosure, (5) Incident notification obligations, (6) Insurance coverage, (7) Geographic data residency, (8) Exit strategy and data return. Rate overall risk as Low/Medium/High.
🚀 Onboarding & Change Management
Design an adoption tracking framework for [TOOL/SYSTEM]. Include: (1) Key metrics to track (active users, feature usage, support tickets), (2) Targets for 30/60/90 days, (3) Dashboard layout with visualisations, (4) Data sources for each metric, (5) Alert thresholds (when adoption is below target), (6) Actions to take when metrics are low. Present as a one-page dashboard spec.
Design adoption tracking for [TOOL]. Include: metrics (active users, feature usage, tickets), 30/60/90 targets, dashboard layout, data sources, alert thresholds, low-adoption actions.
Design a change champion programme for [CHANGE/TOOL] rollout. Include: (1) Champion role description and time commitment, (2) Selection criteria and recruitment message, (3) Training plan for champions, (4) Communication toolkit (templates, talking points, FAQ), (5) Recognition and incentive programme, (6) Reporting cadence and feedback loop. Target: [NUMBER] champions across [DEPARTMENTS].
Create a change readiness assessment for [CHANGE — new system / reorganisation / process change]. Include: (1) 10 assessment questions covering awareness, desire, knowledge, ability, and reinforcement (ADKAR), (2) Rating scale, (3) Scoring guide, (4) Risk areas based on scores, (5) Recommended actions for each risk area. Format as a survey the change team can distribute.
Create a guide for handling resistance to [CHANGE]. Address these common objections: (1) We have always done it this way, (2) This is going to make my job harder, (3) Nobody asked us about this, (4) The old system worked fine, (5) I do not have time to learn something new. For each: empathise, reframe, provide evidence, and offer support. Include escalation paths for persistent resistance.
Create a culture guide covering unwritten rules: how we communicate, meeting norms, work-life balance, decision making, social traditions, acronyms, who to ask for what.
Design feedback collection: Day 1 pulse check, Week 1 survey, 30-day check-in guide, 60-day survey, 90-day review. Track satisfaction, time-to-productivity, buddy effectiveness.
Write a welcome email for [NEW HIRE NAME] joining as [ROLE] on [DATE]. Include: (1) Warm personal welcome from [MANAGER NAME], (2) What to expect on day 1 (time, location, who to ask for), (3) First week overview, (4) Key contacts and their roles, (5) Links to essential resources, (6) Something fun or personal about the team. Tone: excited, supportive, and helpful.
▸
New Tool Rollout Plan
Create a communication and training plan for rolling out a new tool
IntermediateCreate a rollout plan for [NEW TOOL] being deployed to [NUMBER] users over [TIMEFRAME]. Include: (1) Pre-launch communication series (3 emails), (2) Training options (self-service guide, live session, video), (3) Pilot group selection and feedback process, (4) Full rollout phases, (5) Support plan and FAQ, (6) Success metrics and adoption targets, (7) Post-rollout feedback survey.
Create an onboarding buddy guide for someone helping [NEW HIRE ROLE] settle in. Include: (1) Your role as a buddy (expectations and time commitment), (2) Week-by-week checklist of things to show and share, (3) Common new hire questions and answers, (4) Cultural norms and unwritten rules, (5) Red flags that the new hire might be struggling, (6) How to hand off when buddying period ends.
Create a role transition checklist for [PERSON] moving from [OLD ROLE] to [NEW ROLE]. Include: (1) Knowledge transfer items from old role, (2) Handoff documents and contacts, (3) New role orientation and expectations, (4) Training and skill gaps to address, (5) Key stakeholder introductions, (6) 30-day milestones in the new role, (7) Support contacts. Both the leaver and the successor should use this.
Create a tech guide for new hires. Cover: communication tools, productivity tools, department tools, getting help, security essentials, efficiency tips. Include setup links.
No prompts match your filters. Try clearing a filter or different search terms.
Frequently Asked Questions
1. What AI platforms do these prompts work with?
Most prompts work across all major AI platforms including Microsoft 365 Copilot, ChatGPT, Claude, Gemini, and Perplexity. Each prompt shows which platforms it's optimised for, with a star on the best match.
2. Can I customize the prompts with my own details?
Yes! Prompts with [PLACEHOLDER] variables show a Customize button. Click it to fill in your specific details — like your role, topic, and audience — and get a ready-to-paste personalized prompt.
3. How do I save my favorite prompts?
Click the star icon on any prompt to save it to your My Prompts collection. Your favorites are stored in your browser and available whenever you return. You can also export them as a Markdown file.
4. Can I modify the prompts?
Absolutely! These prompts are starting points. Use the Customize wizard for variable prompts, or copy and edit freely. Use our Prompt Polisher tool to score and improve any prompt.
5. How often are new prompts added?
We regularly add new prompts based on community feedback and new AI platform capabilities. Check the Prompt of the Day for daily inspiration, or subscribe to our RSS feed.
6. Are the prompts free to use?
Yes, all prompts are completely free. No sign-up, no account, no limits. Copy and use them anywhere.
7. What is Prompt of the Day?
Every day, we highlight a different prompt from the library. It's a great way to discover prompts you might not have tried yet. The selection changes automatically at midnight.
8. Is this tool still being improved?
Yes! We're actively adding new prompts, categories, and features based on community feedback. Share your ideas on our feedback page.
Your Prompt Engineering Toolkit
💬 Got feedback? Share it here →