[{"id":1,"title":"E commerce Damaged Product Complaint Resolution","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Create a customer-first damaged product complaint resolution template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"E commerce Damaged Product Complaint Resolution\"\n\nStarting brief:\nYou are a customer experience copywriter. Draft a damaged product complaint resolution email template for e-commerce.\n\nBusiness context:\nA 29-year-old complaint manager at a Singapore-based e-commerce platform headquartered in one-north deals with daily customer grievances about damaged products. Customers often feel unheard because responses sound generic. She wants a personalized, empathetic, and solution-oriented template that acknowledges the issue, explains next steps, and offers clear resolution timelines.\n\nDesired outcome:\nCreate a customer-first damaged product complaint resolution template.\n\nMy details:\n- E commerce Damaged Product Complaint Resolution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Return/replacement policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":2,"title":"Banking Fraud Dispute Resolution","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Advanced","explanation":"Develop a banking fraud complaint resolution template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Banking Fraud Dispute Resolution\"\n\nStarting brief:\nYou are a financial compliance communications expert. Write a customer letter/email template for resolving fraud transaction disputes.\n\nBusiness context:\nA 34-year-old branch operations head at a Singapore retail bank in the CBD needs a template to address fraud-related complaints. Customers are often stressed and worried about losing money, so communication must be clear, calming, and reassuring, while also meeting MAS compliance standards.\n\nDesired outcome:\nDevelop a banking fraud complaint resolution template.\n\nMy details:\n- Banking Fraud Dispute Resolution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Fraud investigation process details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":3,"title":"Telecom Network Issue Complaint Resolution","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Create a network issue complaint resolution template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Telecom Network Issue Complaint Resolution\"\n\nStarting brief:\nYou are a telecom customer relations content creator. Draft a complaint resolution message for poor network coverage.\n\nBusiness context:\nA 26-year-old customer care lead at a Singapore telecom operator headquartered in Paya Lebar is overwhelmed with repetitive complaints about poor network connectivity in certain estates. She wants a template that not only acknowledges the complaint but also gives transparent updates on network maintenance and improvement plans.\n\nDesired outcome:\nCreate a network issue complaint resolution template.\n\nMy details:\n- Telecom Network Issue Complaint Resolution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Network maintenance schedule\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":4,"title":"Airline Flight Delay Compensation Response","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Advanced","explanation":"Build a customer-centric flight delay complaint resolution template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Airline Flight Delay Compensation Response\"\n\nStarting brief:\nYou are an airline customer communication specialist. Create a flight delay complaint resolution template.\n\nBusiness context:\nA 31-year-old guest relations officer at a low-cost carrier based at Changi Airport receives angry emails daily from passengers affected by delays. The airline needs a standardized yet personalized template to handle these complaints with empathy, transparency, and clear details on compensation or rebooking.\n\nDesired outcome:\nBuild a customer-centric flight delay complaint resolution template.\n\nMy details:\n- Airline Flight Delay Compensation Response details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Airline compensation policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":5,"title":"Restaurant Wrong Order Complaint Handling","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Design a wrong order complaint resolution template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Restaurant Wrong Order Complaint Handling\"\n\nStarting brief:\nYou are a hospitality customer service expert. Write a wrong order complaint response template.\n\nBusiness context:\nA 24-year-old outlet manager at a popular quick-service restaurant chain in Tampines deals with daily wrong order complaints from GrabFood and foodpanda. She wants a quick-response template that apologizes, fixes the issue, and turns the negative experience into a positive one for the customer.\n\nDesired outcome:\nDesign a wrong order complaint resolution template.\n\nMy details:\n- Restaurant Wrong Order Complaint Handling details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Replacement/refund process\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":6,"title":"Hospital Billing Error Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Create a hospital billing error complaint resolution template that reassures patients, explains the correction process, and offers a clear resolution timeline. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Hospital Billing Error Complaint\"\n\nStarting brief:\nYou are a healthcare communication expert. Write a hospital billing error resolution template that includes:\n\nBusiness context:\nIn a large private hospital in Singapore's Novena medical hub, a 33-year-old patient relations executive often deals with tense situations when patients or their families discover unexpected charges on their medical bills. Many patients are already under emotional strain due to health concerns, so even a minor billing discrepancy feels like a major injustice. These disputes can quickly escalate to social media complaints or legal notices if not handled with utmost care. The hospital's reputation depends on...\n\nDesired outcome:\nCreate a hospital billing error complaint resolution template that reassures patients, explains the correction process, and offers a clear resolution timeline.\n\nMy details:\n- Hospital Billing Error Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Billing correction SOP\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":7,"title":"Hotel Room Cleanliness Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Develop a room cleanliness complaint resolution template that combines apology, action, and compensation in a premium hospitality tone. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Hotel Room Cleanliness Complaint\"\n\nStarting brief:\nYou are a hospitality service expert. Draft a complaint resolution email/message for hotel room cleanliness issues that includes:\n\nBusiness context:\nA 28-year-old guest relations manager at a luxury Marina Bay hotel faces a rare but high-impact problem: a guest checking into a room that hasn't met the highest cleanliness standards. In the luxury segment, even a speck of dust can damage brand reputation and lead to negative reviews. When such complaints arise, they must be addressed within minutes, not hours. The tone must convey sincerity, offer an immediate solution, and provide a gesture of goodwill to restore the guest's confidence.\n\nDesired outcome:\nDevelop a room cleanliness complaint resolution template that combines apology, action, and compensation in a premium hospitality tone.\n\nMy details:\n- Hotel Room Cleanliness Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Housekeeping emergency cleaning procedure\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":8,"title":"Online Course Content Error Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Create a course content error complaint resolution template for an edtech platform. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Online Course Content Error Complaint\"\n\nStarting brief:\nYou are an edtech communications specialist. Create a complaint resolution template for course content errors that includes:\n\nBusiness context:\nIn a competitive edtech startup based in one-north, a 27-year-old course manager receives a complaint from a student who found incorrect data in a lesson video. The student is preparing for A-Level examinations and depends on accurate information to succeed. If not addressed quickly, such errors can erode trust across hundreds of learners. The resolution must show that the platform values student feedback, fixes errors fast, and rewards those who help maintain quality.\n\nDesired outcome:\nCreate a course content error complaint resolution template for an edtech platform.\n\nMy details:\n- Online Course Content Error Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Content update workflow\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":9,"title":"Ride Hailing Driver Misconduct Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Design a driver misconduct complaint resolution template that prioritises passenger safety and transparency. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Ride Hailing Driver Misconduct Complaint\"\n\nStarting brief:\nYou are a transportation safety communications officer. Write a resolution template for driver misconduct complaints that includes:\n\nBusiness context:\nAt a ride-hailing company headquartered in Singapore, a 25-year-old safety operations executive receives a complaint from a passenger about aggressive driving and rude behavior from a driver. Such incidents not only risk passenger safety but also the company's public image if shared online. The complaint must be acknowledged within hours, with an assurance that the matter is taken seriously. Temporary actions such as driver suspension during investigation show commitment to safety.\n\nDesired outcome:\nDesign a driver misconduct complaint resolution template that prioritises passenger safety and transparency.\n\nMy details:\n- Ride Hailing Driver Misconduct Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Investigation protocol\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":10,"title":"Gym Membership Overcharge Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Create a gym membership overcharge complaint resolution template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Gym Membership Overcharge Complaint\"\n\nStarting brief:\nYou are a fitness industry service expert. Draft a resolution template for overcharged membership fees that includes:\n\nBusiness context:\nIn a popular fitness chain with outlets across Singapore, a 30-year-old branch manager at the Orchard outlet deals with members who have been overcharged due to a software glitch in the automated GIRO payment system. While the error is unintentional, customers feel cheated when unexpected charges appear on their bank statement. The resolution must be fast, polite, and structured to both refund the amount and prevent future errors. Adding a goodwill gesture can help retain members.\n\nDesired outcome:\nCreate a gym membership overcharge complaint resolution template.\n\nMy details:\n- Gym Membership Overcharge Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Refund process details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":11,"title":"Airline Lost Baggage Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Develop a lost baggage complaint resolution template for airlines that restores passenger trust and outlines a clear recovery process. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Airline Lost Baggage Complaint\"\n\nStarting brief:\nYou are an airline customer service expert. Create a lost baggage resolution template that includes:\n\nBusiness context:\nA 29-year-old ground services manager at Changi Airport faces an urgent complaint from a passenger who has just landed from Dubai and found their checked-in baggage missing. The passenger is visibly stressed, as the bag contains work documents and personal valuables. Lost baggage complaints are time-sensitive and emotionally charged, and a poor response can easily spiral into viral social media outrage. The template must convey urgency, accountability, and confidence in the resolution process.\n\nDesired outcome:\nDevelop a lost baggage complaint resolution template for airlines that restores passenger trust and outlines a clear recovery process.\n\nMy details:\n- Airline Lost Baggage Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Baggage tracking SOP\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":12,"title":"E commerce Late Delivery Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Create a late delivery complaint resolution template for e-commerce businesses. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"E commerce Late Delivery Complaint\"\n\nStarting brief:\nYou are an e-commerce customer care strategist. Draft a late delivery resolution template that includes:\n\nBusiness context:\nAt a fast-growing Singapore e-commerce company headquartered in Tuas, a 26-year-old logistics coordinator handles complaints from customers who didn't receive their orders on the promised date. Delays often result from third-party courier issues, but customers blame the brand directly. With increased competition from Shopee and Lazada, even a 1–2 day delay can lead to order cancellations and loss of repeat business. A well-crafted resolution must be empathetic, transparent, and include a goodwill gesture to...\n\nDesired outcome:\nCreate a late delivery complaint resolution template for e-commerce businesses.\n\nMy details:\n- E commerce Late Delivery Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Delivery tracking data\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":13,"title":"Bank Transaction Failure Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Advanced","explanation":"Design a transaction failure complaint resolution template for banking services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Bank Transaction Failure Complaint\"\n\nStarting brief:\nYou are a financial services communication officer. Create a transaction failure resolution template that includes:\n\nBusiness context:\nA 32-year-old relationship manager at a Singapore retail bank in the Raffles Place CBD gets an urgent complaint from a customer whose funds were debited via PayNow but not credited to the intended account. The customer is anxious because the transaction amount is large and time-sensitive. Financial complaints demand swift acknowledgment, strict adherence to MAS compliance, and absolute clarity in communication to maintain trust.\n\nDesired outcome:\nDesign a transaction failure complaint resolution template for banking services.\n\nMy details:\n- Bank Transaction Failure Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Transaction dispute SOP\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":14,"title":"Restaurant Food Quality Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Develop a food quality complaint resolution template for restaurants. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Restaurant Food Quality Complaint\"\n\nStarting brief:\nYou are a hospitality communication specialist. Draft a food quality complaint resolution template that includes:\n\nBusiness context:\nIn a premium restaurant at Marina Bay Sands, a 27-year-old guest relations manager receives a complaint about undercooked seafood. Food quality issues in high-end dining can damage the brand overnight, especially if the customer is an influential food blogger. The response must combine humility, swift action, and a strong assurance of SFA-compliant food safety standards.\n\nDesired outcome:\nDevelop a food quality complaint resolution template for restaurants.\n\nMy details:\n- Restaurant Food Quality Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Food safety SOP\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":15,"title":"Subscription Service Auto Renewal Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Create an auto-renewal complaint resolution template for subscription services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Subscription Service Auto Renewal Complaint\"\n\nStarting brief:\nYou are a SaaS customer experience expert. Create a resolution template for unintended auto-renewals that includes:\n\nBusiness context:\nA 30-year-old customer support lead at a SaaS company based in one-north handles complaints from users charged automatically for a subscription they didn't intend to renew. Customers feel trapped when they miss the cancellation window, leading to frustration. The resolution must balance company policy with goodwill to maintain brand reputation and user retention.\n\nDesired outcome:\nCreate an auto-renewal complaint resolution template for subscription services.\n\nMy details:\n- Subscription Service Auto Renewal Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Refund/credit policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":16,"title":"Telecom Network Outage Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Advanced","explanation":"Create a complaint resolution template for telecom network outages that balances transparency with reassurance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Telecom Network Outage Complaint\"\n\nStarting brief:\nYou are a telecom service resolution expert. Draft a network outage complaint response template that includes:\n\nBusiness context:\nA 31-year-old telecom customer service supervisor at a Singapore operator headquartered in Paya Lebar receives an urgent complaint from a business owner whose internet and phone lines have been down for over 6 hours. The outage has disrupted point-of-sale transactions and caused customer losses. Network outage complaints are high-pressure, as customers expect not just speed but also clarity and accountability. The response must address both the technical and emotional aspects of the situation.\n\nDesired outcome:\nCreate a complaint resolution template for telecom network outages that balances transparency with reassurance.\n\nMy details:\n- Telecom Network Outage Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Latest outage status report\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":17,"title":"Hotel Overbooking Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Design an overbooking complaint resolution template for hotels. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Hotel Overbooking Complaint\"\n\nStarting brief:\nYou are a hospitality guest recovery specialist. Create a resolution template for overbooking cases that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nDesign an overbooking complaint resolution template for hotels.\n\nMy details:\n- Hotel Overbooking Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Partner hotel list for rebooking\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":18,"title":"Ride Hailing Driver Misconduct Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Advanced","explanation":"Create a driver misconduct complaint resolution template for ride-hailing services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Ride Hailing Driver Misconduct Complaint\"\n\nStarting brief:\nYou are a ride-hailing safety and compliance expert. Draft a misconduct complaint response template that includes:\n\nBusiness context:\nA 26-year-old customer safety officer at a ride-hailing startup based in Singapore receives a complaint about a driver behaving rudely and refusing to follow the GPS route. Such complaints are sensitive as they directly affect customer safety perception and app ratings. The resolution must show zero tolerance for misconduct while protecting due process for the driver.\n\nDesired outcome:\nCreate a driver misconduct complaint resolution template for ride-hailing services.\n\nMy details:\n- Ride Hailing Driver Misconduct Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Driver conduct policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":19,"title":"Courier Package Damage Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Develop a damaged package complaint resolution template for courier companies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Courier Package Damage Complaint\"\n\nStarting brief:\nYou are a courier claims communication expert. Create a resolution template that includes:\n\nBusiness context:\nA 29-year-old claims officer at a Singapore courier company based in Tuas deals with a complaint from a customer whose fragile ceramic vase arrived shattered after a Marina Bay to Woodlands delivery. The sender is angry as the package was marked \"Handle with Care.\" Damage complaints can trigger refund disputes, negative reviews, and insurance claims. The resolution must be empathetic, fast, and clearly outline the claims process.\n\nDesired outcome:\nDevelop a damaged package complaint resolution template for courier companies.\n\nMy details:\n- Courier Package Damage Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Damage claim form link\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":20,"title":"Streaming Service Content Removal Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Create a complaint resolution template for streaming platforms explaining content removal. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Streaming Service Content Removal Complaint\"\n\nStarting brief:\nYou are a streaming service communication strategist. Draft a resolution template that includes:\n\nBusiness context:\nA 27-year-old content operations manager at a streaming platform faces a complaint from a user upset about their favorite TV series being removed suddenly. The customer had subscribed specifically for that series. Content removal complaints involve high emotional investment and require careful brand tone management.\n\nDesired outcome:\nCreate a complaint resolution template for streaming platforms explaining content removal.\n\nMy details:\n- Streaming Service Content Removal Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Removal reason and date\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":21,"title":"Online Course Access Issue Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Beginner","explanation":"Develop a course access issue complaint resolution template for EdTech platforms. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Online Course Access Issue Complaint\"\n\nStarting brief:\nYou are an EdTech student success specialist. Create a resolution template that includes:\n\nBusiness context:\nA 34-year-old support head at a Singapore EdTech company in one-north gets a complaint from a student who paid for a premium course but cannot access it for two days. The student's polytechnic exam is approaching, and the delay has caused high stress. The resolution must convey urgency, empathy, and provide an immediate workaround.\n\nDesired outcome:\nDevelop a course access issue complaint resolution template for EdTech platforms.\n\nMy details:\n- Online Course Access Issue Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Access troubleshooting steps\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":22,"title":"Event Ticket Refund Delay Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Create a complaint resolution template for delayed refunds in ticketing services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Event Ticket Refund Delay Complaint\"\n\nStarting brief:\nYou are a ticketing platform customer experience manager. Draft a refund delay resolution template that includes:\n\nBusiness context:\nA 25-year-old support executive at a Singapore ticketing platform in the CBD is dealing with a complaint from a customer who has been waiting over 15 days for a refund on a cancelled concert at the Singapore Indoor Stadium. Refund delays quickly erode trust in ticketing services and can result in public complaints on social media.\n\nDesired outcome:\nCreate a complaint resolution template for delayed refunds in ticketing services.\n\nMy details:\n- Event Ticket Refund Delay Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Refund processing time policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":23,"title":"Medical Lab Test Report Delay Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Develop a complaint resolution template for delayed lab test reports. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Medical Lab Test Report Delay Complaint\"\n\nStarting brief:\nYou are a healthcare service quality expert. Draft a resolution template that includes:\n\nBusiness context:\nA 33-year-old operations manager at a Singapore pathology lab in Novena receives a complaint from a patient whose critical test results have been delayed, affecting their treatment schedule at a nearby private hospital. Medical delays carry both health and emotional consequences, making swift communication essential.\n\nDesired outcome:\nDevelop a complaint resolution template for delayed lab test reports.\n\nMy details:\n- Medical Lab Test Report Delay Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Lab delay SOP\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":24,"title":"Gym Membership Cancellation Refund Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Create a complaint resolution template for delayed gym membership refunds. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Gym Membership Cancellation Refund Complaint\"\n\nStarting brief:\nYou are a fitness service operations manager. Draft a membership refund resolution template that includes:\n\nBusiness context:\nA 28-year-old fitness centre manager at a Singapore gym chain in Tampines gets a complaint from a member whose cancellation refund has not been processed even after the promised 10 days. The customer feels misled and is threatening to post negative reviews on Google and Facebook.\n\nDesired outcome:\nCreate a complaint resolution template for delayed gym membership refunds.\n\nMy details:\n- Gym Membership Cancellation Refund Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Membership refund policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":25,"title":"Insurance Claim Rejection Complaint","category":"Customer Comms","source":"Admin & Ops","module":"Complaint resolution templates","difficulty":"Intermediate","explanation":"Develop a claim rejection complaint resolution template for insurance companies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Insurance Claim Rejection Complaint\"\n\nStarting brief:\nYou are an insurance communication expert. Draft a claim rejection resolution template that includes:\n\nBusiness context:\nA 35-year-old claims officer at a Singapore insurance company in Raffles Place handles a complaint from a customer whose claim for hospitalisation expenses was rejected. The customer is emotionally distressed and believes the rejection was unfair. Insurance complaints are highly sensitive, requiring precision, transparency, and empathy to avoid escalation to MAS or the Financial Industry Disputes Resolution Centre (FIDReC).\n\nDesired outcome:\nDevelop a claim rejection complaint resolution template for insurance companies.\n\nMy details:\n- Insurance Claim Rejection Complaint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Claim rejection reasons\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":26,"title":"E commerce Return & Refund FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a customer-friendly FAQ for returns and refunds. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"E commerce Return & Refund FAQ\"\n\nStarting brief:\nYou are an e-commerce helpdesk content specialist. Create a multilingual (English + Mandarin + Malay) FAQ section for returns and refunds.\n\nBusiness context:\nA 27-year-old operations manager at a Singapore-based online fashion store headquartered in Paya Lebar is struggling with repetitive queries about returns and refunds. Customers often get frustrated because they can't find clear answers on the website, leading to unnecessary calls to customer care. She wants a comprehensive FAQ page that explains timelines, conditions, and refund modes in plain English (with optional Mandarin and Malay versions for broader reach).\n\nDesired outcome:\nCreate a customer-friendly FAQ for returns and refunds.\n\nMy details:\n- E commerce Return & Refund FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Return policy document\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":27,"title":"Bank Loan Application FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Develop an FAQ section for personal loan applications. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Bank Loan Application FAQ\"\n\nStarting brief:\nYou are a banking content writer. Prepare a clear FAQ for personal loan applicants.\n\nBusiness context:\nA 32-year-old relationship manager at a Singapore bank branch in Raffles Place wants to reduce branch traffic caused by basic queries about personal loans. She needs a concise yet thorough FAQ section on the bank's app and website that covers everything from eligibility and documents to monthly instalment calculation.\n\nDesired outcome:\nDevelop an FAQ section for personal loan applications.\n\nMy details:\n- Bank Loan Application FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Bank's personal loan product details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":28,"title":"Tech Product Troubleshooting FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Advanced","explanation":"Build a self-service troubleshooting FAQ for Wi-Fi issues. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Tech Product Troubleshooting FAQ\"\n\nStarting brief:\nYou are a tech support content creator. Write a troubleshooting FAQ for smart home device Wi-Fi issues.\n\nBusiness context:\nA 25-year-old customer success executive at a Singapore-based electronics company in Jurong East keeps getting the same calls from customers facing Wi-Fi connectivity issues with their smart home device. She wants an FAQ that includes easy-to-follow troubleshooting steps with images or short videos.\n\nDesired outcome:\nBuild a self-service troubleshooting FAQ for Wi-Fi issues.\n\nMy details:\n- Tech Product Troubleshooting FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Technical troubleshooting steps from engineering team\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":29,"title":"Healthcare Appointment FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a patient-friendly appointment and telemedicine FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Healthcare Appointment FAQ\"\n\nStarting brief:\nYou are a healthcare communications writer. Develop an FAQ covering:\n\nBusiness context:\nA 30-year-old administrator at a Singapore private hospital in the Novena medical hub is facing patient frustration due to confusion over appointment booking, cancellations, and telemedicine procedures. She wants an FAQ that answers these questions clearly for both in-person and online consultations.\n\nDesired outcome:\nCreate a patient-friendly appointment and telemedicine FAQ.\n\nMy details:\n- Healthcare Appointment FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Hospital's booking process flow\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":30,"title":"Travel Agency Visa FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Prepare a country-specific visa FAQ for travellers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Travel Agency Visa FAQ\"\n\nStarting brief:\nYou are a travel operations specialist. Create a visa FAQ for the top 10 travel destinations from Singapore.\n\nBusiness context:\nA 28-year-old travel consultant at a Singapore agency in Orchard handles international tour bookings but spends hours answering basic visa-related questions. She needs a destination-wise visa FAQ that travellers can read before calling the agency.\n\nDesired outcome:\nPrepare a country-specific visa FAQ for travellers.\n\nMy details:\n- Travel Agency Visa FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Updated visa requirements for each country\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":31,"title":"Food Delivery App Order Issue FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create an app-based FAQ for common order issues. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Food Delivery App Order Issue FAQ\"\n\nStarting brief:\nYou are a customer support content designer. Create a mobile-friendly FAQ that covers:\n\nBusiness context:\nA 26-year-old support lead at a Singapore food delivery startup based in one-north is overwhelmed with calls about missing items, delayed orders, and refund eligibility. She needs an FAQ that customers can quickly refer to in the app before raising a ticket.\n\nDesired outcome:\nCreate an app-based FAQ for common order issues.\n\nMy details:\n- Food Delivery App Order Issue FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Refund policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":32,"title":"Telecom Service Activation FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Build a customer-friendly telecom service activation FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Telecom Service Activation FAQ\"\n\nStarting brief:\nYou are a telecom helpdesk writer. Prepare an FAQ covering:\n\nBusiness context:\nA 31-year-old customer care manager at a Singapore telecom provider headquartered in the CBD is struggling with repeated calls about SIM activation, porting, and eSIM setup. She wants an FAQ that answers these queries in plain, jargon-free language.\n\nDesired outcome:\nBuild a customer-friendly telecom service activation FAQ.\n\nMy details:\n- Telecom Service Activation FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Telecom activation process docs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":33,"title":"Online Education Platform FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Beginner","explanation":"Create a comprehensive FAQ for online course access. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Online Education Platform FAQ\"\n\nStarting brief:\nYou are an edtech support writer. Build an FAQ covering:\n\nBusiness context:\nA 29-year-old course coordinator at a Singapore edtech startup based in one-north finds that students often drop out because they can't find clear answers about course access, live class links, and recorded lectures.\n\nDesired outcome:\nCreate a comprehensive FAQ for online course access.\n\nMy details:\n- Online Education Platform FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- LMS platform guide\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":34,"title":"Ride Hailing Driver FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Beginner","explanation":"Create a driver partner onboarding FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Ride Hailing Driver FAQ\"\n\nStarting brief:\nYou are a driver relations specialist. Build an FAQ for new drivers covering:\n\nBusiness context:\nA 33-year-old driver partner manager at a Singapore ride-hailing service headquartered in the CBD is dealing with constant queries from new drivers about payouts, penalties, and customer ratings.\n\nDesired outcome:\nCreate a driver partner onboarding FAQ.\n\nMy details:\n- Ride Hailing Driver FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Payment structure document\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":35,"title":"Banking Credit Card FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Beginner","explanation":"Prepare a credit card usage FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Banking Credit Card FAQ\"\n\nStarting brief:\nYou are a banking customer education writer. Create an FAQ covering:\n\nBusiness context:\nA 28-year-old banking call centre manager at a Singapore retail bank in the CBD is getting high call volumes for credit card activation, bill payment, and reward redemption queries.\n\nDesired outcome:\nPrepare a credit card usage FAQ.\n\nMy details:\n- Banking Credit Card FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Card product features\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":36,"title":"Airline Check in & Baggage FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Advanced","explanation":"Create a passenger-friendly check-in FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Airline Check in & Baggage FAQ\"\n\nStarting brief:\nYou are an airline support content writer. Develop an FAQ covering:\n\nBusiness context:\nA 30-year-old customer service officer at a regional airline operating out of Changi Airport wants to reduce check-in counter congestion by giving passengers an online FAQ about baggage allowances, check-in times, and prohibited items.\n\nDesired outcome:\nCreate a passenger-friendly check-in FAQ.\n\nMy details:\n- Airline Check in & Baggage FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Airline baggage policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":37,"title":"Insurance Claim FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Develop a claim filing FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Insurance Claim FAQ\"\n\nStarting brief:\nYou are an insurance helpdesk writer. Create an FAQ covering:\n\nBusiness context:\nA 32-year-old claims manager at a general insurance company headquartered in Singapore's CBD is dealing with repeated policyholder queries about the claim filing process and required documents.\n\nDesired outcome:\nDevelop a claim filing FAQ.\n\nMy details:\n- Insurance Claim FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Policy T&Cs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":38,"title":"Gym Membership FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Beginner","explanation":"Create a gym membership FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Gym Membership FAQ\"\n\nStarting brief:\nYou are a fitness center operations writer. Create an FAQ covering:\n\nBusiness context:\nA 25-year-old front desk manager at a fitness chain with outlets in Tampines and Orchard is constantly asked about membership freeze policies, class bookings, and locker usage.\n\nDesired outcome:\nCreate a gym membership FAQ.\n\nMy details:\n- Gym Membership FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Membership T&Cs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":39,"title":"NGO Volunteer FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a volunteer onboarding FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"NGO Volunteer FAQ\"\n\nStarting brief:\nYou are a nonprofit support writer. Prepare an FAQ covering:\n\nBusiness context:\nA 27-year-old volunteer coordinator at a Singapore-based charity registered with the Commissioner of Charities is tired of repeating onboarding steps to new volunteers.\n\nDesired outcome:\nCreate a volunteer onboarding FAQ.\n\nMy details:\n- NGO Volunteer FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Volunteer policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":40,"title":"OTT Subscription FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Beginner","explanation":"Create an OTT subscription FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"OTT Subscription FAQ\"\n\nStarting brief:\nYou are an OTT helpdesk content creator. Create an FAQ covering:\n\nBusiness context:\nA 26-year-old customer support lead at a streaming service based in Singapore is facing ticket overload from users about subscription plans, renewal, and download limits.\n\nDesired outcome:\nCreate an OTT subscription FAQ.\n\nMy details:\n- OTT Subscription FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Plan details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":41,"title":"Government Service Portal FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a citizen-friendly FAQ for portal access. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Government Service Portal FAQ\"\n\nStarting brief:\nYou are an e-governance communication officer. Build an FAQ covering:\n\nBusiness context:\nA 31-year-old IT officer at a Singapore government agency working with GovTech is tasked with reducing citizen complaints about logging into a SingPass-linked services portal.\n\nDesired outcome:\nCreate a citizen-friendly FAQ for portal access.\n\nMy details:\n- Government Service Portal FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Portal user manual\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":42,"title":"Event Ticket Booking FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create an event ticketing FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Event Ticket Booking FAQ\"\n\nStarting brief:\nYou are an event customer service writer. Build an FAQ covering:\n\nBusiness context:\nA 29-year-old event manager in Singapore is running a music festival at the Marina Bay Floating Platform and getting too many repetitive calls about ticket booking, QR codes, and seating arrangements.\n\nDesired outcome:\nCreate an event ticketing FAQ.\n\nMy details:\n- Event Ticket Booking FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Ticketing platform guide\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":43,"title":"College Admission FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create an admission FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"College Admission FAQ\"\n\nStarting brief:\nYou are a higher education communications officer. Create an FAQ covering:\n\nBusiness context:\nA 33-year-old admissions officer at a Singapore autonomous university faces endless calls from parents and students about eligibility, application timelines, and document submission.\n\nDesired outcome:\nCreate an admission FAQ.\n\nMy details:\n- College Admission FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Admission policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":44,"title":"Real Estate Buyer FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Beginner","explanation":"Create a property purchase FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Real Estate Buyer FAQ\"\n\nStarting brief:\nYou are a real estate support writer. Develop an FAQ covering:\n\nBusiness context:\nA 32-year-old sales manager at a Singapore property developer launching a new condo project in District 19 is flooded with calls about payment plans, possession timelines, and legal clearances.\n\nDesired outcome:\nCreate a property purchase FAQ.\n\nMy details:\n- Real Estate Buyer FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Payment plan\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":45,"title":"Courier Tracking FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a shipment tracking FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Courier Tracking FAQ\"\n\nStarting brief:\nYou are a logistics support content writer. Create an FAQ covering:\n\nBusiness context:\nA 25-year-old customer care agent at a logistics company operating out of Tuas with last-mile delivery across Singapore is constantly asked about shipment delays and tracking updates.\n\nDesired outcome:\nCreate a shipment tracking FAQ.\n\nMy details:\n- Courier Tracking FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Tracking process flow\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":46,"title":"Corporate IT Helpdesk FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create an IT helpdesk FAQ for employees. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Corporate IT Helpdesk FAQ\"\n\nStarting brief:\nYou are a corporate IT support writer. Build an FAQ covering:\n\nBusiness context:\nA 30-year-old IT manager at an MNC with its regional HQ in Singapore's one-north business park is tasked with reducing employee tickets for password resets, VPN access, and printer issues.\n\nDesired outcome:\nCreate an IT helpdesk FAQ for employees.\n\nMy details:\n- Corporate IT Helpdesk FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- IT policies\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":47,"title":"Hospital Insurance Tie Up FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a hospital insurance FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Hospital Insurance Tie Up FAQ\"\n\nStarting brief:\nYou are a healthcare insurance liaison. Create an FAQ covering:\n\nBusiness context:\nA 34-year-old patient services head at a private multi-specialty hospital in Singapore needs an FAQ to answer patient queries about cashless treatment and Integrated Shield Plan insurance tie-ups.\n\nDesired outcome:\nCreate a hospital insurance FAQ.\n\nMy details:\n- Hospital Insurance Tie Up FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Insurance partner list\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":48,"title":"SaaS Software Pricing FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a SaaS pricing FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"SaaS Software Pricing FAQ\"\n\nStarting brief:\nYou are a SaaS product support writer. Develop an FAQ covering:\n\nBusiness context:\nA 29-year-old sales engineer at a SaaS startup based in Paya Lebar Quarter is facing repetitive questions about subscription tiers, free trials, and add-on costs.\n\nDesired outcome:\nCreate a SaaS pricing FAQ.\n\nMy details:\n- SaaS Software Pricing FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Pricing sheet\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":49,"title":"Hotel Booking FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Intermediate","explanation":"Create a hotel booking FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Hotel Booking FAQ\"\n\nStarting brief:\nYou are a hospitality communications specialist. Create an FAQ covering:\n\nBusiness context:\nA 28-year-old reservations manager at a beachfront resort on Sentosa is getting repetitive queries about cancellation policies, room upgrades, and check-in timings.\n\nDesired outcome:\nCreate a hotel booking FAQ.\n\nMy details:\n- Hotel Booking FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Hotel policies\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":50,"title":"Digital Wallet FAQ","category":"Customer Comms","source":"Admin & Ops","module":"Helpdesk FAQ creation","difficulty":"Advanced","explanation":"Create a digital wallet FAQ. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Digital Wallet FAQ\"\n\nStarting brief:\nYou are a fintech support writer. Build an FAQ covering:\n\nBusiness context:\nA 26-year-old support executive at a fintech app based in Singapore gets constant calls about wallet top-ups, PayNow transfer limits, and failed transaction refunds.\n\nDesired outcome:\nCreate a digital wallet FAQ.\n\nMy details:\n- Digital Wallet FAQ details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Wallet policy document\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":51,"title":"Order Delay Notification – English & Mandarin","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual (English & Mandarin) script for informing customers about shipment delays while keeping the tone apologetic yet confident. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Order Delay Notification – English & Mandarin\"\n\nStarting brief:\nYou are a customer communication specialist. Create a bilingual (English & Mandarin) order delay notification script that includes:\n\nBusiness context:\nA Singapore-based e-commerce marketplace ships thousands of packages daily across the island and into nearby Southeast Asian markets. Customers comprise a mix of English- and Mandarin-speaking shoppers. Agents currently write order delay messages in free form, leading to inconsistent tone and missing key details. The company needs a bilingual template to maintain professionalism and trust while providing full delay details.\n\nDesired outcome:\nCreate a bilingual (English & Mandarin) script for informing customers about shipment delays while keeping the tone apologetic yet confident.\n\nMy details:\n- Order Delay Notification – English & Mandarin details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":52,"title":"Service Appointment Confirmation – English & Tamil","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual (English & Tamil) appointment confirmation script that ensures no detail is missed. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Service Appointment Confirmation – English & Tamil\"\n\nStarting brief:\nYou are a service operations communication expert. Create a bilingual (English & Tamil) appointment confirmation script that includes:\n\nBusiness context:\nA home appliance repair service operating across Singapore deals with customers who prefer Tamil — particularly in HDB heartland neighbourhoods like Little India, Tekka, and Woodlands — and others who prefer English. Appointment confirmations vary in style, sometimes missing crucial time or location details, leading to cancellations.\n\nDesired outcome:\nCreate a bilingual (English & Tamil) appointment confirmation script that ensures no detail is missed.\n\nMy details:\n- Service Appointment Confirmation – English & Tamil details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":53,"title":"Payment Reminder – English & Malay","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual (English & Malay) polite payment reminder that encourages timely action without sounding threatening. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Payment Reminder – English & Malay\"\n\nStarting brief:\nYou are a financial customer care scriptwriter. Create a bilingual (English & Malay) premium payment reminder script that includes:\n\nBusiness context:\nA Singapore-based insurance company needs a uniform way to remind customers across its Malay-speaking and English-speaking policyholder base about premium payments. Without a standardized bilingual script, reminders sound either too aggressive or too casual, affecting collections.\n\nDesired outcome:\nCreate a bilingual (English & Malay) polite payment reminder that encourages timely action without sounding threatening.\n\nMy details:\n- Payment Reminder – English & Malay details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":54,"title":"Refund Processing Update – English & Gujarati","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Intermediate","explanation":"Create a bilingual (English & Gujarati) refund update script that reassures customers and clearly outlines next steps. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Refund Processing Update – English & Gujarati\"\n\nStarting brief:\nYou are a customer retention specialist. Create a bilingual (English & Gujarati) refund update script that includes:\n\nBusiness context:\nA Singapore-based online retailer with a strong customer base in the Gujarati-speaking Indian community (across Little India, Tekka, and Serangoon) often gets queries about refunds. Current responses differ between agents, causing confusion about timelines and refund methods. A standardized bilingual message is required.\n\nDesired outcome:\nCreate a bilingual (English & Gujarati) refund update script that reassures customers and clearly outlines next steps.\n\nMy details:\n- Refund Processing Update – English & Gujarati details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":55,"title":"Account Setup Instructions – English & Marathi","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual (English & Marathi) account setup script that is clear, concise, and culturally appropriate. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Account Setup Instructions – English & Marathi\"\n\nStarting brief:\nYou are a fintech onboarding communication specialist. Create a bilingual (English & Marathi) script for guiding customers through digital account setup, including:\n\nBusiness context:\nA Singapore-headquartered fintech expanding into the South Asian market is onboarding thousands of first-time digital banking customers across Southeast Asia, including a sizeable Marathi-speaking diaspora segment. Without a bilingual guide, customers misunderstand setup steps and call support unnecessarily.\n\nDesired outcome:\nCreate a bilingual (English & Marathi) account setup script that is clear, concise, and culturally appropriate.\n\nMy details:\n- Account Setup Instructions – English & Marathi details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":56,"title":"Product Usage Guidance – English & Kannada","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Advanced","explanation":"Create a bilingual (English & Kannada) product usage assistance script for customer service calls. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Product Usage Guidance – English & Kannada\"\n\nStarting brief:\nYou are a customer experience trainer. Create a bilingual (English & Kannada) product usage assistance script that includes:\n\nBusiness context:\nA Singapore-based smart home electronics company sells across Southeast Asia, with a meaningful share of customers in the Kannada-speaking diaspora and partner markets. Customers speak both English and Kannada. The lack of consistent instructions in both languages reduces product satisfaction.\n\nDesired outcome:\nCreate a bilingual (English & Kannada) product usage assistance script for customer service calls.\n\nMy details:\n- Product Usage Guidance – English & Kannada details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product name & model\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":57,"title":"Complaint Acknowledgment – English & Telugu","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual complaint acknowledgment script that reassures the customer their issue is being addressed. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Complaint Acknowledgment – English & Telugu\"\n\nStarting brief:\nYou are a customer complaint handling expert. Create a bilingual (English & Telugu) complaint acknowledgment script that includes:\n\nBusiness context:\nA Singapore-based telecom service provider serving a growing South Asian customer base wants to ensure every complaint is acknowledged in both English and Telugu to build trust and prevent escalation. Currently, some agents skip important empathy phrases.\n\nDesired outcome:\nCreate a bilingual complaint acknowledgment script that reassures the customer their issue is being addressed.\n\nMy details:\n- Complaint Acknowledgment – English & Telugu details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":58,"title":"Renewal Reminder – English & Malayalam","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual (English & Malayalam) polite membership renewal reminder. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Renewal Reminder – English & Malayalam\"\n\nStarting brief:\nYou are a customer retention specialist. Create a bilingual (English & Malayalam) script for membership renewal reminders, including:\n\nBusiness context:\nA Singapore-based fitness chain with branches in Tampines, Jurong, and Orchard wants to remind members about membership renewal. A meaningful share of its members are Malayalam speakers from the local Indian community and expatriate professionals. Without a standard script, tone varies from pushy to vague, affecting retention.\n\nDesired outcome:\nCreate a bilingual (English & Malayalam) polite membership renewal reminder.\n\nMy details:\n- Renewal Reminder – English & Malayalam details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":59,"title":"Delivery Confirmation – English & Punjabi","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual delivery confirmation script that thanks customers and confirms order completion. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Delivery Confirmation – English & Punjabi\"\n\nStarting brief:\nYou are a last-mile delivery communication expert. Create a bilingual (English & Punjabi) delivery confirmation script that includes:\n\nBusiness context:\nA Singapore-based organic food brand delivers across the island and serves a notable Punjabi-speaking customer segment in the Sikh community around Silat Road and beyond. Customers often call to ask if delivery has been completed. A standardized bilingual confirmation message would improve efficiency and trust.\n\nDesired outcome:\nCreate a bilingual delivery confirmation script that thanks customers and confirms order completion.\n\nMy details:\n- Delivery Confirmation – English & Punjabi details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":60,"title":"EMI Payment Reminder – English & Gujarati","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Intermediate","explanation":"Create a culturally respectful instalment payment reminder script in English and Gujarati that ensures customers understand the amount, due date, and payment process without feeling pressured. Copy-ready prompt with placeholders, task steps, output format,...","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"EMI Payment Reminder – English & Gujarati\"\n\nStarting brief:\nYou are a consumer finance communication strategist. Write a bilingual (English & Gujarati) monthly instalment payment reminder script for phone calls and SMS. The script must include:\n\nBusiness context:\nA Singapore-based consumer finance company serves customers across the island, including a sizeable Gujarati-speaking segment among long-time merchant families and recent expatriates. Many customers prefer Gujarati over English when discussing financial matters. Currently, agents use informal, inconsistent phrasing, sometimes missing critical details like due dates or late fees. This causes confusion, late payments, and additional support calls. A well-structured, professional bilingual script will ensure clarity,...\n\nDesired outcome:\nCreate a culturally respectful instalment payment reminder script in English and Gujarati that ensures customers understand the amount, due date, and payment process without feeling pressured.\n\nMy details:\n- EMI Payment Reminder – English & Gujarati details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":61,"title":"Refund Status Update – English & Bengali","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Intermediate","explanation":"Design a refund status update script in English and Bengali that is empathetic, clear, and maintains brand trust. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Refund Status Update – English & Bengali\"\n\nStarting brief:\nYou are an e-commerce support communication expert. Create a bilingual (English & Bengali) refund status update script that includes:\n\nBusiness context:\nA Singapore-based online fashion retailer processes thousands of refund requests monthly, with a significant portion of customers being Bengali-speaking professionals and migrant workers who find English-only updates impersonal and confusing. Without a uniform bilingual approach, some agents miss empathy cues, causing frustration and distrust.\n\nDesired outcome:\nDesign a refund status update script in English and Bengali that is empathetic, clear, and maintains brand trust.\n\nMy details:\n- Refund Status Update – English & Bengali details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":62,"title":"Product Warranty Claim – English & Tamil","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Advanced","explanation":"Develop a bilingual warranty claim explanation script in English and Tamil for call centre and email use. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Product Warranty Claim – English & Tamil\"\n\nStarting brief:\nYou are a product support language specialist. Create a bilingual (English & Tamil) warranty claim assistance script that covers:\n\nBusiness context:\nA Singapore-based home appliance brand is seeing an increase in warranty claims from across the island. Tamil is one of Singapore's four official languages, and a significant share of customers prefer Tamil for technical communication. Without a bilingual Tamil-English guide, customers misunderstand the process due to complex English terms in manuals — they submit incomplete forms or miss deadlines, creating additional service load.\n\nDesired outcome:\nDevelop a bilingual warranty claim explanation script in English and Tamil for call centre and email use.\n\nMy details:\n- Product Warranty Claim – English & Tamil details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":63,"title":"Order Delay Notification – English & Odia","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Advanced","explanation":"Create a delay notification script in English and Odia that is empathetic, transparent, and helps retain customer trust. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Order Delay Notification – English & Odia\"\n\nStarting brief:\nYou are a customer satisfaction strategist. Create a bilingual (English & Odia) order delay notification script including:\n\nBusiness context:\nA Singapore-based handicraft and homeware exporter ships locally and internationally, sourcing artisanal pieces from Odia-speaking craft clusters and serving an Odia-speaking diaspora customer base across Southeast Asia. Shipping delays during peak demand often frustrate customers. Odia-speaking customers, in particular, appreciate receiving updates in their native language. Current notifications lack empathy and personalisation, leading to cancellations.\n\nDesired outcome:\nCreate a delay notification script in English and Odia that is empathetic, transparent, and helps retain customer trust.\n\nMy details:\n- Order Delay Notification – English & Odia details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":64,"title":"Service Appointment Reminder – English & Urdu","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual appointment reminder in English and Urdu for WhatsApp, SMS, and calls. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Service Appointment Reminder – English & Urdu\"\n\nStarting brief:\nYou are a customer engagement copywriter. Create a bilingual (English & Urdu) appointment reminder script that includes:\n\nBusiness context:\nA Singapore-based home cleaning services company caters to both English-speaking households and Urdu-speaking customers, including expatriate families and migrant workers across the island. Service no-shows are common because reminders are inconsistent or unclear. A standard bilingual script will reduce missed appointments and improve customer satisfaction.\n\nDesired outcome:\nCreate a bilingual appointment reminder in English and Urdu for WhatsApp, SMS, and calls.\n\nMy details:\n- Service Appointment Reminder – English & Urdu details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":65,"title":"Premium Subscription Renewal – English & Kannada","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Intermediate","explanation":"Create a friendly and persuasive subscription renewal script in English and Kannada that encourages prompt action while highlighting benefits. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Premium Subscription Renewal – English & Kannada\"\n\nStarting brief:\nYou are a retention-focused communication expert. Write a bilingual (English & Kannada) premium subscription renewal reminder that includes:\n\nBusiness context:\nA Singapore-based online learning platform offers premium courses in technology and business across Southeast Asia. Many subscribers are professionals from the Kannada-speaking community who speak Kannada at home but interact in English at work. Without a bilingual renewal reminder, customers may overlook critical details like expiry date and renewal steps, leading to churn.\n\nDesired outcome:\nCreate a friendly and persuasive subscription renewal script in English and Kannada that encourages prompt action while highlighting benefits.\n\nMy details:\n- Premium Subscription Renewal – English & Kannada details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":66,"title":"Bank Account Opening Confirmation – English & Hindi","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Intermediate","explanation":"Design a clear bilingual account opening confirmation for SMS and printed receipt. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Bank Account Opening Confirmation – English & Hindi\"\n\nStarting brief:\nYou are a banking communication advisor. Create a bilingual (English & Hindi) account opening confirmation that covers:\n\nBusiness context:\nA Singapore retail bank with branches across Little India, Jurong, and the CBD receives high walk-in traffic from customers in the Hindi-speaking community, including expatriate professionals and migrant workers. Many customers are uncertain if their account is active after document submission. The bank wants a standard bilingual confirmation to assure customers and provide next steps.\n\nDesired outcome:\nDesign a clear bilingual account opening confirmation for SMS and printed receipt.\n\nMy details:\n- Bank Account Opening Confirmation – English & Hindi details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":67,"title":"Delivery Rescheduling – English & Malayalam","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a professional yet friendly bilingual delivery rescheduling message for calls, WhatsApp, and SMS. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Delivery Rescheduling – English & Malayalam\"\n\nStarting brief:\nYou are a last-mile delivery communication specialist. Create a bilingual (English & Malayalam) delivery rescheduling notification including:\n\nBusiness context:\nA Singapore-based online grocery store frequently faces delivery slot changes due to heavy tropical rain across the island. Customers who speak Malayalam — including a sizeable diaspora and expatriate professional segment — need clear updates to avoid frustration. Without a proper bilingual script, miscommunication leads to repeated support calls.\n\nDesired outcome:\nCreate a professional yet friendly bilingual delivery rescheduling message for calls, WhatsApp, and SMS.\n\nMy details:\n- Delivery Rescheduling – English & Malayalam details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":68,"title":"Maintenance Downtime Alert – English & Marathi","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Advanced","explanation":"Create a maintenance downtime alert that is clear, polite, and transparent. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Maintenance Downtime Alert – English & Marathi\"\n\nStarting brief:\nYou are a telecom service communication strategist. Write a bilingual (English & Marathi) downtime alert that includes:\n\nBusiness context:\nA Singapore-based broadband provider serving residential customers across Tampines, Punggol, and Bukit Panjang schedules monthly maintenance windows. A growing pocket of Marathi-speaking expatriate customers often misunderstand downtime messages and flood the helpline. A standard bilingual script will cut unnecessary calls and reassure customers.\n\nDesired outcome:\nCreate a maintenance downtime alert that is clear, polite, and transparent.\n\nMy details:\n- Maintenance Downtime Alert – English & Marathi details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":69,"title":"Credit Card Bill Reminder – English & Punjabi","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a credit card bill reminder script in English and Punjabi for SMS and calls. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Credit Card Bill Reminder – English & Punjabi\"\n\nStarting brief:\nYou are a financial communication expert. Write a bilingual (English & Punjabi) credit card bill reminder that includes:\n\nBusiness context:\nA Singapore-based private bank serves many Punjabi-speaking SME owners and professionals who occasionally miss credit card due dates due to unclear reminders. A formal yet friendly bilingual message will improve on-time payments.\n\nDesired outcome:\nCreate a credit card bill reminder script in English and Punjabi for SMS and calls.\n\nMy details:\n- Credit Card Bill Reminder – English & Punjabi details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":70,"title":"Post Service Feedback Request – English & Hindi","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a feedback request script in English and Hindi that is warm and easy to respond to. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Post Service Feedback Request – English & Hindi\"\n\nStarting brief:\nYou are a customer experience manager. Write a bilingual (English & Hindi) post-service feedback request that includes:\n\nBusiness context:\nA Singapore-based air conditioning service company wants to improve customer satisfaction tracking. Many customers in its expatriate and migrant-worker segments are Hindi speakers who ignore English-only feedback links.\n\nDesired outcome:\nCreate a feedback request script in English and Hindi that is warm and easy to respond to.\n\nMy details:\n- Post Service Feedback Request – English & Hindi details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":71,"title":"Policy Renewal Reminder – English & Malay","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a renewal reminder that is polite, urgent, and clear. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Policy Renewal Reminder – English & Malay\"\n\nStarting brief:\nYou are an insurance retention specialist. Write a bilingual (English & Malay) policy renewal reminder that includes:\n\nBusiness context:\nA Singapore-based insurance company serves a sizeable Malay-speaking customer base across HDB heartlands. Without a bilingual renewal notice, customers risk policy lapse.\n\nDesired outcome:\nCreate a renewal reminder that is polite, urgent, and clear.\n\nMy details:\n- Policy Renewal Reminder – English & Malay details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":72,"title":"Loan Approval Notification – English & Mandarin","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a bilingual loan approval message that is celebratory and informative. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Loan Approval Notification – English & Mandarin\"\n\nStarting brief:\nYou are a loan services communication expert. Write a bilingual (English & Mandarin) loan approval message that includes:\n\nBusiness context:\nA Singapore-based licensed moneylender wants customers to feel valued at the approval stage. Many older customers prefer Mandarin and may miss details in English-only letters.\n\nDesired outcome:\nCreate a bilingual loan approval message that is celebratory and informative.\n\nMy details:\n- Loan Approval Notification – English & Mandarin details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":73,"title":"Subscription Cancellation Confirmation – English & Tamil","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Intermediate","explanation":"Create a polite cancellation confirmation that encourages re-subscription in the future. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Subscription Cancellation Confirmation – English & Tamil\"\n\nStarting brief:\nYou are a subscription lifecycle communication expert. Write a bilingual (English & Tamil) cancellation confirmation that includes:\n\nBusiness context:\nA Singapore-based streaming platform receives cancellation requests from Tamil-speaking customers. Without a bilingual confirmation, some think the process is incomplete and keep calling support.\n\nDesired outcome:\nCreate a polite cancellation confirmation that encourages re-subscription in the future.\n\nMy details:\n- Subscription Cancellation Confirmation – English & Tamil details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":74,"title":"Emergency Service Disruption Alert – English & Mandarin","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create an emergency disruption alert that is concise, clear, and reassuring. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Emergency Service Disruption Alert – English & Mandarin\"\n\nStarting brief:\nYou are a utility service communication officer. Write a bilingual (English & Mandarin) emergency water supply disruption alert that includes:\n\nBusiness context:\nA Singapore utility provider needs to inform residents about urgent water service cuts due to repairs. Mandarin-speaking residents, especially seniors in HDB estates, must get the same clear instructions as English speakers.\n\nDesired outcome:\nCreate an emergency disruption alert that is concise, clear, and reassuring.\n\nMy details:\n- Emergency Service Disruption Alert – English & Mandarin details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Affected area / block(s)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":75,"title":"Welcome Onboarding Script – English & Mandarin","category":"Customer Comms","source":"Admin & Ops","module":"Multilingual customer scripts","difficulty":"Beginner","explanation":"Create a warm, professional onboarding script in English and Mandarin for email and in-app pop-ups. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Welcome Onboarding Script – English & Mandarin\"\n\nStarting brief:\nYou are a user onboarding strategist. Write a bilingual (English & Mandarin) welcome message that includes:\n\nBusiness context:\nA Singapore-based wellness app wants to welcome new users warmly. A meaningful slice of users prefer Mandarin, so a bilingual onboarding ensures no one misses key features.\n\nDesired outcome:\nCreate a warm, professional onboarding script in English and Mandarin for email and in-app pop-ups.\n\nMy details:\n- Welcome Onboarding Script – English & Mandarin details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- User name\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":76,"title":"Call Center QA Checklist Creation","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Create a detailed call quality checklist for QA teams to use during monitoring. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Call Center QA Checklist Creation\"\n\nStarting brief:\nYou are a customer service quality consultant. Create a comprehensive call center QA checklist that includes:\n\nBusiness context:\nA large telecom company has a call center with over 200 agents handling billing, technical, and service upgrade queries. Customer churn has increased, and management suspects inconsistent call handling quality. They want to standardize evaluations so that every agent is scored fairly across communication skills, product knowledge, and resolution effectiveness.\n\nDesired outcome:\nCreate a detailed call quality checklist for QA teams to use during monitoring.\n\nMy details:\n- Call Center QA Checklist Creation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry type\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":77,"title":"Email Response Quality Audit Template","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Develop a scoring template for evaluating support emails. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Email Response Quality Audit Template\"\n\nStarting brief:\nYou are a service quality auditor. Create an email response quality scoring template including:\n\nBusiness context:\nA SaaS company receives 1,000+ customer support emails per week. While response times are good, customer satisfaction ratings suggest issues with clarity, tone, and completeness of email replies. Management wants a structured scoring sheet for email audits.\n\nDesired outcome:\nDevelop a scoring template for evaluating support emails.\n\nMy details:\n- Email Response Quality Audit Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":78,"title":"Live Chat Audit Guide","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Build a live chat quality evaluation guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Live Chat Audit Guide\"\n\nStarting brief:\nYou are a CX (Customer Experience) auditor. Create a live chat quality audit guide with parameters for:\n\nBusiness context:\nAn e-commerce marketplace uses live chat for customer queries. Agents tend to give quick responses, but not always complete ones, leading to repeated chats from the same customer. Management wants a quality audit framework that evaluates both speed and accuracy.\n\nDesired outcome:\nBuild a live chat quality evaluation guide.\n\nMy details:\n- Live Chat Audit Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry and chat platform\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":79,"title":"Service Visit Field Audit Checklist","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Create an on-site service quality checklist. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Service Visit Field Audit Checklist\"\n\nStarting brief:\nYou are a field service quality inspector. Develop an on-site service visit audit checklist covering:\n\nBusiness context:\nA home appliance repair company sends technicians to customer locations. Management suspects that some visits are rushed and lack thoroughness, leading to repeat complaints. They want a standardized field visit audit checklist.\n\nDesired outcome:\nCreate an on-site service quality checklist.\n\nMy details:\n- Service Visit Field Audit Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service type (repair/installation)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":80,"title":"First Contact Resolution (FCR) Audit Form","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Design an FCR audit form to capture key resolution metrics. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"First Contact Resolution (FCR) Audit Form\"\n\nStarting brief:\nYou are a metrics-driven service auditor. Create a First Contact Resolution (FCR) audit form including:\n\nBusiness context:\nA subscription box service wants to track how often customer issues are resolved in the first contact. Currently, they lack a formal metric to measure this, making it hard to improve agent performance.\n\nDesired outcome:\nDesign an FCR audit form to capture key resolution metrics.\n\nMy details:\n- First Contact Resolution (FCR) Audit Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Common customer issues\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":81,"title":"IVR Journey Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Evaluate the entire IVR journey for clarity, completion rate, compliance, and escalation availability. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"IVR Journey Quality Audit\"\n\nStarting brief:\nYou are a contact center QA consultant. Audit the IVR experience end-to-end.\n\nBusiness context:\nA Singapore-based D2C brand recently upgraded its IVR but call drop-offs have spiked during option selection. Customers complain they can't reach a human agent quickly, and the menu vocabulary confuses first-time callers. Leadership suspects misaligned menu logic and long sub-menu paths. They want a rigorous IVR audit to identify friction, dead ends, and noncompliant messages.\n\nDesired outcome:\nEvaluate the entire IVR journey for clarity, completion rate, compliance, and escalation availability.\n\nMy details:\n- IVR Journey Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current IVR call flows & audio scripts\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":82,"title":"Social Media Response Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Assess social care replies for tone, accuracy, completeness, and deflection effectiveness. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Social Media Response Quality Audit\"\n\nStarting brief:\nYou are a social CX auditor. Review a sample of social media interactions.\n\nBusiness context:\nA Singapore fintech sees rising X (Twitter) and Instagram queries but CSAT is lagging versus email and chat. Agents respond fast yet replies feel templated and miss key next steps, causing repeat posts. Brand wants tone alignment, accurate redirections, and lower public escalations. A structured social care audit is needed.\n\nDesired outcome:\nAssess social care replies for tone, accuracy, completeness, and deflection effectiveness.\n\nMy details:\n- Social Media Response Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sample posts/DMs with timestamps\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":83,"title":"Knowledge Base (KB) Accuracy & Findability Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Measure KB content quality, freshness, and search discoverability. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Knowledge Base (KB) Accuracy & Findability Audit\"\n\nStarting brief:\nYou are a service documentation auditor. Audit the KB for:\n\nBusiness context:\nAgents in a Singapore support hub at one-north complain that KB articles are outdated and hard to search. New hires over-rely on seniors, inflating handle times and errors. Customers report contradictory instructions between email and chat. Management needs a KB truth-source audit.\n\nDesired outcome:\nMeasure KB content quality, freshness, and search discoverability.\n\nMy details:\n- Knowledge Base (KB) Accuracy & Findability Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- KB export (titles\n- content\n- owners\n- last updated)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":84,"title":"CSAT/DSAT Post Interaction Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Correlate satisfaction outcomes with interaction attributes to find fixable drivers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"CSAT/DSAT Post Interaction Audit\"\n\nStarting brief:\nYou are a CX analytics auditor. Analyze survey and interaction data to:\n\nBusiness context:\nAlthough overall CSAT at a Singapore-based regional contact centre is stable, DSAT comments cite \"partial answers\" and \"no ownership.\" Ops suspects survey bias and tagging gaps. Leadership wants a forensic look linking DSAT reasons to agent behaviors and process issues.\n\nDesired outcome:\nCorrelate satisfaction outcomes with interaction attributes to find fixable drivers.\n\nMy details:\n- CSAT/DSAT Post Interaction Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Survey results (CSAT/NPS\n- comments)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":85,"title":"QA Calibration Workshop Pack","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Create a repeatable QA calibration process and toolkit. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"QA Calibration Workshop Pack\"\n\nStarting brief:\nYou are a QA enablement lead. Build a calibration pack:\n\nBusiness context:\nDifferent QA reviewers in a Singapore contact centre score the same calls differently, triggering agent distrust. Appeals are frequent and time-consuming. Leadership wants a calibration framework to align scoring and reduce variance.\n\nDesired outcome:\nCreate a repeatable QA calibration process and toolkit.\n\nMy details:\n- QA Calibration Workshop Pack details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current QA rubric & weightages\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":86,"title":"Speech Analytics Quality & Compliance Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Evaluate speech analytics performance vs. QA/compliance objectives. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Speech Analytics Quality & Compliance Audit\"\n\nStarting brief:\nYou are a speech analytics auditor. Review:\n\nBusiness context:\nA Singapore contact centre installed speech analytics but insights haven't improved QA outcomes. Agents don't trust keyword flags; compliance misses are still discovered manually. Management needs an audit to tighten model accuracy and governance.\n\nDesired outcome:\nEvaluate speech analytics performance vs. QA/compliance objectives.\n\nMy details:\n- Speech Analytics Quality & Compliance Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Model config (keywords\n- thresholds)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":87,"title":"Escalation Handling Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Assess escalation accuracy, communication, and recovery steps. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Escalation Handling Quality Audit\"\n\nStarting brief:\nYou are a tiered support auditor. Evaluate:\n\nBusiness context:\nEscalations at a Singapore e-commerce support team often jump straight to L3, bypassing L1/L2 fixes. Customers face long waits and repeat contacts. Senior leaders want gatekeeping quality and customer reassurance improved.\n\nDesired outcome:\nAssess escalation accuracy, communication, and recovery steps.\n\nMy details:\n- Escalation Handling Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Escalation SOPs & SLAs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":88,"title":"After Call Work (ACW) Documentation Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Improve completeness, clarity, and standardization of ACW notes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"After Call Work (ACW) Documentation Audit\"\n\nStarting brief:\nYou are a service documentation QA. Audit ACW notes for:\n\nBusiness context:\nSupervisors in a Singapore contact centre notice ACW notes are sparse, hurting handoffs and follow-ups. Duplicate work and customer re-explanations rise. Ops needs a documentation quality audit to set a higher bar.\n\nDesired outcome:\nImprove completeness, clarity, and standardization of ACW notes.\n\nMy details:\n- After Call Work (ACW) Documentation Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sample ACW logs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":89,"title":"Average Handle Time (AHT) vs. Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Audit AHT practices and propose a balanced metric model. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Average Handle Time (AHT) vs. Quality Audit\"\n\nStarting brief:\nYou are a CX metrics auditor. Analyze:\n\nBusiness context:\nTo hit aggressive AHT targets, agents at a Paya Lebar contact centre rush calls, causing DSAT growth. Leadership wants a balanced scorecard that rewards resolution quality, not speed alone.\n\nDesired outcome:\nAudit AHT practices and propose a balanced metric model.\n\nMy details:\n- Average Handle Time (AHT) vs. Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- AHT by queue/agent\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":90,"title":"Email/Chat Tone & Empathy Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Measure tone, empathy, and brand voice adherence; recommend improvements. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Email/Chat Tone & Empathy Audit\"\n\nStarting brief:\nYou are a communications QA specialist. Audit written interactions for:\n\nBusiness context:\nThough factual accuracy is decent, a Singapore-based SaaS support team headquartered in one-north gets feedback that replies feel \"robotic.\" Leaders want empathy without verbosity and consistent brand voice across agents.\n\nDesired outcome:\nMeasure tone, empathy, and brand voice adherence; recommend improvements.\n\nMy details:\n- Email/Chat Tone & Empathy Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sample emails/chats\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":91,"title":"Omnichannel Consistency Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Verify policy consistency and outcome parity across channels. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Omnichannel Consistency Audit\"\n\nStarting brief:\nYou are an omnichannel QA auditor.\n\nBusiness context:\nCustomers of a Singapore retailer with stores across Orchard, VivoCity, and Jewel Changi get different answers across phone, chat, and store counters. Refund rules and timelines vary by agent. The COO wants \"one truth\" regardless of channel.\n\nDesired outcome:\nVerify policy consistency and outcome parity across channels.\n\nMy details:\n- Omnichannel Consistency Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Policy set & KB links\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":92,"title":"Queue & Workforce Management Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Assess forecasting accuracy, staffing, and routing rules. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Queue & Workforce Management Audit\"\n\nStarting brief:\nYou are a WFM auditor. Analyze:\n\nBusiness context:\nA Tampines-based contact centre misses SLAs during peak hours despite spare capacity off-peak. Leaders suspect forecasting and scheduling inefficiencies. They need a WFM audit tied to service impact.\n\nDesired outcome:\nAssess forecasting accuracy, staffing, and routing rules.\n\nMy details:\n- Queue & Workforce Management Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Interval-level volume & AHT\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":93,"title":"Complaint Turnaround Time (TAT) & Resolution Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Audit complaint lifecycle for timeliness and fix effectiveness. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Complaint Turnaround Time (TAT) & Resolution Quality Audit\"\n\nStarting brief:\nYou are a complaints QA auditor. Review:\n\nBusiness context:\nRegulatory complaints in a Singapore fintech licensed by MAS must be resolved within strict timelines. TAT is met, but customers claim \"no real fix,\" triggering repeats. Compliance wants speed with substance.\n\nDesired outcome:\nAudit complaint lifecycle for timeliness and fix effectiveness.\n\nMy details:\n- Complaint Turnaround Time (TAT) & Resolution Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Complaint logs by severity\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":94,"title":"Data Privacy & PII Handling Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Verify privacy-by-design in customer interactions and systems. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Data Privacy & PII Handling Audit\"\n\nStarting brief:\nYou are a privacy compliance auditor.\n\nBusiness context:\nA Singapore health-tech startup based in one-north handles sensitive patient data and must comply with PDPA. Recordings and chat logs sometimes contain excess PII. Legal wants proof of robust redaction and least-privilege practices.\n\nDesired outcome:\nVerify privacy-by-design in customer interactions and systems.\n\nMy details:\n- Data Privacy & PII Handling Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Privacy policy & data map\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":95,"title":"Agent Coaching Effectiveness Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Audit coaching practices and tie them to performance outcomes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Agent Coaching Effectiveness Audit\"\n\nStarting brief:\nYou are a performance QA specialist.\n\nBusiness context:\nSupervisors run weekly huddles, yet QA scores plateau. Agents say coaching is \"generic\" and not tied to their actual calls. Leadership wants coaching to drive measurable uplift.\n\nDesired outcome:\nAudit coaching practices and tie them to performance outcomes.\n\nMy details:\n- Agent Coaching Effectiveness Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Coaching records & templates\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":96,"title":"First Response Quality (FRQ) Audit for Email/Chat","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Score first responses on utility, not just speed. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"First Response Quality (FRQ) Audit for Email/Chat\"\n\nStarting brief:\nYou are a service quality auditor.\n\nBusiness context:\nA Singapore-based marketplace meets first response SLA but customers still recontact for clarity. Leaders suspect the first reply acknowledges but doesn't advance resolution. They want FRQ measured beyond time.\n\nDesired outcome:\nScore first responses on utility, not just speed.\n\nMy details:\n- First Response Quality (FRQ) Audit for Email/Chat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- First-reply samples with timestamps\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":97,"title":"Accessibility & Inclusivity Audit (Language/Disability)","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Ensure interactions meet accessibility standards and language inclusivity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Accessibility & Inclusivity Audit (Language/Disability)\"\n\nStarting brief:\nYou are an accessibility auditor.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nEnsure interactions meet accessibility standards and language inclusivity.\n\nMy details:\n- Accessibility & Inclusivity Audit (Language/Disability) details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Samples across channels (email\n- chat\n- app, IVR)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":98,"title":"Proactive Notifications Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Audit outbound notices for clarity, personalization, and call-deflection. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Proactive Notifications Quality Audit\"\n\nStarting brief:\nYou are a proactive CX auditor.\n\nBusiness context:\nA logistics firm sends outage and delay alerts, yet customers still call asking \"what now?\" Messages lack next steps and personalization. Ops wants proactive comms that actually deflect calls.\n\nDesired outcome:\nAudit outbound notices for clarity, personalization, and call-deflection.\n\nMy details:\n- Proactive Notifications Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Outbound message samples & send logs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":99,"title":"Bot & Automation Quality Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Advanced","explanation":"Evaluate conversation coverage, accuracy, and handoff quality. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Bot & Automation Quality Audit\"\n\nStarting brief:\nYou are a conversational AI auditor.\n\nBusiness context:\nA Singapore EdTech's chatbot handles 40% of queries but NPS dips when the bot loops or dead-ends. Handoffs to humans lack context, frustrating customers. Leadership wants a bot QA audit.\n\nDesired outcome:\nEvaluate conversation coverage, accuracy, and handoff quality.\n\nMy details:\n- Bot & Automation Quality Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Bot transcripts & intent analytics\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":100,"title":"Root Cause Analysis (RCA) & Continuous Improvement Audit","category":"Customer Comms","source":"Admin & Ops","module":"Service quality audits","difficulty":"Intermediate","explanation":"Audit RCA depth, actionability, and follow-through. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Root Cause Analysis (RCA) & Continuous Improvement Audit\"\n\nStarting brief:\nYou are a continuous improvement auditor.\n\nBusiness context:\nA Singapore insurer runs monthly RCAs but the same issues recur (address updates, premium reversals). Fixes seem tactical, not systemic. The COO wants durable improvements with owners and deadlines.\n\nDesired outcome:\nAudit RCA depth, actionability, and follow-through.\n\nMy details:\n- Root Cause Analysis (RCA) & Continuous Improvement Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- RCA reports (last 6–12 months)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":101,"title":"Onboarding Guide for New Support Agents","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a comprehensive onboarding training guide for new support agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Onboarding Guide for New Support Agents\"\n\nStarting brief:\n\"You are a customer support training manager. Create a detailed onboarding training guide for new agents that includes:\n\nBusiness context:\nA mid-sized SaaS company has grown its support team from 10 to 40 agents in the last year. Many new hires have no prior experience in customer support, leading to inconsistent communication styles and knowledge gaps. Management wants a structured onboarding guide to quickly bring agents up to speed on company policies, tools, and customer interaction standards.\n\nDesired outcome:\nCreate a comprehensive onboarding training guide for new support agents.\n\nMy details:\n- Onboarding Guide for New Support Agents details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company profile and mission statement\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":102,"title":"Product Knowledge Training Module","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a product knowledge training module for customer support agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Product Knowledge Training Module\"\n\nStarting brief:\n\"You are a training content developer. Create a product knowledge training module for customer support agents that includes:\n\nBusiness context:\nAn electronics retailer found that many agents give vague or incorrect answers about product specifications. This not only confuses customers but also results in higher product returns. The company needs a focused training module to improve product knowledge retention among support staff.\n\nDesired outcome:\nDevelop a product knowledge training module for customer support agents.\n\nMy details:\n- Product Knowledge Training Module details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product list with specifications\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":103,"title":"Difficult Customer Handling Playbook","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a handling guide for interactions with frustrated or angry customers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Difficult Customer Handling Playbook\"\n\nStarting brief:\n\"You are a customer conflict resolution trainer. Create a detailed playbook for handling difficult customers that includes:\n\nBusiness context:\nA financial services call center deals with clients who are often stressed due to account issues or payment delays. Some agents tend to get defensive, which escalates situations. The company needs a playbook that teaches agents how to remain calm, empathize, and resolve issues without losing control of the conversation.\n\nDesired outcome:\nCreate a handling guide for interactions with frustrated or angry customers.\n\nMy details:\n- Difficult Customer Handling Playbook details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of top complaint types\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":104,"title":"Escalation Process Training Guide","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a clear escalation process training guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Escalation Process Training Guide\"\n\nStarting brief:\n\"You are a service process consultant. Create an escalation process training guide for agents that covers:\n\nBusiness context:\nA tech company's support team has inconsistent escalation practices—some agents escalate too early, others too late. This creates delays in issue resolution and affects customer satisfaction scores. A formal training document is needed to define when and how escalations should happen.\n\nDesired outcome:\nDevelop a clear escalation process training guide.\n\nMy details:\n- Escalation Process Training Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Escalation tier chart\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":105,"title":"Cross Selling & Upselling Script Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Design a cross-selling and upselling training module. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cross Selling & Upselling Script Training\"\n\nStarting brief:\n\"You are a sales-in-service coach. Create a cross-selling/upselling training module for agents that includes:\n\nBusiness context:\nAn online insurance company wants agents to identify opportunities to offer upgrades and additional products during routine service calls. Currently, attempts feel pushy and lead to low conversion rates. The company needs training that teaches subtle, value-driven sales techniques integrated into support conversations.\n\nDesired outcome:\nDesign a cross-selling and upselling training module.\n\nMy details:\n- Cross Selling & Upselling Script Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of products/services for cross-sell\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":106,"title":"Remote Agent Communication Skills Training","category":"Email & Writing","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a training guide for communication best practices for remote agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Remote Agent Communication Skills Training\"\n\nStarting brief:\n\"You are a remote work communication coach. Develop a training guide for remote agents that includes:\n\nBusiness context:\nA hybrid contact center has agents working both on-site and remotely. Managers have noticed remote agents sometimes struggle to maintain professional tone and consistent communication styles without in-person supervision. The company wants a dedicated communication skills guide for remote teams.\n\nDesired outcome:\nCreate a training guide for communication best practices for remote agents.\n\nMy details:\n- Remote Agent Communication Skills Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of internal communication tools\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":107,"title":"Data Privacy & Compliance Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Advanced","explanation":"Build a compliance-focused training module for data privacy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Data Privacy & Compliance Training\"\n\nStarting brief:\n\"You are a compliance training specialist. Create a data privacy and compliance training module for customer support agents that includes:\n\nBusiness context:\nA healthcare customer support team handles sensitive patient information daily. With growing concerns around data breaches, management wants a training module that ensures every agent knows the rules, follows HIPAA-equivalent protocols, and avoids common security mistakes.\n\nDesired outcome:\nBuild a compliance-focused training module for data privacy.\n\nMy details:\n- Data Privacy & Compliance Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry-specific compliance standards\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":108,"title":"Soft Skills & Empathy Development Workshop","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a soft skills and empathy training workshop plan. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Soft Skills & Empathy Development Workshop\"\n\nStarting brief:\n\"You are a hospitality training expert. Design a workshop for soft skills and empathy development including:\n\nBusiness context:\nA luxury hotel chain values emotional connection with guests, but some agents rely too heavily on scripted lines, making interactions sound robotic. Management wants a workshop that helps agents develop genuine empathy and adaptability in conversations.\n\nDesired outcome:\nCreate a soft skills and empathy training workshop plan.\n\nMy details:\n- Soft Skills & Empathy Development Workshop details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Example customer scenarios from past cases\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":109,"title":"Knowledge Base Usage Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a knowledge base usage training manual. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Knowledge Base Usage Training\"\n\nStarting brief:\n\"You are an instructional designer. Create a training manual for knowledge base usage that includes:\n\nBusiness context:\nA subscription software company invested heavily in an internal knowledge base, but agents rarely use it during calls, leading to inconsistent answers. Management wants training that teaches agents how to quickly find and share accurate information from the system.\n\nDesired outcome:\nDevelop a knowledge base usage training manual.\n\nMy details:\n- Knowledge Base Usage Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Access to current KB system\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":110,"title":"Call Flow Mastery Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Advanced","explanation":"Create a call flow mastery training session. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Call Flow Mastery Training\"\n\nStarting brief:\n\"You are a process training consultant. Create a training session plan for mastering call flow, covering:\n\nBusiness context:\nA large retail chain uses a structured call flow to ensure consistency, but new agents often skip or reorder steps. This causes confusion and impacts customer satisfaction. Management wants a refresher training focused on mastering the official call flow structure.\n\nDesired outcome:\nCreate a call flow mastery training session.\n\nMy details:\n- Call Flow Mastery Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Official call flow chart\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":111,"title":"Handling Multiple Chat Conversations Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a multitasking training module for live chat agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Handling Multiple Chat Conversations Training\"\n\nStarting brief:\n\"You are a live chat operations trainer. Create a training module for handling multiple simultaneous chats that covers:\n\nBusiness context:\nA fashion e-commerce site allows agents to handle up to 5 live chat windows at once. New agents are finding it overwhelming to balance speed with quality, resulting in dropped chats and unsatisfied customers. Management needs a training plan that teaches multitasking without compromising service quality.\n\nDesired outcome:\nDevelop a multitasking training module for live chat agents.\n\nMy details:\n- Handling Multiple Chat Conversations Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Average concurrent chat count per agent\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":112,"title":"Email Support Excellence Guide","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a training guide for high-quality email responses. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Email Support Excellence Guide\"\n\nStarting brief:\n\"You are a customer email communication expert. Create a training guide for email support that includes:\n\nBusiness context:\nAn online education platform receives hundreds of email queries daily. Customers often complain about slow replies and impersonal responses. The company wants a guide that helps agents write clear, empathetic, and concise responses that maintain brand voice.\n\nDesired outcome:\nCreate a training guide for high-quality email responses.\n\nMy details:\n- Email Support Excellence Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Brand tone guide\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":113,"title":"Time Management for Support Agents","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Build a time management training guide for support teams. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Time Management for Support Agents\"\n\nStarting brief:\n\"You are a productivity coach. Create a time management training program for support agents that includes:\n\nBusiness context:\nA telecom provider's agents often struggle with balancing long call durations and pending backlogs. Without proper time management skills, cases pile up, increasing stress and lowering customer satisfaction. The leadership team wants a training program to improve daily workflow efficiency.\n\nDesired outcome:\nBuild a time management training guide for support teams.\n\nMy details:\n- Time Management for Support Agents details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Average ticket/call volumes\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":114,"title":"Cross Department Collaboration Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a collaboration skills training program for agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cross Department Collaboration Training\"\n\nStarting brief:\n\"You are a workplace collaboration trainer. Create a training program for cross-department coordination that covers:\n\nBusiness context:\nA subscription box company requires support agents to frequently coordinate with logistics, marketing, and product teams. Miscommunication often leads to delays and customer dissatisfaction. They need a training module that improves cross-department collaboration skills.\n\nDesired outcome:\nDevelop a collaboration skills training program for agents.\n\nMy details:\n- Cross Department Collaboration Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of departments and key contacts\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":115,"title":"Handling Service Interruptions Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a crisis communication training guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Handling Service Interruptions Training\"\n\nStarting brief:\n\"You are a crisis management trainer. Create a protocol for agents during service interruptions that includes:\n\nBusiness context:\nDuring a nationwide outage of a cloud service, customer support lines flooded with calls. Some agents panicked, giving inconsistent updates, which worsened customer frustration. Management wants a training protocol for handling such crises calmly and consistently.\n\nDesired outcome:\nCreate a crisis communication training guide.\n\nMy details:\n- Handling Service Interruptions Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Crisis communication chain of command\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":116,"title":"AI Tool Integration Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Advanced","explanation":"Develop a training module for AI-assisted customer service. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"AI Tool Integration Training\"\n\nStarting brief:\n\"You are a digital tools trainer. Create a training module for integrating AI tools into customer support that covers:\n\nBusiness context:\nA growing startup has introduced AI chat assistance for agents to speed up responses. However, some agents misuse it, relying entirely on AI outputs without verifying accuracy. The company needs training on integrating AI tools into daily workflows responsibly.\n\nDesired outcome:\nDevelop a training module for AI-assisted customer service.\n\nMy details:\n- AI Tool Integration Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- AI tools in use\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":117,"title":"Call Recording Review & Feedback Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Build a positive call review training program. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Call Recording Review & Feedback Training\"\n\nStarting brief:\n\"You are a quality assurance trainer. Create a guide for call recording reviews that includes:\n\nBusiness context:\nA fintech company records all customer calls for quality checks, but most agents see reviews as punitive rather than developmental. Management wants training on using call recordings constructively to improve performance.\n\nDesired outcome:\nBuild a positive call review training program.\n\nMy details:\n- Call Recording Review & Feedback Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Call scoring criteria\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":118,"title":"Stress Management Workshop","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a stress management workshop tailored for support teams. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Stress Management Workshop\"\n\nStarting brief:\n\"You are a workplace wellness coach. Create a stress management workshop plan that includes:\n\nBusiness context:\nSupport agents in a high-volume environment report burnout and emotional fatigue. Without stress management skills, absenteeism rises, and morale drops. The company wants a workshop that equips agents to handle pressure healthily.\n\nDesired outcome:\nCreate a stress management workshop tailored for support teams.\n\nMy details:\n- Stress Management Workshop details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Average daily ticket volume per agent\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":119,"title":"Cultural Sensitivity Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a cultural sensitivity guide for agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cultural Sensitivity Training\"\n\nStarting brief:\n\"You are a cross-cultural communication trainer. Create a cultural sensitivity training module that covers:\n\nBusiness context:\nAn airline serves a global customer base, but some agents unintentionally use phrases or gestures that offend certain cultures. The company needs cultural sensitivity training to avoid misunderstandings and strengthen global relationships.\n\nDesired outcome:\nDevelop a cultural sensitivity guide for agents.\n\nMy details:\n- Cultural Sensitivity Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of customer regions served\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":120,"title":"Service Recovery Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Build a service recovery training plan. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Service Recovery Training\"\n\nStarting brief:\n\"You are a customer retention strategist. Create a service recovery training guide that includes:\n\nBusiness context:\nA subscription meal service occasionally misses deliveries or sends incorrect orders. Agents need training on turning these negative experiences into loyalty-building opportunities.\n\nDesired outcome:\nBuild a service recovery training plan.\n\nMy details:\n- Service Recovery Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Common service failure scenarios\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":121,"title":"Conflict De escalation Masterclass","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a de-escalation masterclass guide for support agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Conflict De escalation Masterclass\"\n\nStarting brief:\n\"You are a conflict resolution coach. Design a masterclass training for agents that covers:\n\nBusiness context:\nA home services platform often receives calls from frustrated customers who have faced multiple service delays. Some agents inadvertently escalate situations by sounding defensive or dismissive. Leadership wants a masterclass training that equips agents with de-escalation skills to turn heated calls into constructive problem-solving conversations.\n\nDesired outcome:\nCreate a de-escalation masterclass guide for support agents.\n\nMy details:\n- Conflict De escalation Masterclass details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of frequent conflict triggers\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":122,"title":"First Call Resolution Skills Training","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop a training program to improve first-call resolution rates. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"First Call Resolution Skills Training\"\n\nStarting brief:\n\"You are a customer service efficiency consultant. Create a training guide that includes:\n\nBusiness context:\nAn insurance company has noticed repeat calls from the same customers because issues aren't being resolved on the first attempt. This wastes time and frustrates clients. The management wants a training module focused on achieving first-call resolution without compromising accuracy.\n\nDesired outcome:\nDevelop a training program to improve first-call resolution rates.\n\nMy details:\n- First Call Resolution Skills Training details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current first-call resolution percentage\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":123,"title":"Soft Skills for Difficult Customers","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Create a soft skills training guide for dealing with difficult customers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Soft Skills for Difficult Customers\"\n\nStarting brief:\n\"You are a hospitality soft skills trainer. Develop a training program that covers:\n\nBusiness context:\nA luxury travel agency serves high-net-worth clients who expect top-tier service. Even minor inconveniences can lead to dissatisfaction. Agents must have impeccable soft skills to handle demanding customers without compromising the brand image.\n\nDesired outcome:\nCreate a soft skills training guide for dealing with difficult customers.\n\nMy details:\n- Soft Skills for Difficult Customers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Brand's tone-of-voice guide\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":124,"title":"Remote Agent Work Best Practices","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Advanced","explanation":"Design a best practices guide for remote customer support agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Agent Work Best Practices\"\n\nStarting brief:\n\"You are a remote work consultant. Create a training manual for remote support agents that includes:\n\nBusiness context:\nSince moving to a remote work model, a tech support team struggles with consistency in response times and collaboration. Some agents also face distractions at home, lowering productivity. The company needs a training guide for remote work efficiency tailored to support roles.\n\nDesired outcome:\nDesign a best practices guide for remote customer support agents.\n\nMy details:\n- Remote Agent Work Best Practices details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of collaboration tools used\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":125,"title":"Upskilling Program for Experienced Agents","category":"Customer Comms","source":"Admin & Ops","module":"Training guides for agents","difficulty":"Intermediate","explanation":"Develop an upskilling program for seasoned customer support agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Upskilling Program for Experienced Agents\"\n\nStarting brief:\n\"You are a corporate training designer. Create an upskilling program that includes:\n\nBusiness context:\nA BPO has agents who have been in their roles for over 5 years. While experienced, their skills haven't evolved to match newer technologies and customer expectations. Management wants an upskilling program to refresh and expand their capabilities.\n\nDesired outcome:\nDevelop an upskilling program for seasoned customer support agents.\n\nMy details:\n- Upskilling Program for Experienced Agents details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current skill assessment reports\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":126,"title":"Transportation Cost Efficiency Report","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Analyse transportation costs, identify inefficiencies, and recommend cost-saving measures. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Transportation Cost Efficiency Report\"\n\nStarting brief:\nYou are a Supply Chain Cost Analyst. Create a transportation cost efficiency report for a distributor with 50 trucks serving 120 cities.\n\nBusiness context:\nA nationwide food distributor operates a fleet of 50 trucks delivering to 120 cities. Rising fuel prices have increased transportation costs by 18% in the last year. Management suspects that inefficient route planning and underutilized truck capacity are driving costs higher. They want a comprehensive cost efficiency report to identify cost drivers and recommend optimization strategies.\n\nDesired outcome:\nAnalyse transportation costs, identify inefficiencies, and recommend cost-saving measures.\n\nMy details:\n- Transportation Cost Efficiency Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Delivery route list with distances\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":127,"title":"Warehouse Operations Cost Audit","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Identify warehouse cost inefficiencies and propose automation-driven savings. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Warehouse Operations Cost Audit\"\n\nStarting brief:\nYou are a Logistics Efficiency Consultant. Conduct a warehouse operations cost audit for 4 locations across Singapore.\n\nBusiness context:\nA retail chain operates 4 warehouses across Singapore (Tuas, Jurong, Changi, and Woodlands). Over the past year, warehouse operational costs have increased by 25%, with electricity, labour, and storage being the biggest contributors. Management wants to understand the cost structure and find areas for automation or process improvement without disrupting operations.\n\nDesired outcome:\nIdentify warehouse cost inefficiencies and propose automation-driven savings.\n\nMy details:\n- Warehouse Operations Cost Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly warehouse cost breakdown (S$)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":128,"title":"Supplier Cost Comparison Report","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Compare supplier pricing and negotiate standardized rates. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Supplier Cost Comparison Report\"\n\nStarting brief:\nYou are a Procurement Cost Analyst. Prepare a supplier cost comparison report for 15 vendors.\n\nBusiness context:\nA manufacturing company works with 15 suppliers for raw materials. Procurement is decentralized, and different plants pay different rates for the same materials. The CFO suspects overpaying due to lack of consolidated data. They need a supplier cost comparison report to identify cost disparities and standardize pricing.\n\nDesired outcome:\nCompare supplier pricing and negotiate standardized rates.\n\nMy details:\n- Supplier Cost Comparison Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Material master list\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":129,"title":"Inventory Holding Cost Analysis","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Calculate holding costs and recommend optimal inventory levels. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Inventory Holding Cost Analysis\"\n\nStarting brief:\nYou are an Inventory Cost Specialist. Perform a holding cost analysis for a furniture retailer.\n\nBusiness context:\nA furniture retailer stocks large items in a central warehouse. Inventory holding costs, including rent, insurance, and capital lock-in, have increased significantly. Some slow-moving items are occupying prime space for months. Management wants a holding cost analysis to determine optimal stock levels.\n\nDesired outcome:\nCalculate holding costs and recommend optimal inventory levels.\n\nMy details:\n- Inventory Holding Cost Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU stock levels and turnover rates\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":130,"title":"Last Mile Delivery Cost Efficiency","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Reduce last-mile delivery costs without affecting service quality. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Last Mile Delivery Cost Efficiency\"\n\nStarting brief:\nYou are a Logistics Cost Reduction Consultant. Prepare a last-mile delivery cost efficiency report for an online grocery service.\n\nBusiness context:\nAn online grocery delivery service offers same-day delivery. While customer satisfaction is high, last-mile delivery costs are eating into profit margins. The operations team wants a cost efficiency report to explore options like delivery slot optimization, batch deliveries, or micro-fulfillment centers.\n\nDesired outcome:\nReduce last-mile delivery costs without affecting service quality.\n\nMy details:\n- Last Mile Delivery Cost Efficiency details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Delivery cost breakdown per order\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":131,"title":"Production Cost Breakdown & Optimization","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Identify and reduce production cost inefficiencies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Production Cost Breakdown & Optimization\"\n\nStarting brief:\nYou are a Manufacturing Cost Analyst. Create a production cost breakdown report for an electronics manufacturer.\n\nBusiness context:\nA mid-sized electronics manufacturer is struggling to maintain profit margins despite steady sales. Management suspects inefficiencies in production cost allocation, especially in assembly and quality testing stages. They need a cost breakdown and actionable recommendations to optimize operations without compromising product quality.\n\nDesired outcome:\nIdentify and reduce production cost inefficiencies.\n\nMy details:\n- Production Cost Breakdown & Optimization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Production cost ledger\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":132,"title":"Procurement Cost vs. Market Price Analysis","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Identify overpriced procurement items and prepare for supplier negotiations. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Procurement Cost vs. Market Price Analysis\"\n\nStarting brief:\nYou are a Procurement Analyst. Prepare a cost vs. market price comparison for all raw materials purchased in the last year.\n\nBusiness context:\nA large FMCG company suspects it is overpaying for certain raw materials compared to market rates. They want a procurement cost analysis that benchmarks their current supplier prices against real-time market averages and historical trends to inform negotiation strategy.\n\nDesired outcome:\nIdentify overpriced procurement items and prepare for supplier negotiations.\n\nMy details:\n- Procurement Cost vs. Market Price Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase records (item\n- price\n- supplier)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":133,"title":"Energy Efficiency & Cost Reduction Report","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Identify energy wastage and recommend cost-effective solutions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Energy Efficiency & Cost Reduction Report\"\n\nStarting brief:\nYou are an Energy Cost Optimization Specialist. Prepare an energy efficiency report for a manufacturing plant.\n\nBusiness context:\nA manufacturing plant's monthly electricity bill has doubled over two years due to outdated machinery and poor energy management. The sustainability team wants an energy efficiency cost reduction report to secure budget approval for green upgrades.\n\nDesired outcome:\nIdentify energy wastage and recommend cost-effective solutions.\n\nMy details:\n- Energy Efficiency & Cost Reduction Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly electricity consumption per machine\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":134,"title":"Freight Cost Benchmarking","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Benchmark freight costs and recommend cost optimization strategies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Freight Cost Benchmarking\"\n\nStarting brief:\nYou are a Freight Cost Analyst. Create a benchmarking report for an exporter using multiple forwarders.\n\nBusiness context:\nA global exporter ships products to multiple regions and uses various freight forwarders. Freight costs have become unpredictable, and the logistics manager wants a benchmarking report to identify cost variations across forwarders, routes, and shipment sizes.\n\nDesired outcome:\nBenchmark freight costs and recommend cost optimization strategies.\n\nMy details:\n- Freight Cost Benchmarking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Freight invoices (last 12 months)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":135,"title":"Cross Department Cost Allocation Report","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Create a fair and transparent cost allocation framework. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cross Department Cost Allocation Report\"\n\nStarting brief:\nYou are a Financial Controller. Prepare a cost allocation report for shared services across departments.\n\nBusiness context:\nA diversified company with manufacturing, sales, and R&D divisions struggles with fair cost allocation. Some departments claim they're unfairly charged for shared resources like IT support, utilities, and admin staff. The CFO wants a transparent, data-backed allocation model.\n\nDesired outcome:\nCreate a fair and transparent cost allocation framework.\n\nMy details:\n- Cross Department Cost Allocation Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Department-wise usage data for shared resources\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":136,"title":"Warehouse Cost Efficiency Audit","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Assess warehouse operations to reduce storage and handling costs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Warehouse Cost Efficiency Audit\"\n\nStarting brief:\nYou are a Warehouse Efficiency Auditor. Conduct a cost audit for a retail chain's warehouses.\n\nBusiness context:\nA retail chain operates multiple regional warehouses, but storage and handling costs have been rising faster than sales. The operations head suspects inefficient space usage, overstaffing, and outdated handling processes. They need a comprehensive warehouse cost audit to identify savings opportunities.\n\nDesired outcome:\nAssess warehouse operations to reduce storage and handling costs.\n\nMy details:\n- Warehouse Cost Efficiency Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Warehouse floor plans and capacity data\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":137,"title":"Supplier Contract Cost Impact Analysis","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Evaluate the cost implications of long-term supplier contracts. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Supplier Contract Cost Impact Analysis\"\n\nStarting brief:\nYou are a Procurement Cost Strategist. Analyze the cost impact of long-term supplier contracts versus short-term procurement.\n\nBusiness context:\nA mid-tier manufacturer recently signed long-term contracts with multiple suppliers. While stable supply is assured, the finance team wants to understand the total cost impact of these deals compared to shorter-term sourcing.\n\nDesired outcome:\nEvaluate the cost implications of long-term supplier contracts.\n\nMy details:\n- Supplier Contract Cost Impact Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Supplier contract terms and pricing\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":138,"title":"Packaging Cost Efficiency Study","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Find cost-effective packaging solutions that maintain quality and branding. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Packaging Cost Efficiency Study\"\n\nStarting brief:\nYou are a Packaging Cost Analyst. Evaluate packaging material costs, supplier options, and alternative designs for a beverage company.\n\nBusiness context:\nA beverage company wants to cut packaging costs without harming product shelf life or brand appeal. The marketing and operations teams are debating over design changes, but need a cost efficiency study with clear data.\n\nDesired outcome:\nFind cost-effective packaging solutions that maintain quality and branding.\n\nMy details:\n- Packaging Cost Efficiency Study details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current packaging specifications\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":139,"title":"Overtime & Labor Cost Review","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Identify causes of excessive overtime and propose solutions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Overtime & Labor Cost Review\"\n\nStarting brief:\nYou are a Labor Cost Analyst. Review overtime trends and labor allocation for a manufacturing unit.\n\nBusiness context:\nA manufacturing unit has seen a steady rise in overtime payments over the past six months. The HR and production teams suspect poor shift planning is driving unnecessary labor costs.\n\nDesired outcome:\nIdentify causes of excessive overtime and propose solutions.\n\nMy details:\n- Overtime & Labor Cost Review details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Overtime payroll data\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":140,"title":"Maintenance Cost vs. Replacement Analysis","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Determine when to replace vs. repair assets for cost efficiency. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Maintenance Cost vs. Replacement Analysis\"\n\nStarting brief:\nYou are an Asset Management Analyst. Compare the total maintenance costs of vehicles/equipment to the cost of replacing them.\n\nBusiness context:\nA logistics firm spends heavily on vehicle and equipment maintenance. Management wants to compare the cost of ongoing repairs with the cost of replacing older assets.\n\nDesired outcome:\nDetermine when to replace vs. repair assets for cost efficiency.\n\nMy details:\n- Maintenance Cost vs. Replacement Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Maintenance logs and repair costs\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":141,"title":"Energy Cost Reduction Plan","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Create a cost-reduction strategy focused on energy efficiency. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Energy Cost Reduction Plan\"\n\nStarting brief:\nYou are an Energy Cost Analyst. Evaluate the current power consumption of a cold storage facility.\n\nBusiness context:\nA large cold storage facility has seen its electricity bills spike due to increasing energy tariffs and outdated cooling systems. The management team wants a detailed plan to cut energy costs while maintaining required storage conditions for perishable goods.\n\nDesired outcome:\nCreate a cost-reduction strategy focused on energy efficiency.\n\nMy details:\n- Energy Cost Reduction Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly electricity bills (12 months)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":142,"title":"Freight Cost vs. Delivery Time Analysis","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Find the optimal trade-off between delivery time and cost. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Freight Cost vs. Delivery Time Analysis\"\n\nStarting brief:\nYou are a Freight Optimization Analyst. Compare the cost and customer satisfaction impact of different delivery speed options.\n\nBusiness context:\nAn e-commerce brand is trying to balance delivery speed with shipping costs. Customers demand faster deliveries, but expedited shipping has significantly increased freight expenses.\n\nDesired outcome:\nFind the optimal trade-off between delivery time and cost.\n\nMy details:\n- Freight Cost vs. Delivery Time Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Freight cost breakdown by delivery type\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":143,"title":"Procurement Cost Leak Detection","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Identify hidden procurement cost leaks and suggest prevention measures. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Procurement Cost Leak Detection\"\n\nStarting brief:\nYou are a Procurement Audit Specialist. Conduct a detailed review of supplier invoices and purchase orders.\n\nBusiness context:\nA mid-size electronics retailer suspects small but consistent cost leaks in procurement due to invoice mismatches and unverified supplier charges. They want a forensic-style review to pinpoint losses.\n\nDesired outcome:\nIdentify hidden procurement cost leaks and suggest prevention measures.\n\nMy details:\n- Procurement Cost Leak Detection details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Supplier invoices (last 6 months)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":144,"title":"Multi Warehouse Cost Allocation Model","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Develop a cost allocation model for multi-warehouse operations. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Multi Warehouse Cost Allocation Model\"\n\nStarting brief:\nYou are a Logistics Cost Planner. Create a cost allocation model for three warehouses.\n\nBusiness context:\nA distributor operates three warehouses across Singapore (Tuas, Jurong, and Changi) but struggles to allocate operational costs fairly. Management wants a transparent model that accounts for both fixed and variable costs.\n\nDesired outcome:\nDevelop a cost allocation model for multi-warehouse operations.\n\nMy details:\n- Multi Warehouse Cost Allocation Model details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly cost data per warehouse\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":145,"title":"Cost Impact of Stockouts","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Calculate the full cost of stockouts and identify reduction strategies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cost Impact of Stockouts\"\n\nStarting brief:\nYou are a Supply Chain Cost Analyst. Calculate the cost of stockouts for key products.\n\nBusiness context:\nA consumer goods company experiences periodic stockouts of fast-moving items, leading to lost sales and emergency restocking costs. They want to quantify the total cost impact of stockouts.\n\nDesired outcome:\nCalculate the full cost of stockouts and identify reduction strategies.\n\nMy details:\n- Cost Impact of Stockouts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales data for out-of-stock products\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":146,"title":"End to End Logistics Cost Breakdown for an E commerce Company","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Prepare a comprehensive cost breakdown and efficiency report for the logistics process from warehouse to customer. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"End to End Logistics Cost Breakdown for an E commerce Company\"\n\nStarting brief:\n\"You are a supply chain analyst. Prepare an end-to-end logistics cost breakdown report for a Singapore-based e-commerce company covering: warehousing costs, first-mile, middle-mile, and last-mile delivery costs, reverse logistics expenses, packaging costs, fuel and ERP/toll charges, and 3PL partner fees. Include efficiency KPIs such as cost per shipment, delivery time variance, and return-to-origin (RTO) rates. Provide both tabular and visual charts.\"\n\nBusiness context:\nA mid-sized e-commerce company headquartered in Singapore delivers across the island and into select Southeast Asian markets using a hybrid logistics model — an in-house fleet for the central business district and densely populated HDB heartlands, and 3PL (third-party logistics) partners for cross-border deliveries to Malaysia and Indonesia. The CFO suspects that last-mile delivery costs are eating into profits, but lacks a clear, visual breakdown of expenses.\n\nDesired outcome:\nPrepare a comprehensive cost breakdown and efficiency report for the logistics process from warehouse to customer.\n\nMy details:\n- End to End Logistics Cost Breakdown for an E commerce Company details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":147,"title":"Warehouse Operations Cost vs. Efficiency Benchmarking","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Advanced","explanation":"Analyze warehouse operational costs and benchmark efficiency against industry standards. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Warehouse Operations Cost vs. Efficiency Benchmarking\"\n\nStarting brief:\n\"You are a warehouse performance consultant. Create a cost and efficiency benchmarking report covering: storage costs per square foot, labor cost per unit handled, picking and packing time per order, inventory accuracy rate, and cost per SKU stored. Include a gap analysis comparing the company's metrics to industry benchmarks and recommend actionable cost-saving strategies.\"\n\nBusiness context:\nA consumer electronics distributor in Singapore operates three warehouses (Tuas, Jurong, and Changi) supporting both local and regional Southeast Asian distribution. Management wants to compare their operational costs and productivity metrics against industry benchmarks to identify where automation or process improvements can cut costs.\n\nDesired outcome:\nAnalyze warehouse operational costs and benchmark efficiency against industry standards.\n\nMy details:\n- Warehouse Operations Cost vs. Efficiency Benchmarking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":148,"title":"Transportation Mode Cost Efficiency Analysis","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Determine the most cost-efficient transport mode mix while balancing delivery timelines. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Transportation Mode Cost Efficiency Analysis\"\n\nStarting brief:\n\"You are a logistics cost optimization expert. Prepare a cost-efficiency analysis comparing road, sea, and air transportation for FMCG distribution from Singapore to regional Southeast Asian markets. Include cost per ton-km, transit time, reliability scores, fuel surcharges, and seasonal price fluctuations. Recommend the optimal mode mix for different order urgency levels and destinations.\"\n\nBusiness context:\nAn FMCG company headquartered in Singapore distributes products across Southeast Asia using a mix of road (cross-border trucking via Tuas and Woodlands checkpoints), sea freight, and air transport. The supply chain head suspects that air shipments for urgent orders are driving up costs without significant ROI.\n\nDesired outcome:\nDetermine the most cost-efficient transport mode mix while balancing delivery timelines.\n\nMy details:\n- Transportation Mode Cost Efficiency Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":149,"title":"Supplier Procurement Cost Variance Report","category":"Excel & Data","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Analyze procurement costs over time and detect efficiency gaps. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Supplier Procurement Cost Variance Report\"\n\nStarting brief:\n\"You are a procurement cost analyst. Create a supplier cost variance report showing: price changes per supplier over the past 12 months, variance percentage, supplier reliability index, and potential cost savings from consolidation or renegotiation. Include visual dashboards to highlight trends and outliers.\"\n\nBusiness context:\nA mid-sized manufacturing firm based in Jurong, Singapore sources raw materials from 12 suppliers across Singapore, Malaysia, and Vietnam. The procurement manager noticed significant cost fluctuations for the same materials over the past year and wants a variance analysis to identify patterns and negotiate better contracts.\n\nDesired outcome:\nAnalyze procurement costs over time and detect efficiency gaps.\n\nMy details:\n- Supplier Procurement Cost Variance Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":150,"title":"Reverse Logistics Cost Optimization Report","category":"Customer Comms","source":"Admin & Ops","module":"Cost analysis efficiency reports","difficulty":"Intermediate","explanation":"Evaluate reverse logistics costs and propose optimization strategies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Reverse Logistics Cost Optimization Report\"\n\nStarting brief:\n\"You are a reverse logistics consultant. Prepare a cost and efficiency report for handling returned goods, covering: cost per return, transportation and handling costs, refurbishment expenses, resale vs. disposal rates, and impact on overall profitability. Recommend strategies for cost reduction such as localized return centers, improved sizing guides, and AI-powered return predictions.\"\n\nBusiness context:\nA fashion retailer with 40 outlets across Singapore (in malls along Orchard Road, Marina Bay, suburban hubs like Tampines and Jurong) and another 60 outlets across Southeast Asia is struggling with high costs from returned goods due to size mismatches and damages. They want to assess their reverse logistics process to identify cost-saving opportunities without compromising customer experience.\n\nDesired outcome:\nEvaluate reverse logistics costs and propose optimization strategies.\n\nMy details:\n- Reverse Logistics Cost Optimization Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":151,"title":"End to End Export Documentation Checklist","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Create a complete, step-by-step export documentation checklist. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"End to End Export Documentation Checklist\"\n\nStarting brief:\nYou are an International Trade Compliance Consultant. Prepare an end-to-end export documentation checklist for a first-time exporter shipping goods from Singapore to the EU.\n\nBusiness context:\nA small manufacturing company in Singapore is preparing its first export order to Europe. The team is nervous about missing critical customs paperwork, which could cause shipment delays or fines. They need a comprehensive checklist to ensure all documentation is prepared correctly and in compliance with EU regulations.\n\nDesired outcome:\nCreate a complete, step-by-step export documentation checklist.\n\nMy details:\n- End to End Export Documentation Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product category and HS code\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":152,"title":"Harmonized System (HS) Code Classification","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Determine the correct HS code for export goods. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Harmonized System (HS) Code Classification\"\n\nStarting brief:\nYou are a Customs Classification Specialist. Verify and confirm the correct HS code for a batch of export products.\n\nBusiness context:\nAn apparel exporter frequently faces customs delays because officers question their HS code classification. This not only increases clearance times but also leads to inconsistent duty calculations.\n\nDesired outcome:\nDetermine the correct HS code for export goods.\n\nMy details:\n- Harmonized System (HS) Code Classification details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Detailed product description\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":153,"title":"Certificate of Origin Preparation","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Intermediate","explanation":"Guide the preparation and application process for a Certificate of Origin. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Certificate of Origin Preparation\"\n\nStarting brief:\nYou are a Trade Documentation Advisor. Create step-by-step instructions for obtaining a Certificate of Origin for Singapore F&B exports to the UAE.\n\nBusiness context:\nA Singapore-based food and beverage exporter shipping to the Middle East has been informed by buyers that they need a Certificate of Origin to qualify for preferential duty rates under existing FTAs. The exporter is unsure of the correct format and issuing authority.\n\nDesired outcome:\nGuide the preparation and application process for a Certificate of Origin.\n\nMy details:\n- Certificate of Origin Preparation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exporter details and registration numbers (UEN)\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":154,"title":"Export Invoice Compliance Audit","category":"Excel & Data","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Create a customs-compliant export invoice template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Export Invoice Compliance Audit\"\n\nStarting brief:\nYou are a Customs Compliance Officer. Audit an exporter's existing invoice and prepare a compliant export invoice template for shipments from Singapore to the US.\n\nBusiness context:\nA medium-sized lifestyle goods exporter in Singapore was recently penalized for discrepancies between their commercial invoice and packing list. They want a compliance-friendly export invoice template to avoid future issues.\n\nDesired outcome:\nCreate a customs-compliant export invoice template.\n\nMy details:\n- Export Invoice Compliance Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current invoice format\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":155,"title":"Export Packing List Standardization","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Create a standard export packing list template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Export Packing List Standardization\"\n\nStarting brief:\nYou are a Logistics Documentation Specialist. Design a standardized export packing list template for electronics shipments from Singapore to Nigeria.\n\nBusiness context:\nA Singapore-based electronics exporter shipping to Africa often receives clearance delays due to incomplete packing list details. Customs authorities have warned them to standardize the document.\n\nDesired outcome:\nCreate a standard export packing list template.\n\nMy details:\n- Export Packing List Standardization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details and HS codes\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":156,"title":"Export License Application Guide","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Guide the exporter through the license application process. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Export License Application Guide\"\n\nStarting brief:\nYou are an Export Licensing Consultant. Outline the complete process for obtaining export licenses for pharmaceutical products from Singapore to the UK.\n\nBusiness context:\nA Singapore-based pharmaceutical exporter received a large overseas order but is unsure about the required export licenses and permits for regulated products. Delays in licensing could cost them the deal.\n\nDesired outcome:\nGuide the exporter through the license application process.\n\nMy details:\n- Export License Application Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product description and HS code\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":157,"title":"Digital Customs Filing Process","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Intermediate","explanation":"Explain the digital customs filing process for exports. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Digital Customs Filing Process\"\n\nStarting brief:\nYou are a Digital Trade Process Expert. Create a detailed, screenshot-supported guide for filing export declarations online via TradeNet (Singapore Customs).\n\nBusiness context:\nA Singapore exporter is transitioning to electronic filing for customs clearance but finds the online portal confusing and error-prone. They want a detailed guide for smooth digital submissions.\n\nDesired outcome:\nExplain the digital customs filing process for exports.\n\nMy details:\n- Digital Customs Filing Process details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exporter registration ID (UEN / CR account)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":158,"title":"Pre Shipment Inspection Report Preparation","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Guide the preparation and completion of a pre-shipment inspection report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Pre Shipment Inspection Report Preparation\"\n\nStarting brief:\nYou are a Quality & Compliance Specialist. Outline how to arrange and complete a pre-shipment inspection report for furniture exports to Australia.\n\nBusiness context:\nA furniture exporter shipping to Australia must provide a pre-shipment inspection report from a recognized agency to comply with import rules.\n\nDesired outcome:\nGuide the preparation and completion of a pre-shipment inspection report.\n\nMy details:\n- Pre Shipment Inspection Report Preparation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details and HS codes\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":159,"title":"Export Duty Calculation Tool","category":"Excel & Data","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Provide a duty calculation framework for exporters. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Export Duty Calculation Tool\"\n\nStarting brief:\nYou are a Trade Tariff Analyst. Create a simple tool or framework for calculating customs duties for Singapore auto parts exports.\n\nBusiness context:\nA Singapore-based auto parts exporter often underestimates customs duties in quotes, leading to reduced profit margins. They need a reliable method to calculate export duties for various countries.\n\nDesired outcome:\nProvide a duty calculation framework for exporters.\n\nMy details:\n- Export Duty Calculation Tool details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- HS codes for all products\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":160,"title":"Export Compliance Risk Assessment","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Assess and mitigate export compliance risks. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Export Compliance Risk Assessment\"\n\nStarting brief:\nYou are an International Trade Risk Consultant. Prepare a compliance risk assessment for a Singapore textile exporter.\n\nBusiness context:\nA Singapore textile exporter has expanded into new markets without fully understanding each country's compliance requirements, risking shipment holds.\n\nDesired outcome:\nAssess and mitigate export compliance risks.\n\nMy details:\n- Export Compliance Risk Assessment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Export market list\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":161,"title":"Importer Security Filing (ISF) for US Shipments","category":"Excel & Data","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Prepare a step-by-step guide for ISF compliance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Importer Security Filing (ISF) for US Shipments\"\n\nStarting brief:\nYou are a US Customs Compliance Advisor. Provide a complete guide for preparing and submitting the Importer Security Filing for goods exported from Singapore to the US.\n\nBusiness context:\nA Singapore stone and tile exporter sending goods to the US is confused about the \"10+2\" ISF requirements. Missing deadlines could result in hefty fines, so they need clear guidance on what to file, when, and how.\n\nDesired outcome:\nPrepare a step-by-step guide for ISF compliance.\n\nMy details:\n- Importer Security Filing (ISF) for US Shipments details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exporter details\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":162,"title":"Dangerous Goods Declaration","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Create a compliant  template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Dangerous Goods Declaration\"\n\nStarting brief:\nYou are a Hazardous Cargo Compliance Specialist. Design a Dangerous Goods Declaration form for chemical exports from Singapore.\n\nBusiness context:\nA Singapore-based chemical exporter shipping across Southeast Asia must comply with IMO regulations and file a Dangerous Goods Declaration. They've faced multiple shipment rejections at the Port of Singapore due to incomplete declarations.\n\nDesired outcome:\nCreate a compliant Dangerous Goods Declaration template.\n\nMy details:\n- Dangerous Goods Declaration details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product chemical composition\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":163,"title":"Letter of Credit Documentation Checklist","category":"Research","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Create a documentation checklist for LC compliance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Letter of Credit Documentation Checklist\"\n\nStarting brief:\nYou are a Trade Finance Documentation Expert. Prepare a checklist for aligning export documents with a buyer's LC terms.\n\nBusiness context:\nA Singapore engineering goods exporter receives payment via letter of credit but often struggles with matching documents to the LC terms, risking non-payment.\n\nDesired outcome:\nCreate a documentation checklist for LC compliance.\n\nMy details:\n- Letter of Credit Documentation Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Copy of LC terms\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":164,"title":"ATA Carnet Preparation Guide","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Guide preparation and use of an ATA Carnet. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"ATA Carnet Preparation Guide\"\n\nStarting brief:\nYou are a Temporary Export Documentation Consultant. Create a complete ATA Carnet preparation and usage guide for Singapore exporters.\n\nBusiness context:\nA Singapore events company is temporarily exporting exhibition goods to Dubai and wants to use an ATA Carnet to simplify customs clearance.\n\nDesired outcome:\nGuide preparation and use of an ATA Carnet.\n\nMy details:\n- ATA Carnet Preparation Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of goods for temporary export\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":165,"title":"Export Health Certificate for Food Products","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Provide steps for obtaining an export health certificate. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Export Health Certificate for Food Products\"\n\nStarting brief:\nYou are a Food Export Compliance Advisor. Outline the process to obtain an export health certificate from the Singapore Food Agency (SFA) for dairy products being shipped from Singapore to Malaysia.\n\nBusiness context:\nA Singapore-based dairy and processed food exporter shipping to Malaysia needs a health certificate issued by Singapore authorities to meet the importing country's food safety standards.\n\nDesired outcome:\nProvide steps for obtaining an export health certificate.\n\nMy details:\n- Export Health Certificate for Food Products details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":166,"title":"Export Permit Renewal Process","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Intermediate","explanation":"Create a step-by-step permit renewal guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Export Permit Renewal Process\"\n\nStarting brief:\nYou are a Government Licensing Liaison. Prepare a guide for renewing Singapore Customs export permits via TradeNet without operational downtime.\n\nBusiness context:\nA Singapore agro-commodity trader holds a 1-year export permit issued via TradeNet but risks expiry in the middle of peak season. They want to renew well in advance.\n\nDesired outcome:\nCreate a step-by-step permit renewal guide.\n\nMy details:\n- Export Permit Renewal Process details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current permit copy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":167,"title":"Bill of Lading Accuracy Checklist","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Intermediate","explanation":"Provide a Bill of Lading accuracy checklist. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Bill of Lading Accuracy Checklist\"\n\nStarting brief:\nYou are a Freight Documentation Specialist. Create a pre-shipment checklist to verify Bill of Lading accuracy for Singapore exporters shipping out of PSA / Tuas / Jurong Port.\n\nBusiness context:\nA Singapore machinery exporter faced demurrage charges when incorrect consignee details on the Bill of Lading delayed release at the destination port.\n\nDesired outcome:\nProvide a Bill of Lading accuracy checklist.\n\nMy details:\n- Bill of Lading Accuracy Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Shipment booking details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":168,"title":"Export Declaration Form Guidance","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Provide updated export declaration guidelines. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Export Declaration Form Guidance\"\n\nStarting brief:\nYou are a Customs Declaration Expert. Provide a 2025-updated guide to filing export declarations through TradeNet in Singapore.\n\nBusiness context:\nA Singapore jewellery exporter regularly files export declarations via TradeNet but struggles to keep up with changing requirements from Singapore Customs.\n\nDesired outcome:\nProvide updated export declaration guidelines.\n\nMy details:\n- Export Declaration Form Guidance details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exporter UEN and TradeNet account details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":169,"title":"Proforma Invoice for International Buyers","category":"Customer Comms","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Create a proforma invoice template aligned with customs needs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Proforma Invoice for International Buyers\"\n\nStarting brief:\nYou are an Export Sales Documentation Expert. Design a proforma invoice template for Singapore exporters selling to EU buyers.\n\nBusiness context:\nA Singapore furniture exporter is expanding into Europe and wants to issue professional, customs-friendly proforma invoices for new buyers.\n\nDesired outcome:\nCreate a proforma invoice template aligned with customs needs.\n\nMy details:\n- Proforma Invoice for International Buyers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":170,"title":"Country Specific Export Restrictions Guide","category":"Research","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"List export restrictions for target countries. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Country Specific Export Restrictions Guide\"\n\nStarting brief:\nYou are a Global Trade Compliance Analyst. Prepare a guide outlining export restrictions for Singapore technology products in key markets, including obligations under the Singapore Strategic Goods (Control) Act.\n\nBusiness context:\nA Singapore technology exporter needs to understand export control laws in different countries to avoid shipping restricted products.\n\nDesired outcome:\nList export restrictions for target countries.\n\nMy details:\n- Country Specific Export Restrictions Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product category and HS codes\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":171,"title":"Incoterms 2025 Documentation Checklist","category":"Excel & Data","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Beginner","explanation":"Provide an Incoterms-specific documentation checklist. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Incoterms 2025 Documentation Checklist\"\n\nStarting brief:\nYou are an International Logistics Trainer. Create a customs documentation checklist for Singapore exporters based on each Incoterm, focusing on DDP obligations.\n\nBusiness context:\nA first-time Singapore exporter agreed to DDP (Delivered Duty Paid) terms with an overseas buyer without understanding the additional documents and responsibilities involved.\n\nDesired outcome:\nProvide an Incoterms-specific documentation checklist.\n\nMy details:\n- Incoterms 2025 Documentation Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Chosen Incoterm\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":172,"title":"Export Insurance Claim Documentation","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Intermediate","explanation":"Create an insurance claim documentation guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Export Insurance Claim Documentation\"\n\nStarting brief:\nYou are an Export Risk Mitigation Consultant. Outline all documents needed for a successful marine cargo insurance claim with Singapore-based insurers (e.g. NTUC Income, AIG Singapore, MSIG).\n\nBusiness context:\nA Singapore textile exporter suffered water damage to goods in transit but couldn't claim insurance due to missing documentation.\n\nDesired outcome:\nCreate an insurance claim documentation guide.\n\nMy details:\n- Export Insurance Claim Documentation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Insurance policy details\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":173,"title":"Export Compliance SOP for SMEs","category":"Research","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Create an export compliance SOP. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Export Compliance SOP for SMEs\"\n\nStarting brief:\nYou are a Trade Compliance Process Designer. Draft a standard operating procedure for export compliance for a Singapore SME.\n\nBusiness context:\nA small Singapore handicraft and lifestyle goods exporter wants to formalize their export compliance process to train new staff.\n\nDesired outcome:\nCreate an export compliance SOP.\n\nMy details:\n- Export Compliance SOP for SMEs details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company size and team structure\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":174,"title":"Electronic Certificate of Origin (eCO) Filing","category":"Email & Writing","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Intermediate","explanation":"Provide an eCO filing guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Electronic Certificate of Origin (eCO) Filing\"\n\nStarting brief:\nYou are an International Trade Digitalisation Specialist. Prepare a guide for filing an Electronic Certificate of Origin from Singapore.\n\nBusiness context:\nA Singapore auto parts exporter wants to switch from paper to electronic certificate of origin filing through TradeNet to save time.\n\nDesired outcome:\nProvide an eCO filing guide.\n\nMy details:\n- Electronic Certificate of Origin (eCO) Filing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exporter UEN\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":175,"title":"Export Document Archiving Policy","category":"Research","source":"Admin & Ops","module":"Customs export documentation","difficulty":"Advanced","explanation":"Create an export document archiving policy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Export Document Archiving Policy\"\n\nStarting brief:\nYou are a Trade Records Management Expert. Develop an archiving policy for export documents in line with Singapore Customs requirements (typically 5 years), IRAS GST record-keeping rules, PDPA, and international regulations.\n\nBusiness context:\nA large Singapore exporter is facing an internal audit and needs a proper document storage policy to comply with legal retention requirements.\n\nDesired outcome:\nCreate an export document archiving policy.\n\nMy details:\n- Export Document Archiving Policy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company size and export volume\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":176,"title":"Automated Inventory Restocking for FMCG","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Beginner","explanation":"Create a restocking alert system that prevents stockouts and maintains optimal inventory levels. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Automated Inventory Restocking for FMCG\"\n\nStarting brief:\nYou are a Supply Chain Data Analyst. Develop an automated restocking alert system for an FMCG distributor handling 2,000 SKUs.\n\nBusiness context:\nYou are managing inventory for a mid-sized FMCG distributor headquartered in Singapore, with warehousing in Tuas servicing supermarkets and convenience stores across the island. Your warehouse handles over 2,000 SKUs, and sales fluctuate based on seasonal demand around festive periods like Chinese New Year and Hari Raya. Stockouts have become a recurring problem, especially for high-demand items, leading to missed sales opportunities. You want an automated restocking system that alerts you before critical...\n\nDesired outcome:\nCreate a restocking alert system that prevents stockouts and maintains optimal inventory levels.\n\nMy details:\n- Automated Inventory Restocking for FMCG details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU list with current stock levels\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":177,"title":"Inventory Tracking Dashboard for E commerce","category":"Customer Comms","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Build a live, multi-location inventory tracking dashboard that syncs with the website. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Inventory Tracking Dashboard for E commerce\"\n\nStarting brief:\nYou are an Inventory Management Specialist. Create a real-time inventory tracking dashboard for an e-commerce business with two warehouses.\n\nBusiness context:\nYou operate a small but growing e-commerce business that sells fashion accessories across Singapore and into Malaysia. You stock products in two warehouses—one in Tuas and one in Johor Bahru just across the Causeway—but inventory updates are often delayed, causing inaccurate stock counts on your website and on Shopee/Lazada listings. This leads to overselling items you no longer have in stock and losing customer trust. You need a live inventory tracking dashboard that updates in real-time and supports...\n\nDesired outcome:\nBuild a live, multi-location inventory tracking dashboard that syncs with the website.\n\nMy details:\n- Inventory Tracking Dashboard for E commerce details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of products and SKUs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":178,"title":"Inventory Ageing & Dead Stock Alerts","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Implement an inventory ageing tracker that identifies slow-moving and obsolete stock. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Inventory Ageing & Dead Stock Alerts\"\n\nStarting brief:\nYou are a Retail Inventory Analyst. Build an inventory ageing and dead stock alert system for an electronics retail chain.\n\nBusiness context:\nYour electronics retail chain often finds products sitting in the warehouse for months without selling, tying up capital. Some items, like mobile accessories, lose value quickly due to market changes. You need an inventory ageing system that flags items nearing expiry or becoming outdated so you can create clearance sales or promotional offers before they lose value.\n\nDesired outcome:\nImplement an inventory ageing tracker that identifies slow-moving and obsolete stock.\n\nMy details:\n- Inventory Ageing & Dead Stock Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU purchase dates and quantities\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":179,"title":"Vendor based Restocking Prioritisation","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Create a vendor-prioritised restocking plan to ensure uninterrupted production. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Vendor based Restocking Prioritisation\"\n\nStarting brief:\nYou are a Procurement & Inventory Planner. Develop a vendor-prioritised restocking system for a manufacturing unit.\n\nBusiness context:\nYour manufacturing unit sources raw materials from multiple vendors, but each has different lead times and reliability rates. Some materials arrive late, affecting production timelines. You want an inventory restocking plan that prioritises reorders with faster and more reliable vendors while balancing costs.\n\nDesired outcome:\nCreate a vendor-prioritised restocking plan to ensure uninterrupted production.\n\nMy details:\n- Vendor based Restocking Prioritisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of raw materials and stock levels\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":180,"title":"Seasonal Restocking Forecast","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Design a seasonal restocking forecast to match demand patterns. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Seasonal Restocking Forecast\"\n\nStarting brief:\nYou are a Demand Forecasting Specialist. Build a seasonal restocking plan for a sports equipment store.\n\nBusiness context:\nYour sports equipment store in Singapore sees significant seasonal demand changes—badminton and running gear spike during the Standard Chartered Singapore Marathon period, football gear during major tournament windows, and gym equipment in January as part of New Year resolutions. Restocking decisions are currently based on guesswork, leading to excess stock in some categories and shortages in others. You need a forecast-driven restocking plan that aligns with seasonal demand.\n\nDesired outcome:\nDesign a seasonal restocking forecast to match demand patterns.\n\nMy details:\n- Seasonal Restocking Forecast details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical sales data by product category\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":181,"title":"Automated Inventory Reconciliation","category":"Customer Comms","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Implement a real-time reconciliation system for multi-channel inventory accuracy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Automated Inventory Reconciliation\"\n\nStarting brief:\nYou are an Inventory Accuracy Specialist. Create an automated reconciliation workflow for a grocery chain with both online and offline sales.\n\nBusiness context:\nYour mid-sized grocery chain uses multiple sales channels—physical stores, online orders, and third-party delivery apps. Stock discrepancies occur frequently between system records and actual warehouse counts, leading to customer cancellations. You need an automated reconciliation process that flags mismatches and corrects them before sales are impacted.\n\nDesired outcome:\nImplement a real-time reconciliation system for multi-channel inventory accuracy.\n\nMy details:\n- Automated Inventory Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Access to POS & online sales data\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":182,"title":"Predictive Stockout Prevention","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Create a predictive alert system that links social media trends to stock levels. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Predictive Stockout Prevention\"\n\nStarting brief:\nYou are a Demand Signal Analyst. Design a predictive stockout prevention system for an organic food brand.\n\nBusiness context:\nA popular organic food brand has products that sell out quickly once they go viral on Instagram, leaving stock empty for weeks until the next batch arrives. The brand wants a predictive model to detect social media spikes and adjust inventory alerts accordingly, preventing stockouts during sudden demand surges.\n\nDesired outcome:\nCreate a predictive alert system that links social media trends to stock levels.\n\nMy details:\n- Predictive Stockout Prevention details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU list with current inventory\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":183,"title":"Warehouse Bin level Inventory Alerts","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Build a bin-location inventory alert system for warehouse efficiency. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Warehouse Bin level Inventory Alerts\"\n\nStarting brief:\nYou are a Warehouse Operations Specialist. Develop a bin-level stock alert system for a distribution warehouse.\n\nBusiness context:\nYour warehouse stores thousands of items in bins, but stock checks happen only at SKU level. This leads to cases where some bins run empty while others still have stock, causing inefficient picking routes. You want an alert system that tracks inventory at the bin location level and signals replenishment within the warehouse before it impacts outbound orders.\n\nDesired outcome:\nBuild a bin-location inventory alert system for warehouse efficiency.\n\nMy details:\n- Warehouse Bin level Inventory Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Bin mapping with SKU assignments\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":184,"title":"Multi Store Restocking Coordination","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Beginner","explanation":"Create an inter-store transfer-based restocking system. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Multi Store Restocking Coordination\"\n\nStarting brief:\nYou are a Retail Supply Chain Planner. Design a restocking plan for a multi-store apparel chain.\n\nBusiness context:\nA retail apparel chain has 25 outlets across Singapore—spread across Orchard, Marina Bay, Jurong, Tampines, and major suburban malls—each with different sales velocities. Some stores overstock while others run out, leading to uneven distribution and unnecessary procurement costs. You want a system to coordinate restocking by shifting inventory between stores before placing new supplier orders.\n\nDesired outcome:\nCreate an inter-store transfer-based restocking system.\n\nMy details:\n- Multi Store Restocking Coordination details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Store list with stock levels\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":185,"title":"Perishable Goods Expiry Alerts","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Set up a perishable goods expiry tracking and alert system. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Perishable Goods Expiry Alerts\"\n\nStarting brief:\nYou are a Fresh Food Inventory Manager. Create an expiry alert system for bakery products.\n\nBusiness context:\nYour bakery supplies fresh products to supermarkets, but some items expire before being sold, causing wastage and financial loss. You want an expiry-based alert system that prompts early discounts or redistribution to other outlets before spoilage occurs.\n\nDesired outcome:\nSet up a perishable goods expiry tracking and alert system.\n\nMy details:\n- Perishable Goods Expiry Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU list with expiry details\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":186,"title":"Spare Parts Restocking for Manufacturing","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Create a preventive restocking plan for critical spare parts. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Spare Parts Restocking for Manufacturing\"\n\nStarting brief:\nYou are a Maintenance Inventory Planner. Develop a spare parts inventory management system for a manufacturing plant.\n\nBusiness context:\nYour manufacturing plant runs multiple production lines that frequently stop due to missing spare parts. Currently, there's no systematic tracking, and maintenance teams only request parts when breakdowns occur. You want a preventive inventory system for spare parts that restocks before machinery downtime happens.\n\nDesired outcome:\nCreate a preventive restocking plan for critical spare parts.\n\nMy details:\n- Spare Parts Restocking for Manufacturing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Spare parts list with usage data\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":187,"title":"Inventory Shrinkage Alerts","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Implement an inventory shrinkage detection and alert mechanism. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Inventory Shrinkage Alerts\"\n\nStarting brief:\nYou are a Loss Prevention Analyst. Create an inventory shrinkage alert system for convenience stores.\n\nBusiness context:\nA chain of convenience stores is experiencing unexplained inventory losses due to theft, misplacement, or accounting errors. You need an alert system that detects unusual shrinkage patterns in real time and flags high-risk products or locations.\n\nDesired outcome:\nImplement an inventory shrinkage detection and alert mechanism.\n\nMy details:\n- Inventory Shrinkage Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical shrinkage rates\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":188,"title":"Inventory Buffer Planning for Festivals","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Plan inventory buffers for peak festival sales. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Inventory Buffer Planning for Festivals\"\n\nStarting brief:\nYou are a Seasonal Demand Planner. Develop a festival inventory buffer plan for a cosmetics brand.\n\nBusiness context:\nYour cosmetic products business sees a huge spike during Chinese New Year, Hari Raya, Deepavali, and Valentine's Day. Last year, late restocking led to missed opportunities. You need an inventory buffer system that pre-orders additional stock ahead of festivals while avoiding overstocking.\n\nDesired outcome:\nPlan inventory buffers for peak festival sales.\n\nMy details:\n- Inventory Buffer Planning for Festivals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Festival sales history by SKU\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":189,"title":"Automated Vendor Restock Requests","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Automate vendor restock request generation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Automated Vendor Restock Requests\"\n\nStarting brief:\nYou are a Procurement Automation Specialist. Create an automated vendor restock request system for a hardware tools distributor.\n\nBusiness context:\nA hardware tools distributor works with multiple suppliers and currently sends restock requests manually. This delays procurement and often leads to missed sales. You want an automated system that sends restock purchase orders to vendors based on pre-set inventory triggers.\n\nDesired outcome:\nAutomate vendor restock request generation.\n\nMy details:\n- Automated Vendor Restock Requests details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU list with reorder thresholds\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":190,"title":"Overstock Clearance Trigger","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Detect and clear overstocked items efficiently. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Overstock Clearance Trigger\"\n\nStarting brief:\nYou are a Retail Inventory Optimiser. Build an overstock clearance trigger system for a home décor retailer.\n\nBusiness context:\nA home décor retailer often over-orders certain designs that remain unsold for months, occupying valuable warehouse space. You need an automated system that flags overstock situations and triggers clearance campaigns to free up space.\n\nDesired outcome:\nDetect and clear overstocked items efficiently.\n\nMy details:\n- Overstock Clearance Trigger details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Stock cover rules\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":191,"title":"Cross Dock Inventory Flow Monitoring","category":"Customer Comms","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Ensure seamless inventory flow through cross-docking operations. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cross Dock Inventory Flow Monitoring\"\n\nStarting brief:\nYou are a Logistics Flow Analyst. Create a monitoring system for cross-dock inventory movements.\n\nBusiness context:\nA logistics company operates multiple cross-dock facilities where goods are quickly transferred from inbound to outbound trucks. Due to poor inventory visibility, pallets sometimes sit unshipped for days, leading to missed deliveries and unhappy clients. You need a real-time system to track cross-dock movements and trigger alerts for delayed transfers.\n\nDesired outcome:\nEnsure seamless inventory flow through cross-docking operations.\n\nMy details:\n- Cross Dock Inventory Flow Monitoring details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Dock facility layout and process maps\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":192,"title":"Seasonal Restocking Automation","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Automate seasonal restocking for recurring demand patterns. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Seasonal Restocking Automation\"\n\nStarting brief:\nYou are a Seasonal Supply Planner. Develop an automated restocking trigger for seasonal beverage SKUs.\n\nBusiness context:\nYour beverage distribution business experiences predictable seasonal demand for certain flavors—like mango in summer and cranberry in winter. Currently, seasonal orders are placed manually, often late. You want an automated seasonal restocking trigger to ensure timely supplier orders ahead of peak periods.\n\nDesired outcome:\nAutomate seasonal restocking for recurring demand patterns.\n\nMy details:\n- Seasonal Restocking Automation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Seasonal sales history by SKU\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":193,"title":"Vendor Lead Time Alert System","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Track and respond to supplier lead time changes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Vendor Lead Time Alert System\"\n\nStarting brief:\nYou are a Vendor Performance Analyst. Create a vendor lead time alert system for an electronics retailer.\n\nBusiness context:\nAn electronics retailer deals with multiple suppliers, each with different lead times. Late awareness of lead time changes causes urgent air freight costs. You want an alert system that detects when supplier lead times shift, allowing proactive restocking adjustments.\n\nDesired outcome:\nTrack and respond to supplier lead time changes.\n\nMy details:\n- Vendor Lead Time Alert System details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Vendor list with current lead times\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":194,"title":"Kanban Based Inventory Alerts","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Implement a digital Kanban-based replenishment alert system. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Kanban Based Inventory Alerts\"\n\nStarting brief:\nYou are a Lean Manufacturing Inventory Specialist. Develop a digital Kanban inventory alert system for an auto parts plant.\n\nBusiness context:\nA small-scale auto parts manufacturer wants to adopt a Kanban system for its assembly line components. The current manual card system is slow and often misplaced. You need a digital Kanban alert system that notifies replenishment teams instantly when a bin is empty.\n\nDesired outcome:\nImplement a digital Kanban-based replenishment alert system.\n\nMy details:\n- Kanban Based Inventory Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Component bin mapping\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":195,"title":"Multi Currency Inventory Valuation","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Create a real-time multi-currency inventory valuation system. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Multi Currency Inventory Valuation\"\n\nStarting brief:\nYou are a Global Inventory Finance Analyst. Build a multi-currency valuation system for stock in multiple countries.\n\nBusiness context:\nA global distributor stocks products sourced from multiple countries. Exchange rate fluctuations make it difficult to track accurate inventory value in real-time, affecting restocking decisions. You want a valuation system that adjusts inventory costs dynamically based on currency changes.\n\nDesired outcome:\nCreate a real-time multi-currency inventory valuation system.\n\nMy details:\n- Multi Currency Inventory Valuation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Inventory quantities per location\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":196,"title":"Safety Stock Optimization","category":"Customer Comms","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Optimise safety stock for cost efficiency without stockouts. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Safety Stock Optimization\"\n\nStarting brief:\nYou are a Pharma Supply Planner. Develop a safety stock optimisation model for pharmaceutical distribution.\n\nBusiness context:\nYour pharmaceutical wholesale business keeps high safety stock to avoid shortages, but this ties up too much capital. You want a system to calculate optimal safety stock levels per SKU while maintaining service level targets.\n\nDesired outcome:\nOptimise safety stock for cost efficiency without stockouts.\n\nMy details:\n- Safety Stock Optimization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Demand history per SKU\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":197,"title":"Geo Fenced Inventory Alerts","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Track equipment inventory using geo-fencing. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Geo Fenced Inventory Alerts\"\n\nStarting brief:\nYou are an Asset Tracking Specialist. Build a geo-fenced alert system for rental equipment inventory.\n\nBusiness context:\nA construction equipment rental company needs to track equipment location and stock availability across multiple yards. Equipment is sometimes transferred without system updates, causing rental delays. You want a geo-fenced alert system to detect when equipment leaves or enters a yard.\n\nDesired outcome:\nTrack equipment inventory using geo-fencing.\n\nMy details:\n- Geo Fenced Inventory Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Equipment list with GPS tracker IDs\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":198,"title":"Returns Processing Inventory Updates","category":"Excel & Data","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Intermediate","explanation":"Accelerate inventory availability from returned goods. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Returns Processing Inventory Updates\"\n\nStarting brief:\nYou are a Reverse Logistics Coordinator. Design a returns processing inventory update system.\n\nBusiness context:\nAn online fashion retailer receives thousands of returns weekly, but restocking delays occur because returned items take too long to be updated in inventory. You want an automated system that updates inventory the moment return inspection is complete.\n\nDesired outcome:\nAccelerate inventory availability from returned goods.\n\nMy details:\n- Returns Processing Inventory Updates details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Return processing workflow\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":199,"title":"Supplier Minimum Order Consolidation","category":"Customer Comms","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Enable MOQ-based consolidated restocking. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Supplier Minimum Order Consolidation\"\n\nStarting brief:\nYou are a Procurement Efficiency Planner. Create a consolidated ordering system for MOQ suppliers.\n\nBusiness context:\nA food service distributor deals with suppliers who have high minimum order quantities (MOQs). Often, urgent restocks fail because the MOQ isn't met. You want a system to consolidate orders across multiple branches to meet MOQ faster.\n\nDesired outcome:\nEnable MOQ-based consolidated restocking.\n\nMy details:\n- Supplier Minimum Order Consolidation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Branch order data\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":200,"title":"Inventory Reorder Simulation Tool","category":"Customer Comms","source":"Admin & Ops","module":"Inventory tracking sheets","difficulty":"Advanced","explanation":"Create a reorder policy simulation tool. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Inventory Reorder Simulation Tool\"\n\nStarting brief:\nYou are an Inventory Policy Analyst. Build a simulation tool for testing different reorder points.\n\nBusiness context:\nA home appliance retailer wants to experiment with different reorder points to see how it affects stockouts and holding costs before making policy changes. You need a simulation tool that models various reorder scenarios.\n\nDesired outcome:\nCreate a reorder policy simulation tool.\n\nMy details:\n- Inventory Reorder Simulation Tool details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- SKU demand history\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":201,"title":"Optimised Route Plan for Multiple Deliveries","category":"Excel & Data","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Create an optimised delivery route plan that reduces fuel usage and delivery times while improving driver productivity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Optimised Route Plan for Multiple Deliveries\"\n\nStarting brief:\nYou are an experienced Logistics Planner with expertise in traffic prediction and route optimisation. Design a delivery schedule and route map for 15 vans covering 120 orders across Singapore.\n\nBusiness context:\nYou are the operations head for a mid-sized courier company based in Singapore. Your team manages 15 delivery vans covering over 120 daily orders across the island, and you've been facing late deliveries due to unplanned routing. Your drivers sometimes take overlapping paths or face unexpected congestion along the PIE/CTE expressways. You need a systematic way to optimise routes so that each driver covers the shortest possible distance while ensuring timely delivery for high-priority packages. You also want to...\n\nDesired outcome:\nCreate an optimised delivery route plan that reduces fuel usage and delivery times while improving driver productivity.\n\nMy details:\n- Optimised Route Plan for Multiple Deliveries details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of delivery vehicles & their capacity\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":202,"title":"Peak Hour Delivery Route Adjustment","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Design a peak-hour delivery plan that adjusts in real time to ensure all deliveries meet promised timelines. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Peak Hour Delivery Route Adjustment\"\n\nStarting brief:\nYou are a Last-Mile Delivery Optimisation Expert. Create a peak-hour routing strategy for 20 grocery delivery riders across Singapore.\n\nBusiness context:\nYou manage the dispatch team for an online grocery delivery service in Singapore. Every evening between 6 PM–9 PM, orders spike as working professionals return home to HDB estates and condo developments. Your current delivery pattern is fixed throughout the day, causing delays during peak traffic hours along the CTE, AYE, and PIE. Drivers often miss their ETA targets, and customers complain about late grocery drop-offs. You want a dynamic route adjustment system that automatically reshuffles deliveries when...\n\nDesired outcome:\nDesign a peak-hour delivery plan that adjusts in real time to ensure all deliveries meet promised timelines.\n\nMy details:\n- Peak Hour Delivery Route Adjustment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of delivery addresses with time windows\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":203,"title":"Fuel Efficient Regional Delivery Planning","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Create a regional delivery schedule that minimises fuel consumption and covers all townships efficiently. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Fuel Efficient Regional Delivery Planning\"\n\nStarting brief:\nYou are a Regional Logistics Planner with expertise in fuel efficiency. Prepare a delivery plan covering 30 townships across Johor and southern Peninsular Malaysia from a Singapore hub, using 5 vans.\n\nBusiness context:\nYou operate a regional courier service from Singapore covering cross-border deliveries into Johor and selected towns across Peninsular Malaysia, where customer drop-off points are far apart and road conditions vary. Fuel and toll costs are a major concern, and deliveries must be made twice a week to multiple townships. Your drivers often take routes that result in wasted fuel due to poor planning. You want to design a schedule that covers all destinations in the shortest distance possible, while ensuring urgent...\n\nDesired outcome:\nCreate a regional delivery schedule that minimises fuel consumption and covers all townships efficiently.\n\nMy details:\n- Fuel Efficient Regional Delivery Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of townships with GPS coordinates\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":204,"title":"Same Day Delivery Slot Management","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Beginner","explanation":"Create a same-day delivery slot allocation system that ensures workload balance and on-time delivery. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Same Day Delivery Slot Management\"\n\nStarting brief:\nYou are an E-commerce Logistics Strategist. Develop a same-day delivery scheduling plan for Singapore with:\n\nBusiness context:\nYou manage the logistics for an e-commerce company headquartered in Singapore that promises same-day delivery for orders placed before 1 PM. The problem is, orders are unevenly distributed across the island, causing certain delivery zones (e.g., Tampines, Jurong East) to be overloaded while others like the CBD or Sentosa are underutilised. This results in overtime costs for some drivers and idle time for others. You want a dynamic slot management system that allocates deliveries based on real-time order inflow and...\n\nDesired outcome:\nCreate a same-day delivery slot allocation system that ensures workload balance and on-time delivery.\n\nMy details:\n- Same Day Delivery Slot Management details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of delivery vehicles & capacity\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":205,"title":"Seasonal Festival Delivery Planning","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Design a delivery plan for high-demand festival seasons with alternate routes and buffer time. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Seasonal Festival Delivery Planning\"\n\nStarting brief:\nYou are a City Logistics Specialist. Create a Chinese New Year delivery plan for Singapore:\n\nBusiness context:\nYour courier company operates across Singapore, and every year during the Chinese New Year period, areas like Chinatown, Geylang Bahru, and the Marina Bay light-up zones experience heavy footfall and traffic disruptions due to bazaars, road closures, and parade routes. Customer orders also increase by nearly 40% during this time as families prepare for reunion dinners. In previous years, your deliveries were delayed because the routes did not account for blocked roads and event schedules. This year, you want a...\n\nDesired outcome:\nDesign a delivery plan for high-demand festival seasons with alternate routes and buffer time.\n\nMy details:\n- Seasonal Festival Delivery Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Festival traffic restriction map (LTA advisories)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":206,"title":"Hyperlocal Pharmacy Delivery Scheduling","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Create a hyperlocal delivery schedule for pharmacies that prioritises urgency while minimising travel time. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Hyperlocal Pharmacy Delivery Scheduling\"\n\nStarting brief:\nYou are a Hyperlocal Delivery Planner. Design a 2-hour delivery routing system for 8 pharmacies across Singapore:\n\nBusiness context:\nYou run a chain of 8 pharmacies across Singapore (in neighbourhoods such as Toa Payoh, Bedok, Clementi, and Ang Mo Kio) offering 2-hour delivery for medicines within a 6 km radius. Many orders are urgent (e.g., diabetic medications), while others are routine refills. Currently, your riders follow a first-come, first-served approach, which leads to urgent orders sometimes being delayed. You want a route and schedule plan that prioritises urgent deliveries while still batching nearby orders for efficiency.\n\nDesired outcome:\nCreate a hyperlocal delivery schedule for pharmacies that prioritises urgency while minimising travel time.\n\nMy details:\n- Hyperlocal Pharmacy Delivery Scheduling details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Pharmacy locations & service radius\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":207,"title":"Cold Chain Delivery Scheduling for Perishables","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Beginner","explanation":"Develop an optimised cold chain delivery schedule that ensures timely deliveries while preserving product quality. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cold Chain Delivery Scheduling for Perishables\"\n\nStarting brief:\nYou are a Cold Chain Logistics Expert. Create a delivery plan for refrigerated trucks operating across Singapore:\n\nBusiness context:\nYou operate a cold chain logistics business in Singapore, delivering perishable goods like dairy, seafood, and fresh produce to supermarkets (FairPrice, Cold Storage), restaurants, and hotels across the island. Your refrigerated trucks must maintain specific temperature ranges, especially given Singapore's year-round tropical heat, and every hour of delay risks spoilage. Current routes are planned manually, leading to inefficiencies when there's unexpected congestion on the AYE/PIE or a last-minute high-priority...\n\nDesired outcome:\nDevelop an optimised cold chain delivery schedule that ensures timely deliveries while preserving product quality.\n\nMy details:\n- Cold Chain Delivery Scheduling for Perishables details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of delivery addresses with deadlines\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":208,"title":"Multi City Fleet Route Coordination","category":"Excel & Data","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Create an intercity fleet schedule that maximises efficiency and reduces costs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Multi City Fleet Route Coordination\"\n\nStarting brief:\nYou are a Fleet Operations Strategist. Create a coordinated delivery schedule for 50 trucks operating between Singapore, Kuala Lumpur, and Penang:\n\nBusiness context:\nYou manage a fleet of 50 trucks transporting goods between Singapore, Kuala Lumpur, and Penang as part of a Southeast Asian regional logistics operation. Each city has its own delivery schedule, but sometimes routes overlap unnecessarily, increasing fuel and toll costs. Additionally, overnight layovers add expenses for driver accommodations. You want a route plan that coordinates trips across cities, reduces redundancy, and schedules deliveries in a way that maximises vehicle usage while keeping driver shifts...\n\nDesired outcome:\nCreate an intercity fleet schedule that maximises efficiency and reduces costs.\n\nMy details:\n- Multi City Fleet Route Coordination details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- City-to-city delivery requirements\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":209,"title":"Last Mile Delivery Optimisation for Regional Areas","category":"Excel & Data","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Design a regional last-mile delivery routing plan that minimises delays and maximises delivery success rates. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Last Mile Delivery Optimisation for Regional Areas\"\n\nStarting brief:\nYou are a Regional Logistics Planner. Design a last-mile delivery system for towns in Johor and Pahang served from a Singapore hub:\n\nBusiness context:\nYour Singapore-based logistics company is expanding cross-border deliveries into smaller towns across Johor and Pahang, where road infrastructure is inconsistent in rural pockets and GPS coverage can be patchy. Deliveries often require drivers to navigate small kampung lanes or unmarked roads. Current routing methods fail in these areas, leading to missed deliveries and return-to-origin costs. You need a route optimisation system that incorporates local knowledge, offline mapping, and driver coordination for...\n\nDesired outcome:\nDesign a regional last-mile delivery routing plan that minimises delays and maximises delivery success rates.\n\nMy details:\n- Last Mile Delivery Optimisation for Regional Areas details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Regional delivery locations with map coordinates (if available)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":210,"title":"Priority Medical Supply Transport","category":"Excel & Data","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Design an emergency medical transport routing plan that guarantees minimum delivery times for critical supplies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Priority Medical Supply Transport\"\n\nStarting brief:\nYou are an Emergency Medical Logistics Planner. Develop a routing system for critical medical supplies across Singapore's public hospital network:\n\nBusiness context:\nYou manage emergency logistics for a hospital network in Singapore (covering SGH, NUH, TTSH, KTPH, and CGH) that frequently needs to move critical medical supplies such as blood units, oxygen cylinders, and transplant organs between facilities. Delays can cost lives, but the routes often cross congested zones along the CTE, PIE, and CBD during peak hours. Current dispatch methods do not differentiate between critical and non-critical medical items, causing slower response times. You want a priority-based transport...\n\nDesired outcome:\nDesign an emergency medical transport routing plan that guarantees minimum delivery times for critical supplies.\n\nMy details:\n- Priority Medical Supply Transport details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of hospitals & coordinates\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":211,"title":"Shared Ride Parcel Deliveries","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Beginner","explanation":"Create an integrated ride-hail and parcel delivery route system that maximises efficiency without disrupting passenger trips. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Shared Ride Parcel Deliveries\"\n\nStarting brief:\nYou are a Shared Mobility Logistics Expert. Design a parcel delivery system for ride-hailing drivers in Singapore:\n\nBusiness context:\nYou run a parcel delivery startup in Singapore that partners with Grab and Gojek drivers to deliver small packages during their downtime between passenger trips. However, current route assignments are inefficient, often sending drivers far out of their passenger route to deliver parcels, which reduces willingness to participate. You need a scheduling system that intelligently assigns parcels only if they fit naturally along a driver's planned route.\n\nDesired outcome:\nCreate an integrated ride-hail and parcel delivery route system that maximises efficiency without disrupting passenger trips.\n\nMy details:\n- Shared Ride Parcel Deliveries details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Active driver locations and trip routes\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":212,"title":"E Grocery Dark Store Route Planning","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Create a zone-based route allocation system for dark stores to ensure fastest grocery delivery. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"E Grocery Dark Store Route Planning\"\n\nStarting brief:\nYou are an E-Grocery Operations Manager. Build a delivery schedule for multiple dark stores across Singapore:\n\nBusiness context:\nYou manage an e-grocery service in Singapore (think RedMart or FairPrice On) operating from multiple \"dark stores\" — mini fulfilment hubs in HDB heartland areas like Tampines, Jurong, and Bishan, without walk-in customers. Your promise is 30-minute delivery, but overlapping delivery zones between stores sometimes cause duplicate dispatches and confusion. You want a system that assigns orders to the closest store and optimises rider routes to handle multiple deliveries in a single trip.\n\nDesired outcome:\nCreate a zone-based route allocation system for dark stores to ensure fastest grocery delivery.\n\nMy details:\n- E Grocery Dark Store Route Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Dark store locations & delivery radius\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":213,"title":"School Bus Route Optimisation","category":"Meetings","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Beginner","explanation":"Optimise school bus routes for minimal travel time and maximum safety. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"School Bus Route Optimisation\"\n\nStarting brief:\nYou are a School Transport Coordinator. Create an optimised school bus route plan for a private school network in Singapore:\n\nBusiness context:\nYou manage school transport for a chain of private schools across Singapore. The challenge is to minimise total travel time while ensuring that no student spends more than 45 minutes on the bus. Parents often request custom drop-off points at specific HDB blocks or condo entrances, creating inefficient detours. You need a schedule that balances route efficiency with student safety and parental preferences.\n\nDesired outcome:\nOptimise school bus routes for minimal travel time and maximum safety.\n\nMy details:\n- School Bus Route Optimisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Student addresses and preferred drop points\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":214,"title":"Port to Warehouse Freight Scheduling","category":"Meetings","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Beginner","explanation":"Develop a dynamic freight pickup and delivery schedule that reduces waiting time and costs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Port to Warehouse Freight Scheduling\"\n\nStarting brief:\nYou are a Port Logistics Scheduler. Build a port-to-warehouse delivery plan for Singapore's PSA terminals:\n\nBusiness context:\nYour company handles freight logistics from PSA Tuas Port and Pasir Panjang Terminal to warehouses across Singapore (Tuas, Jurong, Changi, and Pioneer). Ship arrivals are often delayed, causing trucks to wait idly and increasing demurrage costs. You need a scheduling system that reacts dynamically to ship ETA changes and reassigns trucks to avoid idle time while still meeting delivery commitments.\n\nDesired outcome:\nDevelop a dynamic freight pickup and delivery schedule that reduces waiting time and costs.\n\nMy details:\n- Port to Warehouse Freight Scheduling details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Ship arrival schedules & updates\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":215,"title":"Reverse Logistics Pickup Scheduling","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Create a reverse logistics route plan that reduces fuel costs and pickup times. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Reverse Logistics Pickup Scheduling\"\n\nStarting brief:\nYou are a Reverse Logistics Planner. Design a returns pickup schedule for Singapore:\n\nBusiness context:\nYou operate a large e-commerce returns processing centre in Singapore (think a Shopee or Lazada returns hub in Jurong). Customers schedule pickups for returned products, but routes are not optimised, causing multiple trips to the same area in a single day. You want a system that batches returns by locality and assigns them to the most efficient driver routes.\n\nDesired outcome:\nCreate a reverse logistics route plan that reduces fuel costs and pickup times.\n\nMy details:\n- Reverse Logistics Pickup Scheduling details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer return addresses and preferred pickup times\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":216,"title":"Festival Season Delivery Surge Plan","category":"Excel & Data","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Design a festive season delivery plan that ensures timely completion despite high order volume. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Festival Season Delivery Surge Plan\"\n\nStarting brief:\nYou are a Seasonal Logistics Strategist. Create a Chinese New Year delivery surge plan for Singapore:\n\nBusiness context:\nYour courier company in Singapore experiences a 3× spike in orders during Chinese New Year and the year-end festive period (Christmas and Hari Raya), with a high concentration of deliveries in HDB estates and condo developments. Previous years saw missed deadlines, rider fatigue, and excessive overtime costs. You want a surge-specific routing strategy that balances workload, maintains promised delivery times, and factors in lift-access constraints and pedestrian-heavy void decks during festive hours.\n\nDesired outcome:\nDesign a festive season delivery plan that ensures timely completion despite high order volume.\n\nMy details:\n- Festival Season Delivery Surge Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical order volume per area during Chinese New Year\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":217,"title":"AI Powered Food Delivery Routing","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Create a delivery assignment and routing system that aligns pickup timing with food readiness. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"AI Powered Food Delivery Routing\"\n\nStarting brief:\nYou are a FoodTech Logistics Expert. Design an AI-powered delivery routing model for Singapore:\n\nBusiness context:\nYou run a food delivery service in Singapore that partners with 200+ hawker stalls and restaurants across the island. Delays often occur because orders are assigned based on distance alone, without considering prep time or kitchen delays. This results in riders arriving too early or too late, lowering customer satisfaction. You want a smart dispatch system that factors in restaurant preparation time along with delivery route optimisation.\n\nDesired outcome:\nCreate a delivery assignment and routing system that aligns pickup timing with food readiness.\n\nMy details:\n- AI Powered Food Delivery Routing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Restaurant locations and prep time averages\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":218,"title":"Heavy Equipment Transport Scheduling","category":"CRM & Projects","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Plan compliant and efficient heavy equipment transport routes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Heavy Equipment Transport Scheduling\"\n\nStarting brief:\nYou are a Heavy Transport Planner. Create a movement schedule for large construction equipment across Singapore:\n\nBusiness context:\nYour construction logistics firm in Singapore moves large cranes, bulldozers, and cement mixers between project sites — typically between Tuas, Jurong Industrial, and CBD redevelopment zones. These vehicles require LTA permits and police escorts, and some roads are off-limits due to weight restrictions or off-peak movement rules. Poor planning often leads to rescheduling and fines. You need a compliance-first routing plan that ensures legal clearance while optimising travel distance and escort resource allocation.\n\nDesired outcome:\nPlan compliant and efficient heavy equipment transport routes.\n\nMy details:\n- Heavy Equipment Transport Scheduling details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Equipment dimensions and weight\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":219,"title":"Urban E Bike Courier Network","category":"CRM & Projects","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Beginner","explanation":"Optimise e-bike delivery routes for battery efficiency and speed. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Urban E Bike Courier Network\"\n\nStarting brief:\nYou are a Sustainable Logistics Planner. Create a delivery plan for e-bike couriers in Singapore:\n\nBusiness context:\nYour startup in Singapore uses electric bikes for last-mile delivery across the CBD, Orchard, and HDB heartland estates. The challenge is optimising battery usage while covering maximum orders per trip. Riders sometimes run low on charge before completing all deliveries, causing delays and reroutes. You need a system that plans routes according to both delivery clusters and battery capacity.\n\nDesired outcome:\nOptimise e-bike delivery routes for battery efficiency and speed.\n\nMy details:\n- Urban E Bike Courier Network details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Battery range per bike\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":220,"title":"Multi Warehouse Dispatch Planning","category":"Meetings","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Create a warehouse-aware routing and dispatch plan to reduce cost and delivery time. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Multi Warehouse Dispatch Planning\"\n\nStarting brief:\nYou are a Warehouse Dispatch Strategist. Build a multi-warehouse delivery plan for Singapore operations:\n\nBusiness context:\nYou operate an online furniture store with warehouses in Tuas, Jurong, and Changi serving Singapore and selected Southeast Asia markets. Orders are sometimes shipped from farther warehouses due to inventory mismatches, increasing delivery costs. You want a dispatch logic that selects the best warehouse for each order while still meeting delivery time commitments.\n\nDesired outcome:\nCreate a warehouse-aware routing and dispatch plan to reduce cost and delivery time.\n\nMy details:\n- Multi Warehouse Dispatch Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Warehouse locations and stock levels\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":221,"title":"Cold Chain Delivery Route Planning","category":"Excel & Data","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Advanced","explanation":"Design a cold chain delivery route that preserves product integrity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Cold Chain Delivery Route Planning\"\n\nStarting brief:\nYou are a Cold Chain Logistics Specialist. Plan delivery routes for chilled dairy products in Singapore:\n\nBusiness context:\nYou manage cold chain logistics for a dairy and chilled foods distributor in Singapore, supplying supermarkets like FairPrice, Cold Storage, and Sheng Siong. Deliveries must maintain a temperature of 4°C or below, and vehicle refrigeration systems consume extra fuel — particularly demanding given Singapore's tropical, year-round humid climate. Poor route planning leads to delays, risking spoilage and SFA compliance issues. You need an optimised cold chain routing plan that minimises travel time and ensures...\n\nDesired outcome:\nDesign a cold chain delivery route that preserves product integrity.\n\nMy details:\n- Cold Chain Delivery Route Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Vehicle refrigeration capacity\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":222,"title":"Postal Service Route Digitisation","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Digitise and optimise postal delivery route allocation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Postal Service Route Digitisation\"\n\nStarting brief:\nYou are a Postal Route Optimisation Expert. Design a digital route planning tool for SingPost's delivery operations:\n\nBusiness context:\nSingPost wants to modernise its daily route assignments for postmen across Singapore. Current paper-based route planning does not adapt to changing parcel volumes, leading to overburdened postmen in some zones (especially as e-commerce parcel volumes grow). You need to create a digital route assignment tool that automatically adjusts workloads in real time.\n\nDesired outcome:\nDigitise and optimise postal delivery route allocation.\n\nMy details:\n- Postal Service Route Digitisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Delivery addresses and volume per zone\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":223,"title":"B2B Wholesale Distribution Planning","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Create a variable-frequency delivery schedule that maximises resource use. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"B2B Wholesale Distribution Planning\"\n\nStarting brief:\nYou are a Wholesale Distribution Planner. Build a delivery plan for FMCG products across Singapore:\n\nBusiness context:\nYou run a wholesale FMCG distribution network in Singapore supplying over 300 retailers weekly — provision shops, minimarts, F&B outlets, and HDB heartland convenience stores. Some retailers order only once a week, while others order daily. Sending the same route daily wastes resources. You want a frequency-based route plan that schedules deliveries according to retailer order patterns.\n\nDesired outcome:\nCreate a variable-frequency delivery schedule that maximises resource use.\n\nMy details:\n- B2B Wholesale Distribution Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Retailer order frequency and volume\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":224,"title":"Event Equipment Logistics Planning","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Synchronise event equipment delivery with venue readiness. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Event Equipment Logistics Planning\"\n\nStarting brief:\nYou are an Event Logistics Coordinator. Create a delivery schedule for event equipment in Singapore:\n\nBusiness context:\nYou operate a logistics firm that supplies staging, lighting, and audio equipment for events across Singapore — from concerts at the National Stadium and Singapore Indoor Stadium to MICE events at Marina Bay Sands and Suntec. Events often require equipment to be delivered at specific times for setup, sometimes late at night. Current routing causes delays, and drivers sometimes arrive before venues are ready. You need a time-sensitive delivery plan that aligns with event schedules.\n\nDesired outcome:\nSynchronise event equipment delivery with venue readiness.\n\nMy details:\n- Event Equipment Logistics Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Event locations and setup timelines\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":225,"title":"Cross Border E Commerce Delivery","category":"Customer Comms","source":"Admin & Ops","module":"Route optimisation delivery scheduling","difficulty":"Intermediate","explanation":"Plan cross-border e-commerce delivery routes with accurate ETAs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Cross Border E Commerce Delivery\"\n\nStarting brief:\nYou are a Cross-Border Logistics Specialist. Develop a delivery plan from Singapore to Malaysia:\n\nBusiness context:\nYou manage cross-border deliveries from Singapore into Malaysia (Johor and beyond) for an e-commerce marketplace. Customs clearance delays at the Tuas and Woodlands checkpoints, plus varying road conditions on the North-South Expressway, cause unpredictable delivery times. You want a route and scheduling system that accounts for border wait times and provides accurate ETAs to customers.\n\nDesired outcome:\nPlan cross-border e-commerce delivery routes with accurate ETAs.\n\nMy details:\n- Cross Border E Commerce Delivery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Origin and destination cities\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":226,"title":"Upskilling Program for Experienced Agents","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Develop an upskilling program for seasoned customer support agents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Upskilling Program for Experienced Agents\"\n\nStarting brief:\n\"You are a corporate training designer. Create an upskilling program that includes:\n\nBusiness context:\nA BPO has agents who have been in their roles for over 5 years. While experienced, their skills haven't evolved to match newer technologies and customer expectations. Management wants an upskilling program to refresh and expand their capabilities.\n\nDesired outcome:\nDevelop an upskilling program for seasoned customer support agents.\n\nMy details:\n- Upskilling Program for Experienced Agents details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current skill assessment reports\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":227,"title":"RFQ for Bulk Raw Material Purchase","category":"Email & Writing","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Prepare a professional RFQ email for sourcing bulk raw materials. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Bulk Raw Material Purchase\"\n\nStarting brief:\n\"You are a procurement manager drafting an RFQ email for bulk packaging material. Your email should:\n\nBusiness context:\nA mid-sized FMCG manufacturer is scaling up production for the festive season and requires 50 tons of high-grade packaging material. They have identified a list of pre-qualified vendors but want to ensure they get competitive prices without compromising quality. The procurement team must clearly communicate specifications, delivery requirements, and payment terms so vendors can submit accurate quotes.\n\nDesired outcome:\nPrepare a professional RFQ email for sourcing bulk raw materials.\n\nMy details:\n- RFQ for Bulk Raw Material Purchase details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company name and short profile\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":228,"title":"RFQ for Office Furniture Supply","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Beginner","explanation":"Draft a detailed RFQ for procuring ergonomic office furniture. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Office Furniture Supply\"\n\nStarting brief:\n\"You are the office admin preparing an RFQ email for furniture vendors. Your email should:\n\nBusiness context:\nA new IT firm is setting up a 200-seat office space and requires ergonomic chairs, modular desks, and storage units. The HR and Admin teams want furniture that meets ergonomic standards, offers durability, and comes with a warranty. They will be sending this RFQ to multiple vendors to compare prices and delivery timelines.\n\nDesired outcome:\nDraft a detailed RFQ for procuring ergonomic office furniture.\n\nMy details:\n- RFQ for Office Furniture Supply details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of furniture items with specifications\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":229,"title":"RFQ for IT Hardware Procurement","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Create a detailed RFQ for sourcing IT hardware. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for IT Hardware Procurement\"\n\nStarting brief:\n\"You are the IT procurement officer preparing an RFQ email for IT hardware suppliers. Your email should:\n\nBusiness context:\nA growing SaaS startup is onboarding 50 new employees and needs laptops, docking stations, and monitors. They want reliable hardware with strong after-sales support and must ensure compatibility with their existing systems. The procurement lead is tasked with drafting an RFQ to shortlist suitable vendors.\n\nDesired outcome:\nCreate a detailed RFQ for sourcing IT hardware.\n\nMy details:\n- RFQ for IT Hardware Procurement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of required hardware items\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":230,"title":"RFQ for Logistics & Freight Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Beginner","explanation":"Prepare an RFQ email for domestic and regional logistics and freight services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Logistics & Freight Services\"\n\nStarting brief:\n\"You are the supply chain manager preparing an RFQ email to logistics companies. Your email should:\n\nBusiness context:\nA Singapore-based electronics distributor is expanding regionally across Southeast Asia and requires a reliable logistics partner for both inbound and outbound shipments. The company needs multi-modal transport options (sea + air + land) and must ensure strict adherence to delivery schedules to avoid delays in fulfilling customer orders. The RFQ should solicit pricing, delivery guarantees, and damage liability clauses from multiple logistics firms.\n\nDesired outcome:\nPrepare an RFQ email for domestic and regional logistics and freight services.\n\nMy details:\n- RFQ for Logistics & Freight Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of goods shipped\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":231,"title":"RFQ for Corporate Uniforms","category":"Excel & Data","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Beginner","explanation":"Draft an RFQ for sourcing custom corporate uniforms. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Corporate Uniforms\"\n\nStarting brief:\n\"You are the brand operations manager preparing an RFQ for uniform suppliers. Your email should:\n\nBusiness context:\nA regional hospitality chain headquartered in Singapore is rebranding and wants to roll out new uniforms for all front-line and back-office staff. They need a vendor who can handle custom designs, provide multiple size fittings, and ensure durable fabric quality for long-term use. The procurement team plans to distribute the uniforms across 20 properties spanning Singapore and Southeast Asia.\n\nDesired outcome:\nDraft an RFQ for sourcing custom corporate uniforms.\n\nMy details:\n- RFQ for Corporate Uniforms details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of uniform types\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":232,"title":"RFQ for Industrial Cleaning Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Create a comprehensive RFQ for industrial cleaning service providers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Industrial Cleaning Services\"\n\nStarting brief:\n\"You are the facility manager preparing an RFQ email for industrial cleaning vendors. Your email should:\n\nBusiness context:\nA large manufacturing facility requires monthly deep cleaning of production floors, warehouses, and administrative areas. Vendors must use industrial-grade cleaning equipment, adhere to occupational safety standards, and provide documentation of health and safety compliance. The RFQ must detail chemical usage guidelines and waste disposal processes.\n\nDesired outcome:\nCreate a comprehensive RFQ for industrial cleaning service providers.\n\nMy details:\n- RFQ for Industrial Cleaning Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Facility size and layout details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":233,"title":"RFQ for Corporate Catering","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Draft a vendor RFQ for daily corporate catering services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Corporate Catering\"\n\nStarting brief:\n\"You are the office admin preparing an RFQ email for corporate catering vendors. Your email should:\n\nBusiness context:\nA Singapore company with 500 employees wants to introduce a daily lunch service to improve employee satisfaction and health. They require vendors who can provide balanced meals, accommodate Singapore's diverse dietary needs (halal, vegetarian, no pork/no lard), and ensure timely delivery to their CBD office. The RFQ should request menus, cost per meal, and SFA hygiene compliance certifications.\n\nDesired outcome:\nDraft a vendor RFQ for daily corporate catering services.\n\nMy details:\n- RFQ for Corporate Catering details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees to serve\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":234,"title":"RFQ for Safety Equipment","category":"Email & Writing","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Draft a detailed RFQ for PPE procurement. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Safety Equipment\"\n\nStarting brief:\n\"You are the site safety officer preparing an RFQ email for PPE vendors. Your email should:\n\nBusiness context:\nA new infrastructure project in Singapore requires personal protective equipment (PPE) for all site workers. Items include helmets, gloves, safety shoes, and high-visibility jackets. Vendors must supply SS (Singapore Standard) / ISO-certified gear that meets MOM Workplace Safety and Health (WSH) requirements, and ensure timely delivery before project commencement.\n\nDesired outcome:\nDraft a detailed RFQ for PPE procurement.\n\nMy details:\n- RFQ for Safety Equipment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of PPE items and specifications\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":235,"title":"RFQ for Printing & Branding Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Create an RFQ for printing and branding services. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Printing & Branding Services\"\n\nStarting brief:\n\"You are the marketing manager preparing an RFQ for printing vendors. Your email should:\n\nBusiness context:\nA retail chain is launching a seasonal sale and needs banners, posters, and brochures printed in bulk. The vendor must deliver high-quality prints with color accuracy and meet strict deadlines to align with the campaign launch.\n\nDesired outcome:\nCreate an RFQ for printing and branding services.\n\nMy details:\n- RFQ for Printing & Branding Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of print materials with specifications\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":236,"title":"RFQ for Warehouse Management System (WMS)","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Prepare a detailed RFQ for a WMS vendor. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Warehouse Management System (WMS)\"\n\nStarting brief:\n\"You are the IT head drafting an RFQ email for WMS providers. Your email should:\n\nBusiness context:\nA logistics company is upgrading its warehouse operations and needs a software system to handle inventory management, shipment tracking, and integration with their ERP. The system must be scalable for future expansion and offer robust customer support.\n\nDesired outcome:\nPrepare a detailed RFQ for a WMS vendor.\n\nMy details:\n- RFQ for Warehouse Management System (WMS) details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Warehouse details (size\n- operations)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":237,"title":"RFQ for Office Furniture","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Prepare a comprehensive RFQ for office furniture suppliers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Office Furniture\"\n\nStarting brief:\n\"You are the admin manager drafting an RFQ email for furniture suppliers. Your email should:\n\nBusiness context:\nA rapidly growing tech startup is moving into a new workspace and needs ergonomic office furniture to support employee comfort and productivity. They are looking for bulk supply of desks, chairs, storage units, and meeting room tables. Vendors must offer warranty coverage and the ability to customize designs to match the company's branding.\n\nDesired outcome:\nPrepare a comprehensive RFQ for office furniture suppliers.\n\nMy details:\n- RFQ for Office Furniture details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Furniture type and quantity\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":238,"title":"RFQ for IT Hardware","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Draft an RFQ email for IT hardware procurement. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for IT Hardware\"\n\nStarting brief:\n\"You are the IT procurement lead preparing an RFQ for hardware suppliers. Your email should:\n\nBusiness context:\nA corporate office is upgrading its IT infrastructure to accommodate new hires. They require laptops, monitors, docking stations, and peripherals from reliable vendors who can offer volume discounts and post-purchase technical support.\n\nDesired outcome:\nDraft an RFQ email for IT hardware procurement.\n\nMy details:\n- RFQ for IT Hardware details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Hardware types and specifications\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":239,"title":"RFQ for Event Management Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Create a detailed RFQ for event management companies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Event Management Services\"\n\nStarting brief:\n\"You are the corporate communications head drafting an RFQ for event managers. Your email should:\n\nBusiness context:\nA company is planning a large annual conference for its partners and clients. They need an event management firm to handle venue booking, décor, catering, entertainment, and audio-visual setups. The chosen vendor must have experience in corporate events and a proven track record of managing large gatherings.\n\nDesired outcome:\nCreate a detailed RFQ for event management companies.\n\nMy details:\n- RFQ for Event Management Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Event date and duration\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":240,"title":"RFQ for Packaging Materials","category":"Excel & Data","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Prepare an RFQ for eco-friendly packaging material suppliers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Packaging Materials\"\n\nStarting brief:\n\"You are the operations head creating an RFQ for packaging vendors. Your email should:\n\nBusiness context:\nA Singapore-based e-commerce brand needs sustainable and durable packaging for shipping fragile items across Singapore and the Southeast Asia region. They want eco-friendly materials, custom branding on packaging, and bulk supply capacity. Vendors must comply with NEA (National Environment Agency) environmental regulations and Singapore's mandatory packaging reporting requirements.\n\nDesired outcome:\nPrepare an RFQ for eco-friendly packaging material suppliers.\n\nMy details:\n- RFQ for Packaging Materials details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Packaging types and sizes\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":241,"title":"RFQ for Solar Energy Installation","category":"Excel & Data","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Beginner","explanation":"Draft an RFQ for solar energy installation providers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Solar Energy Installation\"\n\nStarting brief:\n\"You are the facility energy manager preparing an RFQ for solar installation companies. Your email should:\n\nBusiness context:\nA manufacturing plant wants to reduce energy costs by installing a solar power system. They require a vendor who can design, supply, and install the system, handle government approvals, and provide long-term maintenance.\n\nDesired outcome:\nDraft an RFQ for solar energy installation providers.\n\nMy details:\n- RFQ for Solar Energy Installation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":242,"title":"RFQ for Corporate Catering Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Draft an RFQ for corporate meal catering vendors. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Corporate Catering Services\"\n\nStarting brief:\n\"You are the admin lead preparing an RFQ for catering vendors. Your email should:\n\nBusiness context:\nA multinational company with its regional headquarters in Singapore is looking for a reliable catering partner to serve daily meals to 300 employees at its corporate office. The menu must include halal, vegetarian, and non-halal options reflecting Singapore's multicultural workforce, with strict SFA hygiene standards. The company is seeking a vendor who can deliver variety, nutritional balance, and competitive pricing.\n\nDesired outcome:\nDraft an RFQ for corporate meal catering vendors.\n\nMy details:\n- RFQ for Corporate Catering Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees to be served\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":243,"title":"RFQ for Digital Marketing Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Prepare an RFQ for digital marketing agencies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Digital Marketing Services\"\n\nStarting brief:\n\"You are the brand manager preparing an RFQ for digital marketing vendors. Your email should:\n\nBusiness context:\nA mid-sized retail brand wants to expand its online presence through SEO, social media campaigns, and influencer collaborations. They need a digital marketing agency that can create and execute a 6-month strategy with measurable KPIs.\n\nDesired outcome:\nPrepare an RFQ for digital marketing agencies.\n\nMy details:\n- RFQ for Digital Marketing Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Brand overview and objectives\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":244,"title":"RFQ for Uniform Supply","category":"Email & Writing","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Beginner","explanation":"Draft an RFQ for uniform suppliers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Uniform Supply\"\n\nStarting brief:\n\"You are the procurement manager creating an RFQ for uniform suppliers. Your email should:\n\nBusiness context:\nA hotel chain is looking for a vendor to supply uniforms for its staff across multiple locations. The uniforms must be durable, easy to maintain, and aligned with the brand's colors and style guidelines.\n\nDesired outcome:\nDraft an RFQ for uniform suppliers.\n\nMy details:\n- RFQ for Uniform Supply details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of staff roles and uniform types\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":245,"title":"RFQ for Warehouse Management System","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Create an RFQ for WMS software vendors. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Warehouse Management System\"\n\nStarting brief:\n\"You are the operations IT head drafting an RFQ for WMS providers. Your email should:\n\nBusiness context:\nA distribution company needs a robust Warehouse Management System (WMS) to handle inventory tracking, order processing, and reporting. They are looking for vendors with experience in integrating WMS into existing ERP systems.\n\nDesired outcome:\nCreate an RFQ for WMS software vendors.\n\nMy details:\n- RFQ for Warehouse Management System details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current warehouse operations description\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":246,"title":"RFQ for Corporate Travel Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Draft an RFQ for corporate travel agencies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Corporate Travel Services\"\n\nStarting brief:\n\"You are the admin coordinator preparing an RFQ for corporate travel providers. Your email should:\n\nBusiness context:\nA consultancy firm requires a travel management partner to handle domestic and international bookings for 100+ employees. They want negotiated rates, 24/7 support, and expense reporting.\n\nDesired outcome:\nDraft an RFQ for corporate travel agencies.\n\nMy details:\n- RFQ for Corporate Travel Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual travel volume estimates\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":247,"title":"RFQ for Security Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Prepare an RFQ for security service providers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Security Services\"\n\nStarting brief:\n\"You are the facility manager preparing an RFQ for security vendors. Your email should:\n\nBusiness context:\nA manufacturing facility needs 24/7 on-site security personnel, CCTV monitoring, and access control systems. They require a vendor with licensed and trained security staff, plus the ability to integrate technology into security operations.\n\nDesired outcome:\nPrepare an RFQ for security service providers.\n\nMy details:\n- RFQ for Security Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Security service scope\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":248,"title":"RFQ for Printing & Branding","category":"Research","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Draft an RFQ for printing and branding vendors. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Printing & Branding\"\n\nStarting brief:\n\"You are the marketing manager drafting an RFQ for printing vendors. Your email should:\n\nBusiness context:\nA company is launching a marketing campaign and needs a vendor to handle printing of brochures, banners, and merchandise branding. They require high-quality printing with fast turnaround times.\n\nDesired outcome:\nDraft an RFQ for printing and branding vendors.\n\nMy details:\n- RFQ for Printing & Branding details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Printing items and specs\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":249,"title":"RFQ for HVAC Maintenance","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Advanced","explanation":"Create an RFQ for HVAC maintenance providers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for HVAC Maintenance\"\n\nStarting brief:\n\"You are the facility operations lead preparing an RFQ for HVAC maintenance. Your email should:\n\nBusiness context:\nA corporate building requires regular maintenance for its HVAC systems to ensure efficiency and air quality. The vendor must offer quarterly inspections, emergency repairs, and compliance with safety standards.\n\nDesired outcome:\nCreate an RFQ for HVAC maintenance providers.\n\nMy details:\n- RFQ for HVAC Maintenance details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- HVAC system details\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":250,"title":"RFQ for Logistics Services","category":"Customer Comms","source":"Admin & Ops","module":"Vendor RFQs sourcing emails","difficulty":"Intermediate","explanation":"Draft an RFQ for logistics vendors. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"RFQ for Logistics Services\"\n\nStarting brief:\n\"You are the supply chain manager preparing an RFQ for logistics companies. Your email should:\n\nBusiness context:\nA retail chain wants a logistics partner to handle warehousing and last-mile delivery across multiple cities. They require scalability, technology-enabled tracking, and cost efficiency.\n\nDesired outcome:\nDraft an RFQ for logistics vendors.\n\nMy details:\n- RFQ for Logistics Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Delivery locations and frequency\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":251,"title":"Prompt 1 – Conflict Between Two Team Members Over Credit for Work","category":"Meetings","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a step-by-step script for mediating a dispute between two employees over project credit, ensuring both feel heard and valued while focusing on collective team success. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 1 – Conflict Between Two Team Members Over Credit for Work\"\n\nStarting brief:\nYou are an HR conflict resolution specialist. Draft a mediation script for a manager to resolve a dispute between two team members over credit for a successful project. The script should include:\n\nBusiness context:\nIn a digital marketing agency in Singapore's CBD, two young executives — both in their late 20s — have been working on a high-profile campaign for a luxury brand. After the campaign's success, both claimed to have been the primary contributor. The disagreement has escalated into passive-aggressive emails and visible tension in team meetings. The account manager needs a conflict resolution script to address both parties, ensure credit is shared fairly, and restore team harmony without causing further resentment.\n\nDesired outcome:\nCreate a step-by-step script for mediating a dispute between two employees over project credit, ensuring both feel heard and valued while focusing on collective team success.\n\nMy details:\n- Prompt 1 – Conflict Between Two Team Members Over Credit for Work details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Details of the project\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":252,"title":"Prompt 2 – Manager Employee Conflict Over Workload","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Create a resolution script that facilitates open conversation between the employee and manager, balancing workload expectations with employee well-being. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 2 – Manager Employee Conflict Over Workload\"\n\nStarting brief:\nYou are a workplace mediator. Draft a conflict resolution script for a meeting between a manager and an employee over workload concerns. The script should include:\n\nBusiness context:\nA 29-year-old software developer at a one-north tech company in Singapore feels overwhelmed by unrealistic deadlines set by their project manager. They believe the workload distribution is unfair compared to other team members. The manager, however, thinks the developer is underestimating their own capacity. Tension has been building over months, leading to disengagement and missed deadlines.\n\nDesired outcome:\nCreate a resolution script that facilitates open conversation between the employee and manager, balancing workload expectations with employee well-being.\n\nMy details:\n- Prompt 2 – Manager Employee Conflict Over Workload details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current project deadlines and workload distribution\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":253,"title":"Prompt 3 – Conflict Over Remote Work vs. In Office Policy","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Draft a resolution script that helps both parties find a workable compromise, maintaining productivity while addressing personal needs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 3 – Conflict Over Remote Work vs. In Office Policy\"\n\nStarting brief:\nYou are an HR policy mediator. Draft a conflict resolution script between an employee and a manager over remote work flexibility. The script should include:\n\nBusiness context:\nA fintech startup at Marina Bay in Singapore recently implemented a mandatory 3-day in-office policy. A 30-year-old senior analyst, who has been performing exceptionally well remotely, feels the policy is unnecessary and disruptive to their work-life balance. The department head insists on in-person collaboration for better team synergy. The disagreement has reached HR, and a mediation is scheduled.\n\nDesired outcome:\nDraft a resolution script that helps both parties find a workable compromise, maintaining productivity while addressing personal needs.\n\nMy details:\n- Prompt 3 – Conflict Over Remote Work vs. In Office Policy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company's hybrid work policy\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":254,"title":"Prompt 4 – Cultural Misunderstanding Between Team Members","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Create a culturally sensitive conflict resolution script to clear misunderstandings and improve collaboration. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 4 – Cultural Misunderstanding Between Team Members\"\n\nStarting brief:\n\"You are an intercultural workplace coach. Draft a conflict resolution script for addressing a cultural communication misunderstanding between two colleagues. The script should include:\n\nBusiness context:\nIn a multinational IT firm in Singapore's Changi Business Park, a 27-year-old local team lead and a 31-year-old expat colleague have had recurring misunderstandings during project discussions. The expat team member feels the lead's communication style is too direct and abrupt, while the lead finds the colleague's indirectness frustrating. The tension is starting to impact project delivery timelines.\n\nDesired outcome:\nCreate a culturally sensitive conflict resolution script to clear misunderstandings and improve collaboration.\n\nMy details:\n- Prompt 4 – Cultural Misunderstanding Between Team Members details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Examples of past misunderstandings\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":255,"title":"Prompt 5 – Disagreement Between Sales and Operations Teams","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a conflict resolution script for a joint meeting between sales and operations to establish realistic commitments and improve interdepartmental trust. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 5 – Disagreement Between Sales and Operations Teams\"\n\nStarting brief:\n\"You are a cross-functional collaboration facilitator. Draft a mediation script for resolving recurring conflicts between sales and operations teams. The script should include:\n\nBusiness context:\nA large FMCG company headquartered in Singapore is facing friction between its sales and operations teams. Sales promises quick delivery timelines to clients to close deals, while operations struggles to meet these commitments due to supply chain constraints. The ongoing blame game is affecting customer satisfaction and internal morale.\n\nDesired outcome:\nDraft a conflict resolution script for a joint meeting between sales and operations to establish realistic commitments and improve interdepartmental trust.\n\nMy details:\n- Prompt 5 – Disagreement Between Sales and Operations Teams details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current sales promises and delivery records\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":256,"title":"Prompt 6 – Conflict Over Budget Allocation Between Departments","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a conflict resolution script that helps both departments understand each other's priorities and reach a balanced allocation decision. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 6 – Conflict Over Budget Allocation Between Departments\"\n\nStarting brief:\nYou are a corporate budget mediator. Draft a step-by-step script for resolving a dispute between two departments over quarterly budget allocation. Include:\n\nBusiness context:\nIn a mid-sized health-tech company based in Singapore's one-north, the R&D department and the Marketing team are clashing over budget distribution for the next quarter. R&D argues that more funds are needed for product improvements to maintain competitiveness, while Marketing insists on higher budgets for promotional campaigns to boost sales. The CEO has asked the operations head to mediate before the disagreement escalates into open hostility.\n\nDesired outcome:\nCreate a conflict resolution script that helps both departments understand each other's priorities and reach a balanced allocation decision.\n\nMy details:\n- Prompt 6 – Conflict Over Budget Allocation Between Departments details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current quarterly budget\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":257,"title":"Prompt 7 – Interpersonal Clash Between New Joiner and Senior Employee","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Draft a conflict resolution script that helps bridge the experience gap while fostering respect and collaboration. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 7 – Interpersonal Clash Between New Joiner and Senior Employee\"\n\nStarting brief:\nYou are an HR culture coach. Draft a mediation script for addressing tension between a new joiner and a senior team member. Include:\n\nBusiness context:\nA 25-year-old new recruit at a Singapore-based e-commerce startup in Paya Lebar feels undermined by a senior colleague who often dismisses their ideas in meetings. The senior employee claims the new joiner lacks industry experience and should \"learn first, suggest later.\" The growing tension is creating an unhealthy team environment.\n\nDesired outcome:\nDraft a conflict resolution script that helps bridge the experience gap while fostering respect and collaboration.\n\nMy details:\n- Prompt 7 – Interpersonal Clash Between New Joiner and Senior Employee details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Employee tenure and roles\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":258,"title":"Prompt 8 – Conflict Between Team Leads Over Resource Sharing","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a resolution script to fairly allocate shared resources while minimizing delays and ensuring business priorities are met. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 8 – Conflict Between Team Leads Over Resource Sharing\"\n\nStarting brief:\nYou are a project resource allocation mediator. Draft a resolution script for two team leads disputing over shared resource usage. Include:\n\nBusiness context:\nIn a Singapore-based SaaS firm at one-north, two team leads are at odds over sharing a key software developer between their projects. Each believes their project is more critical to the company's success. The resource allocation dispute has already caused delays in both projects.\n\nDesired outcome:\nCreate a resolution script to fairly allocate shared resources while minimizing delays and ensuring business priorities are met.\n\nMy details:\n- Prompt 8 – Conflict Between Team Leads Over Resource Sharing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project timelines and deadlines\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":259,"title":"Prompt 9 – Conflict Due to Micromanagement","category":"Meetings","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a resolution script that addresses concerns over micromanagement while maintaining accountability. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 9 – Conflict Due to Micromanagement\"\n\nStarting brief:\nYou are a workplace relationship facilitator. Draft a conflict resolution script for a meeting between a manager and an employee over micromanagement concerns. Include:\n\nBusiness context:\nA 28-year-old designer at a Singapore-based branding agency in Tanjong Pagar feels suffocated by a manager who constantly checks in on their work progress. The manager argues they are just ensuring quality and meeting deadlines, but the designer perceives it as a lack of trust. The relationship is strained, and productivity is dropping.\n\nDesired outcome:\nDraft a resolution script that addresses concerns over micromanagement while maintaining accountability.\n\nMy details:\n- Prompt 9 – Conflict Due to Micromanagement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of check-ins currently happening per week\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":260,"title":"Prompt 10 – Conflict Between Co Founders Over Strategic Direction","category":"Meetings","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a resolution script to help co-founders align on a unified strategic direction. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 10 – Conflict Between Co Founders Over Strategic Direction\"\n\nStarting brief:\n\"You are a startup strategy mediator. Draft a resolution script for a meeting between two co-founders with differing growth strategies. Include:\n\nBusiness context:\nTwo co-founders of a Singapore-based edtech startup at one-north, both aged 32, are disagreeing on the next growth phase. One believes the company should focus on scaling fast across Southeast Asia, while the other insists on strengthening the core product first. The ongoing disagreement is confusing the leadership team and stalling decision-making.\n\nDesired outcome:\nCreate a resolution script to help co-founders align on a unified strategic direction.\n\nMy details:\n- Prompt 10 – Conflict Between Co Founders Over Strategic Direction details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current company growth metrics\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":261,"title":"Prompt 11 – Customer Service & Product Team Misalignment","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a resolution script that improves collaboration and establishes clear roles between the two teams. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 11 – Customer Service & Product Team Misalignment\"\n\nStarting brief:\nYou are a cross-functional problem-solving facilitator. Draft a script for a joint meeting between customer service and product teams to address recurring customer issue disputes. Include:\n\nBusiness context:\nAt a consumer electronics company based in Singapore's Jurong, the customer service team blames the product team for frequent issues, while the product team accuses customer service of poor troubleshooting. The constant blame-shifting has resulted in delayed issue resolution and frustrated customers.\n\nDesired outcome:\nDraft a resolution script that improves collaboration and establishes clear roles between the two teams.\n\nMy details:\n- Prompt 11 – Customer Service & Product Team Misalignment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Examples of recent disputes\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":262,"title":"Prompt 12 – Conflict Over Meeting Schedules","category":"Meetings","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Create a resolution script to find an equitable meeting schedule that accommodates time zones fairly. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 12 – Conflict Over Meeting Schedules\"\n\nStarting brief:\nYou are a global team meeting facilitator. Draft a resolution script for addressing time zone meeting conflicts. Include:\n\nBusiness context:\nA project team at a Singapore-headquartered firm has members working across multiple time zones spanning Asia, Europe and the Americas. A 27-year-old team member based in Singapore feels excluded because most meetings are scheduled late at night in their time zone to accommodate Western counterparts. The project manager argues the schedule is optimal for the majority. Frustration is building, with the team member threatening to step back from the project.\n\nDesired outcome:\nCreate a resolution script to find an equitable meeting schedule that accommodates time zones fairly.\n\nMy details:\n- Prompt 12 – Conflict Over Meeting Schedules details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current meeting schedule\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":263,"title":"Prompt 13 – Disagreement Between HR and Department Heads on Hiring Needs","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a resolution script that balances cost control with operational efficiency. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 13 – Disagreement Between HR and Department Heads on Hiring Needs\"\n\nStarting brief:\nYou are a workforce planning mediator. Draft a script for resolving a hiring needs dispute between HR and department heads. Include:\n\nBusiness context:\nIn a Singapore manufacturing firm based in Tuas, HR wants to slow down hiring to manage costs, while department heads argue that understaffing is hurting productivity. The standoff is delaying recruitment decisions and increasing stress on existing employees.\n\nDesired outcome:\nDraft a resolution script that balances cost control with operational efficiency.\n\nMy details:\n- Prompt 13 – Disagreement Between HR and Department Heads on Hiring Needs details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current staffing levels\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":264,"title":"Prompt 14 – Conflict Over Creative Direction in a Marketing Campaign","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a resolution script that aligns creative and business priorities. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 14 – Conflict Over Creative Direction in a Marketing Campaign\"\n\nStarting brief:\nYou are a creative-business alignment coach. Draft a conflict resolution script for a marketing vs. creative team dispute. Include:\n\nBusiness context:\nIn a Singapore-based fashion brand headquartered in Orchard, the marketing head and creative director disagree over the campaign theme for the upcoming season. The marketing head wants a mass-market appeal, while the creative director wants an artistic, niche approach. The launch date is near, and delays are becoming costly.\n\nDesired outcome:\nCreate a resolution script that aligns creative and business priorities.\n\nMy details:\n- Prompt 14 – Conflict Over Creative Direction in a Marketing Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Campaign objectives\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":265,"title":"Prompt 15 – Dispute Over Performance Metrics","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a resolution script to reassess and agree on performance metrics that are both ambitious and fair. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 15 – Dispute Over Performance Metrics\"\n\nStarting brief:\nYou are a performance management facilitator. Draft a mediation script for resolving disputes over performance metrics. Include:\n\nBusiness context:\nAt a logistics firm based in Tuas, Singapore, the operations team feels the performance metrics set by the management are unrealistic and demotivating. Management insists the targets are achievable based on industry benchmarks. The disagreement has led to a drop in morale and growing friction.\n\nDesired outcome:\nDraft a resolution script to reassess and agree on performance metrics that are both ambitious and fair.\n\nMy details:\n- Prompt 15 – Dispute Over Performance Metrics details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current performance metrics\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":266,"title":"Prompt 16 – Conflict Over Remote Work vs. Office Attendance","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Draft a resolution script that balances flexibility with team cohesion. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 16 – Conflict Over Remote Work vs. Office Attendance\"\n\nStarting brief:\nYou are a workplace flexibility mediator. Draft a resolution script for addressing disputes over remote work vs. office attendance. Include:\n\nBusiness context:\nA Singapore fintech startup based in the CBD implemented a hybrid work policy, but one team wants to work fully remotely, citing productivity and commute savings. The leadership insists on at least three days in the office for better collaboration. Frustrations are rising, with threats of resignation from some employees.\n\nDesired outcome:\nDraft a resolution script that balances flexibility with team cohesion.\n\nMy details:\n- Prompt 16 – Conflict Over Remote Work vs. Office Attendance details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Productivity data\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":267,"title":"Prompt 17 – Disagreement Between Finance and Operations Over Expense Approvals","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a script to streamline approvals without compromising financial control. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 17 – Disagreement Between Finance and Operations Over Expense Approvals\"\n\nStarting brief:\nYou are a process efficiency coach. Draft a conflict resolution script for finance and operations over expense approval delays. Include:\n\nBusiness context:\nIn a Singapore manufacturing firm based in Jurong, finance insists on strict pre-approval for all expenses, while operations complains that delays in approvals disrupt urgent purchases. The tension is slowing down projects and creating mutual resentment.\n\nDesired outcome:\nCreate a script to streamline approvals without compromising financial control.\n\nMy details:\n- Prompt 17 – Disagreement Between Finance and Operations Over Expense Approvals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current approval workflow\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":268,"title":"Prompt 18 – Conflict Over Role Overlap Between Departments","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a resolution script to clearly define roles and prevent overlap. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 18 – Conflict Over Role Overlap Between Departments\"\n\nStarting brief:\nYou are an organizational role clarity consultant. Draft a resolution script for overlapping responsibilities between two teams. Include:\n\nBusiness context:\nIn a Singapore-based BPO operating out of Paya Lebar, the sales and account management teams are clashing over client communication responsibilities. Both teams sometimes duplicate efforts or contradict each other in client calls, confusing customers.\n\nDesired outcome:\nDraft a resolution script to clearly define roles and prevent overlap.\n\nMy details:\n- Prompt 18 – Conflict Over Role Overlap Between Departments details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current task lists of each team\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":269,"title":"Prompt 19 – Dispute Over Bonus Allocation","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Advanced","explanation":"Create a resolution script that establishes a fair, transparent bonus structure. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 19 – Dispute Over Bonus Allocation\"\n\nStarting brief:\nYou are a compensation strategy mediator. Draft a resolution script for conflicting views on bonus allocation. Include:\n\nBusiness context:\nIn a Singapore software firm based in one-north, the product team believes bonuses should be tied to collective project success, while the sales team insists on individual sales performance. HR is stuck mediating the disagreement before the annual payout.\n\nDesired outcome:\nCreate a resolution script that establishes a fair, transparent bonus structure.\n\nMy details:\n- Prompt 19 – Dispute Over Bonus Allocation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current bonus pool\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":270,"title":"Prompt 20 – Disagreement Between Marketing and Legal Over Campaign Messaging","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Advanced","explanation":"Draft a resolution script to align creative ambition with legal compliance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 20 – Disagreement Between Marketing and Legal Over Campaign Messaging\"\n\nStarting brief:\nYou are a compliance-creative alignment coach. Draft a resolution script for marketing and legal over ad campaign messaging. Include:\n\nBusiness context:\nA Singapore tech startup's marketing team wants edgy, bold messaging for a product launch. The legal team warns some taglines may breach advertising regulations under ASAS and IMDA guidelines. The launch date is close, and both teams feel the other is being unreasonable.\n\nDesired outcome:\nDraft a resolution script to align creative ambition with legal compliance.\n\nMy details:\n- Prompt 20 – Disagreement Between Marketing and Legal Over Campaign Messaging details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Campaign slogans proposed\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":271,"title":"Prompt 21 – Conflict Over Team Workload Distribution","category":"Excel & Data","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Create a script to re-balance workloads fairly. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 21 – Conflict Over Team Workload Distribution\"\n\nStarting brief:\nYou are a workload balancing facilitator. Draft a resolution script for redistributing tasks in a team. Include:\n\nBusiness context:\nIn a Singapore digital agency based in Tanjong Pagar, some team members feel overburdened while others are perceived as underutilized. Resentment is growing, and deadlines are slipping because work is unevenly allocated.\n\nDesired outcome:\nCreate a script to re-balance workloads fairly.\n\nMy details:\n- Prompt 21 – Conflict Over Team Workload Distribution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Task allocation chart\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":272,"title":"Prompt 22 – Disagreement Over Tool Adoption","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a script to resolve resistance and agree on tool adoption. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 22 – Disagreement Over Tool Adoption\"\n\nStarting brief:\nYou are a change management facilitator. Draft a resolution script for adopting new tools. Include:\n\nBusiness context:\nA Singapore consulting firm's IT team wants to roll out a new project management tool. The delivery teams resist, citing learning curve and disruption. The standoff is delaying implementation.\n\nDesired outcome:\nDraft a script to resolve resistance and agree on tool adoption.\n\nMy details:\n- Prompt 22 – Disagreement Over Tool Adoption details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Tool features\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":273,"title":"Prompt 23 – Conflict Between Manager and HR Over Disciplinary Action","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Intermediate","explanation":"Draft a resolution script that ensures due process while addressing performance issues. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 23 – Conflict Between Manager and HR Over Disciplinary Action\"\n\nStarting brief:\nYou are an HR-policy mediator. Draft a conflict resolution script for disputes over disciplinary action. Include:\n\nBusiness context:\nIn a Singapore hospitality company operating a hotel along Sentosa, a manager wants to fire an underperforming employee immediately, while HR insists on following a formal improvement process aligned with the Employment Act and MOM guidelines. The disagreement is delaying action and frustrating both sides.\n\nDesired outcome:\nDraft a resolution script that ensures due process while addressing performance issues.\n\nMy details:\n- Prompt 23 – Conflict Between Manager and HR Over Disciplinary Action details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Employee performance records\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":274,"title":"Prompt 24 – Conflict Over Leadership Style","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Beginner","explanation":"Create a script to bridge leadership style differences. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 24 – Conflict Over Leadership Style\"\n\nStarting brief:\nYou are a leadership adaptation coach. Draft a resolution script for leadership style clashes. Include:\n\nBusiness context:\nAt a Singapore IT firm based in Changi Business Park, a new department head's direct, results-driven style is clashing with a team used to a more collaborative, nurturing leader. Misunderstandings and resignations are becoming a risk.\n\nDesired outcome:\nCreate a script to bridge leadership style differences.\n\nMy details:\n- Prompt 24 – Conflict Over Leadership Style details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team performance metrics\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":275,"title":"Prompt 25 – Inter Generational Workplace Conflict","category":"Customer Comms","source":"Admin & Ops","module":"Conflict resolution scripts","difficulty":"Advanced","explanation":"Draft a resolution script to integrate innovative thinking with proven approaches. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 25 – Inter Generational Workplace Conflict\"\n\nStarting brief:\nYou are a workplace culture integrator. Draft a resolution script for inter-generational team conflicts. Include:\n\nBusiness context:\nIn a Singapore design agency based in Tiong Bahru, younger employees prefer rapid experimentation, while older employees emphasize tried-and-tested methods. The cultural gap is creating frustration and slowing decision-making.\n\nDesired outcome:\nDraft a resolution script to integrate innovative thinking with proven approaches.\n\nMy details:\n- Prompt 25 – Inter Generational Workplace Conflict details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team demographics\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":276,"title":"Festival Themed Virtual Engagement Plan","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Create a detailed festival-themed virtual engagement plan that celebrates Chinese New Year while fostering team spirit, inclusivity, and creativity in a remote setting. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Festival Themed Virtual Engagement Plan\"\n\nStarting brief:\nYou are an HR culture strategist. Create a virtual Chinese New Year engagement plan for a remote team of 15 people spread across Singapore and Southeast Asia. Include:\n\nBusiness context:\nPriya, 29, leads a fully remote design team across Singapore and the wider Southeast Asian region. The team members work from different home offices and rarely meet in person, which has led to a feeling of disconnection. With Chinese New Year approaching, Priya wants to organise a virtual engagement plan that celebrates the festival while boosting team bonding. She is looking for creative activities that combine fun, cultural connection, and light-hearted competition.\n\nDesired outcome:\nCreate a detailed festival-themed virtual engagement plan that celebrates Chinese New Year while fostering team spirit, inclusivity, and creativity in a remote setting.\n\nMy details:\n- Festival Themed Virtual Engagement Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of team members\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":277,"title":"Wellness Week for a Corporate Office","category":"Productivity","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Design a 5-day wellness engagement program that encourages employees to participate without feeling pressured, combining physical fitness, mindfulness, and nutrition. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Wellness Week for a Corporate Office\"\n\nStarting brief:\nYou are a workplace wellness consultant. Create a 'Wellness Week' plan for 100 employees in a corporate office. The plan should include:\n\nBusiness context:\nAaron, 33, is an HR executive at a tech company in one-north, Singapore. Many employees have complained of burnout and back pain due to long hours of sitting. Management wants to address wellness in a way that's fun, not preachy. Aaron is tasked with organising a \"Wellness Week\" that includes both physical and mental health activities.\n\nDesired outcome:\nDesign a 5-day wellness engagement program that encourages employees to participate without feeling pressured, combining physical fitness, mindfulness, and nutrition.\n\nMy details:\n- Wellness Week for a Corporate Office details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":278,"title":"Cross Department Collaboration Challenge","category":"Research","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Develop a one-week cross-department collaboration program that fosters idea-sharing, creativity, and healthy competition. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Cross Department Collaboration Challenge\"\n\nStarting brief:\nYou are a corporate engagement specialist. Create a 'Collaboration Challenge' for 80 employees across 4 departments. The program should:\n\nBusiness context:\nMei Ling, 27, recently joined as an engagement coordinator at a mid-sized FMCG company in Singapore. She noticed that employees mostly interact within their own departments, which limits idea exchange and innovation. She wants to design a fun \"Collaboration Challenge\" that encourages employees from different teams to work together.\n\nDesired outcome:\nDevelop a one-week cross-department collaboration program that fosters idea-sharing, creativity, and healthy competition.\n\nMy details:\n- Cross Department Collaboration Challenge details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":279,"title":"Employee Birthday Celebration Calendar","category":"Excel & Data","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Create an annual employee birthday celebration plan that is budget-friendly and personalised. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Employee Birthday Celebration Calendar\"\n\nStarting brief:\nYou are a workplace culture consultant. Design a 12-month employee birthday celebration calendar for a team of 50 people. Include:\n\nBusiness context:\nKar Wei, 31, works in HR at a start-up in the Singapore CBD. Employees often forget each other's birthdays due to hectic schedules, which misses opportunities for bonding. Kar Wei wants a simple but memorable birthday engagement plan that makes each employee feel valued without spending much.\n\nDesired outcome:\nCreate an annual employee birthday celebration plan that is budget-friendly and personalised.\n\nMy details:\n- Employee Birthday Celebration Calendar details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":280,"title":"Gamified Learning Program","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Create a gamified corporate learning plan that encourages employees to actively participate and retain knowledge. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Gamified Learning Program\"\n\nStarting brief:\nYou are a corporate learning designer. Create a gamified training program for 200 employees that:\n\nBusiness context:\nSonia, 28, is an L&D (Learning and Development) officer at a large IT company in Singapore's Changi Business Park. Many employees attend training sessions but forget most of the content after a few weeks. She wants to make learning fun by gamifying the process and offering rewards for consistent participation.\n\nDesired outcome:\nCreate a gamified corporate learning plan that encourages employees to actively participate and retain knowledge.\n\nMy details:\n- Gamified Learning Program details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":281,"title":"Office Décor Competition","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Design a team-based office décor challenge that encourages creativity, collaboration, and pride in the workplace. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Office Décor Competition\"\n\nStarting brief:\nYou are a workplace engagement designer. Create an 'Office Décor Competition' plan for 60 employees divided into 6 teams. The plan should:\n\nBusiness context:\nRyan, 30, works at a creative agency in one-north, Singapore. The office environment has started to feel dull, with blank walls and outdated furniture. Ryan believes a lively, visually stimulating workspace can boost motivation. He wants to run an \"Office Décor Competition\" where teams can transform their work areas into inspiring zones.\n\nDesired outcome:\nDesign a team-based office décor challenge that encourages creativity, collaboration, and pride in the workplace.\n\nMy details:\n- Office Décor Competition details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of teams\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":282,"title":"‘Lunch & Learn’ Knowledge Sharing","category":"Productivity","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Create a monthly \"Lunch & Learn\" program that encourages peer-to-peer learning in a relaxed, social setting. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"‘Lunch & Learn’ Knowledge Sharing\"\n\nStarting brief:\nYou are a workplace learning consultant. Design a 12-month 'Lunch & Learn' plan for 40 employees. The program should:\n\nBusiness context:\nShermaine, 32, manages HR at a fintech company in Marina Bay, Singapore. She wants employees to learn from each other's skills without it feeling like another mandatory training. She envisions short, interactive lunch sessions where employees present topics they're passionate about — from investing tips to photography.\n\nDesired outcome:\nCreate a monthly \"Lunch & Learn\" program that encourages peer-to-peer learning in a relaxed, social setting.\n\nMy details:\n- ‘Lunch & Learn’ Knowledge Sharing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":283,"title":"CSR Volunteering Day","category":"Productivity","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Plan a corporate volunteering day that blends social impact with team bonding. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"CSR Volunteering Day\"\n\nStarting brief:\nYou are a CSR engagement strategist. Create a 1-day corporate volunteering plan for 100 employees. The plan should:\n\nBusiness context:\nDaniel, 34, is the CSR lead at a manufacturing company in Tuas, Singapore. He wants employees to feel more connected to the company's values by participating in a hands-on volunteering day. His challenge is to make it enjoyable and impactful, rather than just another formality.\n\nDesired outcome:\nPlan a corporate volunteering day that blends social impact with team bonding.\n\nMy details:\n- CSR Volunteering Day details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of volunteers\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":284,"title":"Monthly Recognition Wall","category":"Research","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Create a recognition system that is public, interactive, and ongoing throughout the year. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Monthly Recognition Wall\"\n\nStarting brief:\nYou are a workplace culture consultant. Design a 'Monthly Recognition Wall' program for a company of 80 employees. The program should:\n\nBusiness context:\nTanya, 26, is an HR associate in a mid-size marketing firm in the Singapore CBD. While the company gives annual awards, she notices employees crave more frequent recognition. She wants a visible and interactive way to celebrate small wins every month.\n\nDesired outcome:\nCreate a recognition system that is public, interactive, and ongoing throughout the year.\n\nMy details:\n- Monthly Recognition Wall details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":285,"title":"Department Swap Day","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Encourage cross-functional understanding through a fun, role-swapping activity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Department Swap Day\"\n\nStarting brief:\nYou are a team culture facilitator. Create a 'Department Swap Day' plan for 50 employees across 5 departments. The plan should:\n\nBusiness context:\nAdrian, 29, works at a large logistics company in Jurong, Singapore. Employees often don't understand what other departments do, leading to miscommunication. Adrian wants to introduce a \"Department Swap Day\" where employees experience a different role for a few hours.\n\nDesired outcome:\nEncourage cross-functional understanding through a fun, role-swapping activity.\n\nMy details:\n- Department Swap Day details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":286,"title":"Innovation Pitch Day","category":"Customer Comms","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Create a non-intimidating platform for employees to pitch creative ideas. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Innovation Pitch Day\"\n\nStarting brief:\nYou are a workplace innovation coach. Design a quarterly 'Innovation Pitch Day' for 70 employees. The plan should:\n\nBusiness context:\nRachel, 31, heads the innovation committee at a healthcare start-up in Biopolis, Singapore. She wants employees to feel empowered to share new ideas without fear of rejection. She decides to host a fun \"Pitch Day\" where anyone can present a business improvement idea.\n\nDesired outcome:\nCreate a non-intimidating platform for employees to pitch creative ideas.\n\nMy details:\n- Innovation Pitch Day details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":287,"title":"Fun Friday Game Hour","category":"Productivity","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Boost morale and social connection through regular, casual game sessions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Fun Friday Game Hour\"\n\nStarting brief:\nYou are a team engagement planner. Create a 'Fun Friday' schedule for a company of 40 employees. The plan should:\n\nBusiness context:\nVincent, 25, is the youngest member of HR at a retail company in Orchard, Singapore. He believes ending the week with lighthearted fun can improve morale. He wants to host a recurring \"Fun Friday\" game session.\n\nDesired outcome:\nBoost morale and social connection through regular, casual game sessions.\n\nMy details:\n- Fun Friday Game Hour details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":288,"title":"Pet Day at Work","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Strengthen workplace relationships through a pet-friendly event. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Pet Day at Work\"\n\nStarting brief:\nYou are an event engagement specialist. Create a 'Pet Day' plan for 30 employees. The plan should:\n\nBusiness context:\nNatalie, 28, works in HR for a creative agency in Tanjong Pagar, Singapore. Many employees have pets and often share stories about them. She wants to create a \"Pet Day\" where employees can bring their pets to the office for a bonding experience.\n\nDesired outcome:\nStrengthen workplace relationships through a pet-friendly event.\n\nMy details:\n- Pet Day at Work details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":289,"title":"Office Talent Show","category":"Productivity","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Celebrate employee diversity and creativity through a talent showcase. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Office Talent Show\"\n\nStarting brief:\nYou are a workplace culture events planner. Design an 'Office Talent Show' for 150 employees. The plan should:\n\nBusiness context:\nHafiz, 35, manages HR at a multinational in Raffles Place, Singapore. He wants employees to showcase their hidden talents beyond work skills. He decides on an annual \"Office Talent Show\" that welcomes everything from singing to stand-up comedy.\n\nDesired outcome:\nCelebrate employee diversity and creativity through a talent showcase.\n\nMy details:\n- Office Talent Show details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":290,"title":"Microlearning Challenge","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Enhance skill development through quick, fun, and competitive learning modules. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Microlearning Challenge\"\n\nStarting brief:\nYou are a corporate learning strategist. Create a 4-week 'Microlearning Challenge' for 100 employees. The plan should:\n\nBusiness context:\nIvan, 27, works in L&D for a SaaS company in Paya Lebar, Singapore. Employees are too busy for long training sessions, so he wants to introduce \"Microlearning Challenges\" — short, engaging learning bites.\n\nDesired outcome:\nEnhance skill development through quick, fun, and competitive learning modules.\n\nMy details:\n- Microlearning Challenge details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of employees\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":291,"title":"Cultural Potluck Day","category":"Email & Writing","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Foster cross-departmental bonding, cultural appreciation, and informal conversation through a shared food experience. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Cultural Potluck Day\"\n\nStarting brief:\nYou are a workplace culture designer. Create a detailed plan for a 'Cultural Potluck Day' for 80 employees from Singapore's multicultural mix (Chinese, Malay, Indian, Eurasian, and expats from across Southeast Asia). Your plan must include:\n\nBusiness context:\nSarah, 29, works in HR for an ed-tech startup in the Singapore CBD with employees from diverse backgrounds — Chinese, Malay, Indian, Eurasian, and expats from across Southeast Asia. She notices that despite the diversity, most people eat lunch with their immediate team and rarely interact beyond their department. To encourage cultural exchange, she wants to organize a \"Cultural Potluck Day\" where everyone brings a homemade dish representing their culture or heritage. The aim is not just about food, but also about...\n\nDesired outcome:\nFoster cross-departmental bonding, cultural appreciation, and informal conversation through a shared food experience.\n\nMy details:\n- Cultural Potluck Day details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":292,"title":"Reverse Mentorship Program","category":"Customer Comms","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Encourage knowledge exchange between generations, improve digital literacy among senior leaders, and empower young employees. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Reverse Mentorship Program\"\n\nStarting brief:\nYou are a workplace mentorship architect. Design a 6-month 'Reverse Mentorship Program' for 40 mentor-mentee pairs. Your plan must include:\n\nBusiness context:\nAaron, 34, works at a large IT services firm in Changi Business Park, Singapore. While senior leadership has years of industry knowledge, many are unfamiliar with new tools, Gen Z work culture, or emerging tech trends. Aaron proposes a \"Reverse Mentorship Program\" where younger employees mentor senior leaders on topics like AI tools, social media, or UX design, while also learning leadership skills in return.\n\nDesired outcome:\nEncourage knowledge exchange between generations, improve digital literacy among senior leaders, and empower young employees.\n\nMy details:\n- Reverse Mentorship Program details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of mentor-mentee pairs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":293,"title":"Sustainability Challenge Month","category":"Meetings","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Promote environmental consciousness while fostering healthy competition between teams. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Sustainability Challenge Month\"\n\nStarting brief:\nYou are an environmental workplace engagement planner. Create a 4-week 'Sustainability Challenge' for 120 employees. The plan should:\n\nBusiness context:\nNadia, 26, is part of the employee engagement committee in a Singapore-based e-commerce company headquartered in Tampines. She wants to combine team-building with environmental responsibility. She envisions a \"Sustainability Challenge Month\" where employees earn points for eco-friendly actions — taking the MRT, using reusable bottles, or joining tree-planting drives.\n\nDesired outcome:\nPromote environmental consciousness while fostering healthy competition between teams.\n\nMy details:\n- Sustainability Challenge Month details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of teams\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":294,"title":"Mystery Coffee Chats","category":"Meetings","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Break silos and encourage casual networking across the company. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Mystery Coffee Chats\"\n\nStarting brief:\nYou are a corporate networking facilitator. Design a 12-month 'Mystery Coffee Chats' program for 200 employees. The plan must:\n\nBusiness context:\nRebecca, 28, works in HR for a fintech company in Marina Bay, Singapore. She notices employees tend to network within their own departments, missing opportunities to build wider professional relationships. She wants to introduce \"Mystery Coffee Chats\" where employees are randomly paired to meet over coffee once a month.\n\nDesired outcome:\nBreak silos and encourage casual networking across the company.\n\nMy details:\n- Mystery Coffee Chats details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":295,"title":"‘Pay It Forward’ Week","category":"Customer Comms","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Strengthen trust, empathy, and interpersonal connection in the workplace. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"‘Pay It Forward’ Week\"\n\nStarting brief:\nYou are a workplace culture strategist. Design a 1-week 'Pay It Forward' program for 60 employees. The plan should:\n\nBusiness context:\nMarcus, 33, works in HR for a mid-sized logistics firm in Tuas, Singapore. He wants to introduce a culture of kindness by encouraging small acts of service among employees. His idea: a \"Pay It Forward\" week where each person does something thoughtful for a colleague, and that colleague continues the chain.\n\nDesired outcome:\nStrengthen trust, empathy, and interpersonal connection in the workplace.\n\nMy details:\n- ‘Pay It Forward’ Week details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":296,"title":"Book Club for Professional & Personal Growth","category":"Meetings","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Encourage continuous learning, empathy, and cross-functional discussion through a structured book club. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Book Club for Professional & Personal Growth\"\n\nStarting brief:\nYou are a workplace learning and engagement consultant. Create a quarterly 'Workplace Book Club' program for 50 employees. The plan should:\n\nBusiness context:\nPriya, 27, is in L&D for a consulting firm in Raffles Place, Singapore. She believes reading is a powerful way to grow both personally and professionally. She wants to start a company-wide book club that covers leadership books, fiction for empathy building, and Southeast Asian business case studies.\n\nDesired outcome:\nEncourage continuous learning, empathy, and cross-functional discussion through a structured book club.\n\nMy details:\n- Book Club for Professional & Personal Growth details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of members\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":297,"title":"Themed Dress Up Days","category":"Excel & Data","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Boost employee morale and create lighthearted shared experiences. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Themed Dress Up Days\"\n\nStarting brief:\nYou are a workplace culture creator. Design a 12-month 'Themed Dress-Up Day' calendar for 80 employees. Your plan must:\n\nBusiness context:\nKai, 25, works in HR at a digital marketing firm in Paya Lebar, Singapore. He wants to inject some fun into the workweek by introducing monthly themed dress-up days, such as Retro 90s, Monochrome Monday, or Superhero Day.\n\nDesired outcome:\nBoost employee morale and create lighthearted shared experiences.\n\nMy details:\n- Themed Dress Up Days details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of themes per year\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":298,"title":"DIY Skill Swap Fair","category":"Productivity","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Foster peer learning, creativity, and appreciation of colleagues' talents. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"DIY Skill Swap Fair\"\n\nStarting brief:\nYou are a workplace learning event organizer. Plan a 1-day 'DIY Skill Swap Fair' for 100 employees. The plan should:\n\nBusiness context:\nAmanda, 30, works for a co-working space in one-north, Singapore. She notices employees have unique personal skills — baking, photography, coding shortcuts — but no platform to share them. She wants to host a \"Skill Swap Fair\" where employees teach each other in short, hands-on sessions.\n\nDesired outcome:\nFoster peer learning, creativity, and appreciation of colleagues' talents.\n\nMy details:\n- DIY Skill Swap Fair details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":299,"title":"Well being Passport","category":"Excel & Data","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Intermediate","explanation":"Increase employee participation in wellness initiatives through gamification. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Well being Passport\"\n\nStarting brief:\nYou are a workplace wellness strategist. Design a 6-month 'Well-being Passport' program for 150 employees. The plan should:\n\nBusiness context:\nMei Ling, 31, works in HR for a large retail chain headquartered in Singapore with stores across the island. She wants to encourage employees to take part in wellness activities — from yoga classes to mindfulness workshops — by gamifying the process through a \"Well-being Passport.\n\nDesired outcome:\nIncrease employee participation in wellness initiatives through gamification.\n\nMy details:\n- Well being Passport details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":300,"title":"Annual Gratitude Week","category":"Customer Comms","source":"Admin & Ops","module":"Employee Engagement Ideas","difficulty":"Beginner","explanation":"Build a culture of appreciation, reflection, and positivity at year-end. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Annual Gratitude Week\"\n\nStarting brief:\nYou are a corporate culture consultant. Plan a 5-day 'Gratitude Week' for 200 employees. Your plan should:\n\nBusiness context:\nRyan, 35, leads HR at a mid-sized IT services company based in one-north, Singapore. He wants employees to end the year on a positive note by reflecting on achievements, appreciating colleagues, and recognizing team contributions through a \"Gratitude Week.\n\nDesired outcome:\nBuild a culture of appreciation, reflection, and positivity at year-end.\n\nMy details:\n- Annual Gratitude Week details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":301,"title":"Prompt 1 – KPI Based Annual Performance Review Template","category":"Excel & Data","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a KPI-linked annual review template for startup employees. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 1 – KPI Based Annual Performance Review Template\"\n\nStarting brief:\n\"You are an HR strategist for a fast-growing Singapore fintech startup. Design a KPI-based annual performance review template that captures:\n\nBusiness context:\nRyan, 29, works as an HR manager for a fintech startup based in the CBD, Singapore, with 120 employees. The company has just completed its second financial year and wants to formalise a structured performance review system. Until now, evaluations were ad-hoc, based on manager notes and verbal feedback. Ryan needs a KPI-based review template that aligns individual goals with company OKRs, while also factoring in soft skills and cultural fit. The leadership team wants the process to be fair, data-driven, and...\n\nDesired outcome:\nCreate a KPI-linked annual review template for startup employees.\n\nMy details:\n- Prompt 1 – KPI Based Annual Performance Review Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Department type (Tech\n- Marketing\n- Sales\n- etc.)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":302,"title":"Prompt 2 – 360° Feedback Performance Review Form","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a 360° feedback performance review form. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 2 – 360° Feedback Performance Review Form\"\n\nStarting brief:\n\"You are an organisational development expert. Design a 360° feedback form for a Singapore IT services company that includes:\n\nBusiness context:\nA mid-sized IT services firm headquartered in Changi Business Park, Singapore, with 500 employees, is moving towards a 360° feedback model to encourage a culture of openness and peer learning. Currently, reviews only happen between a manager and employee, which limits perspectives. The HR director wants a feedback form that collects inputs from managers, peers, subordinates, and even cross-functional collaborators. The challenge is to design it in a way that keeps anonymity intact while ensuring the questions are...\n\nDesired outcome:\nCreate a 360° feedback performance review form.\n\nMy details:\n- Prompt 2 – 360° Feedback Performance Review Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role level (Junior, Mid\n- Senior)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":303,"title":"Prompt 3 – Self Reflection Performance Review Template","category":"Research","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Develop a self-reflection template for employee reviews. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Prompt 3 – Self Reflection Performance Review Template\"\n\nStarting brief:\n\"You are an HR content designer for a non-profit organisation. Create a self-reflection performance review template with sections for:\n\nBusiness context:\nA non-profit in Singapore working on environmental awareness campaigns wants to introduce self-reflection in its annual appraisal process. The leadership believes employees should evaluate their own contributions, challenges, and learnings before their manager review. The template should encourage honest introspection while guiding employees to align their personal growth goals with the organisation's mission.\n\nDesired outcome:\nDevelop a self-reflection template for employee reviews.\n\nMy details:\n- Prompt 3 – Self Reflection Performance Review Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Employee role type\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":304,"title":"Prompt 4 – Behavioural Competency Based Review Sheet","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a behavioural competency-based review sheet. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 4 – Behavioural Competency Based Review Sheet\"\n\nStarting brief:\n\"You are an HR analytics consultant. Design a performance review sheet for a Singapore e-commerce firm focusing on behavioural competencies. Include:\n\nBusiness context:\nA leading e-commerce company headquartered in Singapore wants to shift from purely numerical performance scoring to a competency-based model. They want to assess employees on behavioural traits such as adaptability, teamwork, problem-solving, and creativity. The HR analytics team is looking for a review sheet that can rate employees on these competencies with clear behavioural indicators for each rating.\n\nDesired outcome:\nCreate a behavioural competency-based review sheet.\n\nMy details:\n- Prompt 4 – Behavioural Competency Based Review Sheet details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of core competencies\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":305,"title":"Prompt 5 – Probation Period Performance Evaluation Form","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Design a probation period performance review form. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 5 – Probation Period Performance Evaluation Form\"\n\nStarting brief:\n\"You are a talent acquisition and retention expert. Create a probation performance evaluation form for a BPO. Include sections for:\n\nBusiness context:\nA BPO based in Paya Lebar, Singapore, hires hundreds of fresh hires every quarter. Many leave during their probation period due to unclear expectations and lack of structured feedback. The HR team wants to implement a probation review form that evaluates both job performance and cultural fit within the first 90 days. The form should help decide whether to confirm, extend, or terminate the probation.\n\nDesired outcome:\nDesign a probation period performance review form.\n\nMy details:\n- Prompt 5 – Probation Period Performance Evaluation Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Probation duration (in days)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":306,"title":"Prompt 6 – Quarterly Performance Snapshot Template","category":"Excel & Data","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Create a concise but comprehensive quarterly review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 6 – Quarterly Performance Snapshot Template\"\n\nStarting brief:\n\"You are an HR operations designer. Create a quarterly performance snapshot template for a SaaS company. Include:\n\nBusiness context:\nShantini, 31, is the HR lead for a mid-sized SaaS company in one-north, Singapore. The leadership team wants more frequent but lighter performance reviews to keep track of progress without waiting for the annual cycle. They need a quarterly performance snapshot template that balances KPIs, recent achievements, and short-term goal tracking. It should be fast to fill, yet provide meaningful insights for both managers and employees.\n\nDesired outcome:\nCreate a concise but comprehensive quarterly review template.\n\nMy details:\n- Prompt 6 – Quarterly Performance Snapshot Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Department focus\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":307,"title":"Prompt 7 – OKR Linked Performance Review Template","category":"Research","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Design an OKR-linked performance review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Prompt 7 – OKR Linked Performance Review Template\"\n\nStarting brief:\n\"You are an organisational performance consultant. Create a performance review template that maps individual OKRs to company OKRs. Include:\n\nBusiness context:\nAn edtech startup based in Singapore has adopted OKRs (Objectives and Key Results) for strategic alignment. The HR team needs a review template that directly ties employee performance to the company's quarterly and annual OKRs. This ensures everyone's work ladders up to the organisation's mission and helps track contribution impact.\n\nDesired outcome:\nDesign an OKR-linked performance review template.\n\nMy details:\n- Prompt 7 – OKR Linked Performance Review Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company OKRs\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":308,"title":"Prompt 8 – Skill Development Oriented Review Form","category":"Excel & Data","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a skill development-focused review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 8 – Skill Development Oriented Review Form\"\n\nStarting brief:\n\"You are a workforce development strategist. Create a performance review form that evaluates:\n\nBusiness context:\nA precision manufacturing firm based in Tuas, Singapore, is trying to improve workforce skills in automation and quality control. The HR department wants a review form that focuses on assessing skills acquired, training completed, and readiness for advanced roles. The template should be forward-looking rather than only backward-focused.\n\nDesired outcome:\nCreate a skill development-focused review template.\n\nMy details:\n- Prompt 8 – Skill Development Oriented Review Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry skill priorities\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":309,"title":"Prompt 9 – Customer Feedback Integrated Review Sheet","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Design a review sheet that includes customer feedback data. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 9 – Customer Feedback Integrated Review Sheet\"\n\nStarting brief:\n\"You are a customer experience and HR integration specialist. Create a performance review template for retail staff that includes:\n\nBusiness context:\nA retail chain headquartered in Singapore with stores across Orchard, VivoCity and the heartlands has customer-facing staff whose performance is closely tied to customer experience. The HR team wants to integrate customer feedback scores and comments into performance reviews. This will ensure employees see the direct link between their service quality and business impact.\n\nDesired outcome:\nDesign a review sheet that includes customer feedback data.\n\nMy details:\n- Prompt 9 – Customer Feedback Integrated Review Sheet details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Source of customer data (surveys\n- mystery shopping\n- etc.)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":310,"title":"Prompt 10 – Balanced Scorecard Performance Review","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Create a Balanced Scorecard-based review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 10 – Balanced Scorecard Performance Review\"\n\nStarting brief:\n\"You are an HR performance measurement expert. Design a Balanced Scorecard performance review form with four sections:\n\nBusiness context:\nA bank headquartered in Marina Bay, Singapore, is implementing the Balanced Scorecard methodology for performance management. The HR team needs a review form that balances financial metrics, customer service, internal processes, and learning & growth indicators.\n\nDesired outcome:\nCreate a Balanced Scorecard-based review template.\n\nMy details:\n- Prompt 10 – Balanced Scorecard Performance Review details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Department type (Retail Banking\n- Corporate Banking\n- etc.)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":311,"title":"Prompt 11 – Remote Work Performance Review Form","category":"Research","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a remote work-specific performance review form. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Prompt 11 – Remote Work Performance Review Form\"\n\nStarting brief:\n\"You are a remote workforce productivity consultant. Create a performance review form that assesses:\n\nBusiness context:\nPost-pandemic, a digital marketing agency based in Singapore has shifted to hybrid work. The HR team needs a performance review template that evaluates output, communication, self-management, and remote collaboration skills.\n\nDesired outcome:\nCreate a remote work-specific performance review form.\n\nMy details:\n- Prompt 11 – Remote Work Performance Review Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role type (creative\n- technical\n- managerial)\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":312,"title":"Prompt 12 – Project Based Performance Evaluation","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a project completion performance evaluation template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 12 – Project Based Performance Evaluation\"\n\nStarting brief:\n\"You are a project performance analyst. Create an evaluation form for project-based reviews that includes:\n\nBusiness context:\nAn engineering consultancy based in Jurong, Singapore, works on short-term, high-value projects. Instead of annual reviews, they evaluate employees at the end of each project. The HR team wants a project-based evaluation form to capture technical skills, teamwork, and project outcomes.\n\nDesired outcome:\nCreate a project completion performance evaluation template.\n\nMy details:\n- Prompt 12 – Project Based Performance Evaluation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project type (Engineering, IT\n- Design)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":313,"title":"Prompt 13 – Leadership Potential Assessment Template","category":"Research","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Design a performance review to identify future leaders. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Prompt 13 – Leadership Potential Assessment Template\"\n\nStarting brief:\n\"You are a talent management consultant. Create a performance review template that assesses leadership potential by measuring:\n\nBusiness context:\nA healthcare company based in Singapore is looking to identify employees with leadership potential for succession planning. The HR team wants a review template that evaluates leadership skills, decision-making ability, and capacity to inspire teams.\n\nDesired outcome:\nDesign a performance review to identify future leaders.\n\nMy details:\n- Prompt 13 – Leadership Potential Assessment Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role level\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":314,"title":"Prompt 14 – Peer Review Performance Form","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a peer review form for performance evaluation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 14 – Peer Review Performance Form\"\n\nStarting brief:\n\"You are an organisational culture consultant. Design a peer review form that includes:\n\nBusiness context:\nA design agency based in Tiong Bahru, Singapore, has a flat team structure where peer feedback is critical. The HR team wants a peer review template to encourage constructive criticism and collaboration.\n\nDesired outcome:\nCreate a peer review form for performance evaluation.\n\nMy details:\n- Prompt 14 – Peer Review Performance Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role type\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":315,"title":"Prompt 15 – Competency Gap Analysis Review","category":"Excel & Data","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Create a competency gap-focused review form. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 15 – Competency Gap Analysis Review\"\n\nStarting brief:\n\"You are a workforce development expert. Create a performance review form that:\n\nBusiness context:\nA logistics company based in Tuas, Singapore, wants to improve employee training ROI by identifying competency gaps during performance reviews. They need a template that compares required competencies vs current performance levels.\n\nDesired outcome:\nCreate a competency gap-focused review form.\n\nMy details:\n- Prompt 15 – Competency Gap Analysis Review details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role competency framework\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":316,"title":"Prompt 16 – Behavioural Competency Evaluation Form","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Design a review template that measures behavioural competencies alongside technical KPIs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 16 – Behavioural Competency Evaluation Form\"\n\nStarting brief:\n\"You are an organisational psychologist. Create a performance review form that includes:\n\nBusiness context:\nA multinational IT services company headquartered in Singapore (with delivery teams in one-north and Changi Business Park) has strong technical teams but wants to also evaluate employees on behavioural competencies like adaptability, collaboration, and ethical conduct. The HR head believes that these soft skills are as crucial as technical abilities for client satisfaction and long-term retention.\n\nDesired outcome:\nDesign a review template that measures behavioural competencies alongside technical KPIs.\n\nMy details:\n- Prompt 16 – Behavioural Competency Evaluation Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company's competency framework\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":317,"title":"Prompt 17 – 360° Feedback Review Template","category":"Research","source":"Admin & Ops","module":"Performance review templates","difficulty":"Advanced","explanation":"Create a 360° performance review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Prompt 17 – 360° Feedback Review Template\"\n\nStarting brief:\n\"You are an HR strategy consultant. Create a 360° feedback performance review form that includes:\n\nBusiness context:\nA fintech company based in Singapore's CBD wants a full-circle evaluation method involving self-assessment, peer review, manager assessment, and subordinate feedback. They believe 360° feedback offers richer, multi-perspective insights compared to traditional top-down reviews.\n\nDesired outcome:\nCreate a 360° performance review template.\n\nMy details:\n- Prompt 17 – 360° Feedback Review Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role level\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":318,"title":"Prompt 18 – Sales Performance Review Template","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Design a sales-focused performance review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 18 – Sales Performance Review Template\"\n\nStarting brief:\n\"You are a sales performance analyst. Create a performance review form for sales representatives that includes:\n\nBusiness context:\nA consumer goods company headquartered in Singapore (with regional accounts across Southeast Asia) needs a review form tailored for sales teams. The review should track revenue targets, lead conversion, territory performance, and client retention. Motivation and incentive-linked metrics should also be captured.\n\nDesired outcome:\nDesign a sales-focused performance review template.\n\nMy details:\n- Prompt 18 – Sales Performance Review Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales target data\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":319,"title":"Prompt 19 – Creative Role Performance Review","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Create a performance review template for creative roles. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 19 – Creative Role Performance Review\"\n\nStarting brief:\n\"You are a creative industry HR consultant. Design a performance review form for creative professionals that measures:\n\nBusiness context:\nA film and content production house based in Singapore (servicing brands across Southeast Asia) wants to evaluate scriptwriters, editors, and designers based on creativity, originality, and alignment with brand storytelling. They need a review format that captures qualitative aspects alongside deadlines and project impact.\n\nDesired outcome:\nCreate a performance review template for creative roles.\n\nMy details:\n- Prompt 19 – Creative Role Performance Review details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project type (film\n- digital ad\n- etc.)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":320,"title":"Prompt 20 – KPI Weighted Scoring Review Sheet","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Create a KPI-weighted performance review sheet. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 20 – KPI Weighted Scoring Review Sheet\"\n\nStarting brief:\n\"You are a performance metrics designer. Create a review form that:\n\nBusiness context:\nAn IT services firm based in Singapore's one-north precinct uses multiple KPIs, but managers often struggle to weight them consistently. They need a standardised review form with KPI weightages clearly defined to maintain fairness.\n\nDesired outcome:\nCreate a KPI-weighted performance review sheet.\n\nMy details:\n- Prompt 20 – KPI Weighted Scoring Review Sheet details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- KPI list and weights\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":321,"title":"Prompt 21 – High Potential Employee (HiPo) Identification Form","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Design a HiPo-focused performance review form. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 21 – High Potential Employee (HiPo) Identification Form\"\n\nStarting brief:\n\"You are a talent identification specialist. Create a performance review form to assess high-potential employees based on:\n\nBusiness context:\nA pharmaceutical company headquartered in Singapore (with R&D in Tuas Biomedical Park) wants to identify high-potential employees early for leadership programs. They need a review form focused on innovation, initiative, and problem-solving beyond the current role.\n\nDesired outcome:\nDesign a HiPo-focused performance review form.\n\nMy details:\n- Prompt 21 – High Potential Employee (HiPo) Identification Form details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role category\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":322,"title":"Prompt 22 – Employee Self Review Template","category":"Research","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Create a self-review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Prompt 22 – Employee Self Review Template\"\n\nStarting brief:\n\"You are an HR engagement consultant. Create an employee self-review form that includes:\n\nBusiness context:\nA media company based in Singapore (offices in Paya Lebar) wants employees to take ownership of their performance reviews by starting with self-assessments. The goal is to encourage honest self-reflection and alignment with manager observations.\n\nDesired outcome:\nCreate a self-review template.\n\nMy details:\n- Prompt 22 – Employee Self Review Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Role type\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":323,"title":"Prompt 23 – Probation Period Performance Review","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Design a probation review template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 23 – Probation Period Performance Review\"\n\nStarting brief:\n\"You are an HR onboarding specialist. Create a probation performance review form that measures:\n\nBusiness context:\nA hospitality group operating hotels along Sentosa and Marina Bay needs a review form for employees completing their probation period. The form should assess performance, culture fit, and long-term potential before confirmation.\n\nDesired outcome:\nDesign a probation review template.\n\nMy details:\n- Prompt 23 – Probation Period Performance Review details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Probation length\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":324,"title":"Prompt 24 – Underperformance Action Plan Template","category":"Customer Comms","source":"Admin & Ops","module":"Performance review templates","difficulty":"Intermediate","explanation":"Create an underperformance-focused review form. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 24 – Underperformance Action Plan Template\"\n\nStarting brief:\n\"You are a performance improvement coach. Create a review form for underperforming employees that includes:\n\nBusiness context:\nA telecom company headquartered in Singapore wants a review format that identifies underperforming employees and outlines clear, supportive action plans. The goal is to improve performance rather than terminate.\n\nDesired outcome:\nCreate an underperformance-focused review form.\n\nMy details:\n- Prompt 24 – Underperformance Action Plan Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Performance data\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":325,"title":"Prompt 25 – Annual Appraisal Summary Sheet","category":"Excel & Data","source":"Admin & Ops","module":"Performance review templates","difficulty":"Beginner","explanation":"Create an annual appraisal summary template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Prompt 25 – Annual Appraisal Summary Sheet\"\n\nStarting brief:\n\"You are an HR documentation expert. Create a consolidated annual appraisal summary sheet that includes:\n\nBusiness context:\nA Singapore-headquartered conglomerate conducts annual appraisals across multiple business units spanning Southeast Asia. They need a summary sheet for HR to compile individual ratings, comments, and salary increment recommendations in one place.\n\nDesired outcome:\nCreate an annual appraisal summary template.\n\nMy details:\n- Prompt 25 – Annual Appraisal Summary Sheet details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Appraisal rating scale\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":326,"title":"Daily Stand up Protocol for Remote Teams","category":"Meetings","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Create a standardized remote daily stand-up SOP that improves communication, accountability, and alignment across time zones. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Daily Stand up Protocol for Remote Teams\"\n\nStarting brief:\nYou are a remote team operations expert. Design a daily stand-up SOP for a 10-member remote marketing team working across Singapore, Sydney, and London. Your SOP should include:\n\nBusiness context:\nRachel Tan, 29, is a project manager at a digital marketing agency based in Singapore's CBD. Her remote team spans three time zones — Singapore, Sydney, and London. While the team uses Slack and Trello, updates are inconsistent, causing delays and miscommunication. She wants an SOP for a 15-minute daily stand-up that ensures everyone shares progress, blockers, and priorities in a structured way, without eating into work time.\n\nDesired outcome:\nCreate a standardized remote daily stand-up SOP that improves communication, accountability, and alignment across time zones.\n\nMy details:\n- Daily Stand up Protocol for Remote Teams details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size and roles\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":327,"title":"Remote Onboarding SOP","category":"Email & Writing","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Develop a detailed remote onboarding SOP that ensures smooth integration of new hires into the company's culture and workflow. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Remote Onboarding SOP\"\n\nStarting brief:\nYou are a remote work HR consultant. Create a remote onboarding SOP for a fintech company with 50% international hires. Your SOP should include:\n\nBusiness context:\nDaniel Lim, 26, works in HR for a Singapore-based fintech company that has gone fully remote. He finds that new hires often feel lost during their first week because there's no clear onboarding process tailored for remote employees. They miss introductions, fail to set up tools properly, and take longer to get productive. Daniel wants an SOP that standardizes remote onboarding so every new hire feels welcome and confident from day one.\n\nDesired outcome:\nDevelop a detailed remote onboarding SOP that ensures smooth integration of new hires into the company's culture and workflow.\n\nMy details:\n- Remote Onboarding SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company size\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":328,"title":"Communication Cadence SOP","category":"Meetings","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Beginner","explanation":"Create a communication cadence SOP that balances efficiency, clarity, and team connectivity for remote workers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Communication Cadence SOP\"\n\nStarting brief:\nYou are a remote communication strategist. Design a communication cadence SOP for a 15-person product team. The SOP must:\n\nBusiness context:\nAminah Rahman, 32, leads a product team working remotely with members in Singapore, Penang, and Jakarta. She's struggling with overcommunication (too many messages) and undercommunication (missed updates). She wants an SOP that sets a predictable communication cadence so the team knows exactly when and how to share updates without micromanagement.\n\nDesired outcome:\nCreate a communication cadence SOP that balances efficiency, clarity, and team connectivity for remote workers.\n\nMy details:\n- Communication Cadence SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":329,"title":"Performance Review SOP for Remote Teams","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Standardize the performance review process for remote teams, making it transparent, supportive, and data-driven. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Performance Review SOP for Remote Teams\"\n\nStarting brief:\nYou are a remote HR policy writer. Create a performance review SOP for a 12-member remote software team. Include:\n\nBusiness context:\nVincent Goh, 35, manages a fully remote development team distributed across Singapore and Southeast Asia. He finds performance reviews difficult because there's no in-person rapport and tracking individual contributions is tricky. He wants an SOP that ensures fair, transparent, and growth-oriented reviews without creating anxiety among team members.\n\nDesired outcome:\nStandardize the performance review process for remote teams, making it transparent, supportive, and data-driven.\n\nMy details:\n- Performance Review SOP for Remote Teams details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":330,"title":"Conflict Resolution SOP for Remote Teams","category":"Meetings","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Create a conflict resolution SOP specifically for remote and hybrid teams to maintain trust and team cohesion. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Conflict Resolution SOP for Remote Teams\"\n\nStarting brief:\nYou are a workplace conflict management specialist. Write a conflict resolution SOP for a hybrid marketing team of 20 members. Include:\n\nBusiness context:\nMichelle Lee, 30, manages a hybrid marketing team where half the staff work remotely from various neighbourhoods around Singapore (Tampines, Jurong, Woodlands) and a couple of regional members in Kuala Lumpur and Bangkok. She notices conflicts often get escalated because tone is misinterpreted over text, and there's no standard way to resolve disagreements. She needs an SOP that helps managers identify, address, and resolve remote team conflicts quickly and respectfully.\n\nDesired outcome:\nCreate a conflict resolution SOP specifically for remote and hybrid teams to maintain trust and team cohesion.\n\nMy details:\n- Conflict Resolution SOP for Remote Teams details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":331,"title":"Task Handoff SOP for Multi Time Zone Teams","category":"Email & Writing","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Develop a task handoff SOP that ensures no work stalls due to unclear communication across time zones. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Task Handoff SOP for Multi Time Zone Teams\"\n\nStarting brief:\nYou are a remote workflow consultant. Create a task handoff SOP for a SaaS development team across three time zones. The SOP must include:\n\nBusiness context:\nPriya Kumar, 28, works as a project lead at a SaaS company headquartered in Singapore where developers are spread across Singapore, Warsaw, and Toronto. Because of the time differences, handoffs often get delayed or incomplete, which causes bottlenecks. She needs an SOP that makes sure task handoffs are seamless, fully documented, and ready for the next person to pick up without confusion.\n\nDesired outcome:\nDevelop a task handoff SOP that ensures no work stalls due to unclear communication across time zones.\n\nMy details:\n- Task Handoff SOP for Multi Time Zone Teams details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of time zones involved\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":332,"title":"Remote Security & Data Access SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Create a security and data access SOP that ensures safe handling of sensitive files while maintaining productivity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Security & Data Access SOP\"\n\nStarting brief:\nYou are a cybersecurity policy writer. Draft a remote security SOP for a distributed finance team. The SOP must:\n\nBusiness context:\nMarcus Ng, 31, manages a distributed finance team handling sensitive client data. Employees work remotely from various parts of Singapore as well as a couple of regional offices in Southeast Asia, and he's concerned about security breaches and unauthorized file sharing. He needs an SOP that balances easy access for authorized team members with strong security measures to protect confidential data, in line with PDPA and MAS guidelines.\n\nDesired outcome:\nCreate a security and data access SOP that ensures safe handling of sensitive files while maintaining productivity.\n\nMy details:\n- Remote Security & Data Access SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of data handled\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":333,"title":"Remote Brainstorming Session SOP","category":"Meetings","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Design a remote brainstorming SOP that encourages participation, creativity, and actionable outcomes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Remote Brainstorming Session SOP\"\n\nStarting brief:\nYou are a creative facilitation expert. Write a remote brainstorming SOP for a 10-person creative team. Include:\n\nBusiness context:\nAisha Ismail, 27, leads the creative team of an ad agency based in Singapore. Since going remote, brainstorming sessions feel dull, with only a few people speaking while others remain passive. She needs an SOP that turns remote brainstorming into a dynamic, idea-rich, and collaborative process.\n\nDesired outcome:\nDesign a remote brainstorming SOP that encourages participation, creativity, and actionable outcomes.\n\nMy details:\n- Remote Brainstorming Session SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":334,"title":"Async Project Update SOP","category":"Email & Writing","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Beginner","explanation":"Create an asynchronous update SOP to replace unnecessary live meetings and keep projects moving smoothly. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Async Project Update SOP\"\n\nStarting brief:\nYou are a remote productivity expert. Create an async update SOP for a product design team. Include:\n\nBusiness context:\nMarcus Tan, 30, manages a hybrid product design team based in Singapore that struggles with scheduling live meetings due to different work hours across the region. He wants an SOP that ensures asynchronous project updates are clear, timely, and tracked, so no one is left out of the loop.\n\nDesired outcome:\nCreate an asynchronous update SOP to replace unnecessary live meetings and keep projects moving smoothly.\n\nMy details:\n- Async Project Update SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project type\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":335,"title":"Remote Cultural Integration SOP for New Hires","category":"Email & Writing","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Create a cultural integration SOP that helps remote employees feel like part of the team quickly. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Remote Cultural Integration SOP for New Hires\"\n\nStarting brief:\nYou are an organizational culture consultant. Design a cultural integration SOP for a fully remote startup. Include:\n\nBusiness context:\nPriya Kumar, 33, leads HR for a growing Singapore-based startup. While technical onboarding is smooth, new hires often take months to feel connected to the company culture, especially when working remotely. She wants an SOP that speeds up cultural integration through deliberate remote activities.\n\nDesired outcome:\nCreate a cultural integration SOP that helps remote employees feel like part of the team quickly.\n\nMy details:\n- Remote Cultural Integration SOP for New Hires details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company values\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":336,"title":"Remote Leave Management SOP","category":"Research","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Build a leave management SOP that ensures fair, clear, and timely leave planning for remote teams. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a research analyst who compares sources, extracts insight, and flags uncertainty. Help me create a polished, workplace-ready output for this task:\n\"Remote Leave Management SOP\"\n\nStarting brief:\nYou are an HR process designer. Draft a leave management SOP for a remote content team. Include:\n\nBusiness context:\nAdrian Lim, 29, runs a content marketing team in Singapore where members take leave without enough notice, causing delivery delays. He needs a transparent SOP so all leave requests and approvals are tracked and visible without micromanaging.\n\nDesired outcome:\nBuild a leave management SOP that ensures fair, clear, and timely leave planning for remote teams.\n\nMy details:\n- Remote Leave Management SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- research question\n- scope\n- source list or search access\n- geography or market\n- decision to support\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Break the research question into sub-questions before answering.\n2. Use provided sources first; if web access is available, prefer current primary or reputable sources.\n3. Compare alternatives in a table and identify evidence strength.\n4. Separate facts, interpretations, and open questions.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Executive summary\n- Comparison or findings table\n- Evidence notes with source names or source placeholders\n- Implications for our team\n- Open questions and recommended next steps\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- If you cannot verify a claim from the provided material, label it as unverified instead of presenting it as fact.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🔍","color":"cat-purple"},{"id":337,"title":"Remote Mentorship Program SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Create a mentorship program SOP for remote employees to foster skill growth and engagement. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Mentorship Program SOP\"\n\nStarting brief:\nYou are an employee development strategist. Write a mentorship program SOP for a 100-member remote tech company. Include:\n\nBusiness context:\nSarah Ng, 26, is an L&D coordinator for a Singapore tech company. She wants to launch a mentorship program for remote employees to support career growth and skill development. Without in-person interaction, she needs a structured SOP to make mentorship engaging and impactful.\n\nDesired outcome:\nCreate a mentorship program SOP for remote employees to foster skill growth and engagement.\n\nMy details:\n- Remote Mentorship Program SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":338,"title":"Remote Work Wellness SOP","category":"Email & Writing","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Beginner","explanation":"Create a wellness SOP for remote employees that promotes mental and physical health. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Remote Work Wellness SOP\"\n\nStarting brief:\nYou are a workplace wellness consultant. Draft a wellness SOP for remote teams. Include:\n\nBusiness context:\nVincent Wong, 34, is a department head at a Singapore firm who notices remote employees facing burnout from long screen hours. He wants an SOP that encourages wellness habits without feeling forced.\n\nDesired outcome:\nCreate a wellness SOP for remote employees that promotes mental and physical health.\n\nMy details:\n- Remote Work Wellness SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":339,"title":"Virtual Performance Incentive SOP","category":"Excel & Data","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Beginner","explanation":"Design an incentive SOP that motivates remote employees without causing resentment. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Virtual Performance Incentive SOP\"\n\nStarting brief:\nYou are a sales performance consultant. Create an incentive SOP for a remote sales team. Include:\n\nBusiness context:\nDaniel Goh, 32, leads a sales team headquartered in Singapore with members across Southeast Asia. He wants a fair SOP for rewarding top performers remotely, with transparent criteria and easy disbursement.\n\nDesired outcome:\nDesign an incentive SOP that motivates remote employees without causing resentment.\n\nMy details:\n- Virtual Performance Incentive SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":340,"title":"Remote Crisis Management SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Create a crisis management SOP for remote teams to handle emergencies smoothly. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Crisis Management SOP\"\n\nStarting brief:\nYou are a business continuity expert. Draft a crisis management SOP for a remote support team. Include:\n\nBusiness context:\nNadia Rahman, 30, manages customer support for a Singapore-based ed-tech platform. When a sudden platform outage happened, her remote team scrambled without a clear plan. She needs an SOP that outlines exactly what to do during crises.\n\nDesired outcome:\nCreate a crisis management SOP for remote teams to handle emergencies smoothly.\n\nMy details:\n- Remote Crisis Management SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of crises expected\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":341,"title":"Remote Client Handoff SOP for Multi Department Projects","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Create a remote client handoff SOP that ensures a smooth, fully documented, and accountable transfer of work between departments without any information gaps. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Client Handoff SOP for Multi Department Projects\"\n\nStarting brief:\nYou are a remote operations process expert. Develop a Client Handoff SOP for multi-department remote projects that ensures continuity, zero data loss, and accountability. The SOP must include:\n\nBusiness context:\nRachel Teo, 33, works as an account manager in a mid-sized digital agency headquartered in Singapore with remote teams spread across Singapore, Kuala Lumpur, and Sydney. Her projects involve multiple departments — design, development, content, and client servicing — all working in different time zones and schedules. Whenever a client project moves from one department to another, essential information is often missed, resulting in client dissatisfaction and scope creep. Rachel wants a clear, replicable SOP that...\n\nDesired outcome:\nCreate a remote client handoff SOP that ensures a smooth, fully documented, and accountable transfer of work between departments without any information gaps.\n\nMy details:\n- Remote Client Handoff SOP for Multi Department Projects details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of departments involved\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":342,"title":"Remote Knowledge Base Maintenance SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Develop a knowledge base maintenance SOP that ensures every document is reviewed, updated, and tagged regularly so remote teams can find accurate information quickly. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Knowledge Base Maintenance SOP\"\n\nStarting brief:\nYou are a documentation workflow consultant. Write a Knowledge Base Maintenance SOP for a remote SaaS support team. This SOP must include:\n\nBusiness context:\nKevin Chen, 29, manages a fully remote software support team at a Singapore-based enterprise SaaS company. The team maintains a knowledge base (KB) used by both employees and customers, but updates are inconsistent. Some articles are outdated, others are duplicated, and certain crucial troubleshooting guides are buried deep in folders. Because of this, employees waste time searching for the right answer, and customers get conflicting information. Kevin needs a structured SOP to keep the KB accurate, searchable,...\n\nDesired outcome:\nDevelop a knowledge base maintenance SOP that ensures every document is reviewed, updated, and tagged regularly so remote teams can find accurate information quickly.\n\nMy details:\n- Remote Knowledge Base Maintenance SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Size of knowledge base (number of articles)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":343,"title":"Remote Performance Review SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Create a remote performance review SOP that standardizes evaluations across the company, promotes growth, and documents progress effectively. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Performance Review SOP\"\n\nStarting brief:\nYou are an HR policy specialist. Create a Performance Review SOP for a remote IT company. The SOP must detail:\n\nBusiness context:\nNatalie Lee, 31, is the HR manager for a 120-person Singapore IT company that went fully remote after the pandemic. While quarterly performance reviews are scheduled, the process is inconsistent across teams. Some managers conduct detailed evaluations, while others send vague feedback emails. Employees feel demotivated and unclear about their growth path. Natalie wants a unified, transparent performance review SOP tailored for remote teams, with guidelines for collecting peer feedback, reviewing goals, and...\n\nDesired outcome:\nCreate a remote performance review SOP that standardizes evaluations across the company, promotes growth, and documents progress effectively.\n\nMy details:\n- Remote Performance Review SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Review frequency (quarterly/half-yearly)\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":344,"title":"Remote Onboarding SOP for High Volume Hiring","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Develop a high-volume remote onboarding SOP that delivers a consistent experience, reduces manager workload, and accelerates new hire productivity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Onboarding SOP for High Volume Hiring\"\n\nStarting brief:\nYou are an employee experience designer. Draft a High-Volume Remote Onboarding SOP for a fast-growing company. The SOP must include:\n\nBusiness context:\nSamuel Ong, 28, runs talent acquisition for a rapidly scaling Singapore-based ed-tech company. They hire 20–30 new employees per month across sales, operations, and tech roles. Since the team is fully remote, onboarding is done via Zoom calls and shared Google Docs, but the process is chaotic. New hires don't know where to start, and managers are overwhelmed with repetitive questions. Samuel needs a detailed onboarding SOP that scales for high-volume remote hiring while ensuring every new employee feels welcomed,...\n\nDesired outcome:\nDevelop a high-volume remote onboarding SOP that delivers a consistent experience, reduces manager workload, and accelerates new hire productivity.\n\nMy details:\n- Remote Onboarding SOP for High Volume Hiring details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of hires per month\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":345,"title":"Remote Meeting Recording & Archiving SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Beginner","explanation":"Create a remote meeting recording and archiving SOP that ensures secure, searchable, and easy-to-access meeting history. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Meeting Recording & Archiving SOP\"\n\nStarting brief:\nYou are a remote knowledge management specialist. Create a Meeting Recording & Archiving SOP for a consultancy handling multiple daily client calls. The SOP must specify:\n\nBusiness context:\nAnand Suresh, 35, leads operations for a Singapore consultancy that conducts multiple remote client calls daily. Often, key decisions made in meetings are forgotten or misremembered, leading to disputes. While they record meetings, the storage is disorganized and retrieval is difficult. Anand needs a proper SOP that ensures every meeting is recorded, summarized, tagged, and stored in a way that makes it easy to retrieve at any point in the future.\n\nDesired outcome:\nCreate a remote meeting recording and archiving SOP that ensures secure, searchable, and easy-to-access meeting history.\n\nMy details:\n- Remote Meeting Recording & Archiving SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of meetings per day\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":346,"title":"Remote Escalation & Crisis Management SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Create a remote escalation and crisis management SOP that eliminates ambiguity, reduces downtime, and ensures swift coordinated action during emergencies. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Escalation & Crisis Management SOP\"\n\nStarting brief:\nYou are a remote operations strategist. Draft a Crisis Management & Escalation SOP for a distributed marketing agency. This SOP must include:\n\nBusiness context:\nPriya Devi, 34, is the project director of a marketing agency with remote teams across Singapore, Kuala Lumpur, and Jakarta. Recently, a high-profile client campaign almost failed because a critical issue was not escalated on time — team members assumed someone else was handling it. This caused last-minute chaos, unnecessary overtime, and strained client relations. Priya wants a crystal-clear SOP that defines exactly when and how to escalate an issue in a remote setting, who to contact, and how to document actions...\n\nDesired outcome:\nCreate a remote escalation and crisis management SOP that eliminates ambiguity, reduces downtime, and ensures swift coordinated action during emergencies.\n\nMy details:\n- Remote Escalation & Crisis Management SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size & structure\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":347,"title":"Remote Time Zone Coordination SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Create a time zone coordination SOP that standardizes meeting scheduling, deadline setting, and asynchronous communication for global remote teams. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Time Zone Coordination SOP\"\n\nStarting brief:\nYou are a global remote workflow consultant. Write a Time Zone Coordination SOP for a SaaS team. Include:\n\nBusiness context:\nAaron Koh, 30, manages a SaaS development team headquartered in Singapore with members in Germany and Canada. Coordinating meetings and deadlines across time zones is a constant headache — some members are forced into late-night calls, and others miss updates entirely. Deadlines are often misunderstood due to different local times. Aaron needs a repeatable SOP to ensure smooth time zone management, minimizing burnout and missed communication.\n\nDesired outcome:\nCreate a time zone coordination SOP that standardizes meeting scheduling, deadline setting, and asynchronous communication for global remote teams.\n\nMy details:\n- Remote Time Zone Coordination SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team locations and time zones\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":348,"title":"Remote Task Handover for Leave & Absence SOP","category":"Email & Writing","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Design a remote task handover SOP that covers both planned and unplanned absences, ensuring work continuity and accountability. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a business writer who makes workplace messages clear, concise, and easy to act on. Help me create a polished, workplace-ready output for this task:\n\"Remote Task Handover for Leave & Absence SOP\"\n\nStarting brief:\nYou are a workflow process designer. Create a Remote Task Handover SOP for a distributed editorial team. Include:\n\nBusiness context:\nMei Ling Ho, 32, is a senior content strategist working with a remote editorial team based in Singapore. Every time someone goes on vacation or medical leave, their ongoing work is left in limbo, causing delays and confusion. Mei Ling wants an SOP that ensures smooth task handovers before any planned absence and a clear plan for unplanned absences, so deadlines are met without overloading other team members.\n\nDesired outcome:\nDesign a remote task handover SOP that covers both planned and unplanned absences, ensuring work continuity and accountability.\n\nMy details:\n- Remote Task Handover for Leave & Absence SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- audience\n- purpose\n- key points\n- desired tone\n- length or format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Identify the audience, goal, and action the reader should take.\n2. Organize content with the most important point first.\n3. Write in simple language, remove filler, and preserve necessary detail.\n4. Offer two tone options when the audience or situation may require sensitivity.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Polished draft\n- Subject line or title options where relevant\n- Shorter version\n- Review checklist\n- Suggested follow-up line\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Keep claims factual, avoid jargon, and mark any missing names, dates, numbers, or approvals as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"✍️","color":"cat-coral"},{"id":349,"title":"Remote Feedback Loop SOP for Continuous Improvement","category":"Excel & Data","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Intermediate","explanation":"Establish a structured feedback loop SOP that ensures continuous improvement in processes, products, and team communication. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a data analyst who turns messy workplace data into clear business insight. Help me create a polished, workplace-ready output for this task:\n\"Remote Feedback Loop SOP for Continuous Improvement\"\n\nStarting brief:\nYou are an agile process consultant. Draft a Remote Feedback Loop SOP for a hybrid engineering team. Include:\n\nBusiness context:\nVictor Lim, 29, is a product lead managing a hybrid engineering team at a Singapore tech firm. While feedback is encouraged, most suggestions get lost in chat threads or buried in emails. Team members feel unheard, and the same mistakes repeat across sprints. Victor wants an SOP to formalize a feedback loop system so that every suggestion, bug report, and improvement idea is logged, reviewed, prioritized, and acted upon — even in a fully remote setup.\n\nDesired outcome:\nEstablish a structured feedback loop SOP that ensures continuous improvement in processes, products, and team communication.\n\nMy details:\n- Remote Feedback Loop SOP for Continuous Improvement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team's workflow methodology (Agile/Scrum/Kanban)\n- data columns\n- sample rows or file summary\n- business question\n- known data quality issues\n- preferred output table or chart\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Restate the business question and identify the required data fields.\n2. List cleaning checks before analysis, including duplicates, missing values, outliers, and inconsistent formats.\n3. Recommend formulas, pivots, charts, or SQL-style logic only when they fit the data described.\n4. Separate findings from assumptions and call out what must be verified against the source file.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Data-readiness checklist\n- Step-by-step analysis method\n- Formula, pivot, or calculation suggestions\n- Insight summary in plain English\n- Validation checks and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not fabricate numbers. If data is missing, provide the analysis structure and mark where values must be inserted.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📊","color":"cat-green"},{"id":350,"title":"Remote Security & Data Protection SOP","category":"Customer Comms","source":"Admin & Ops","module":"Remote Team Management SOPs","difficulty":"Advanced","explanation":"Develop a security and data protection SOP for a remote fintech team that prevents breaches, ensures compliance, and promotes safe work habits. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Remote Security & Data Protection SOP\"\n\nStarting brief:\nYou are a cybersecurity policy expert. Write a Remote Security & Data Protection SOP for a fintech startup. Include:\n\nBusiness context:\nRonald Tan, 35, is CTO of a fintech startup in Singapore working entirely remotely. Given the sensitive nature of financial data, they face strict compliance requirements under MAS Technology Risk Management guidelines, Singapore's PDPA, and GDPR for overseas clients. Team members work from personal laptops, cafes, and co-working spaces — increasing the risk of security breaches. Ronald needs a robust SOP that ensures maximum data protection while enabling productivity.\n\nDesired outcome:\nDevelop a security and data protection SOP for a remote fintech team that prevents breaches, ensures compliance, and promotes safe work habits.\n\nMy details:\n- Remote Security & Data Protection SOP details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Compliance frameworks applicable\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":351,"title":"Prompt 1 – Weekly Team Sync Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Create a weekly team sync agenda template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 1 – Weekly Team Sync Agenda\"\n\nStarting brief:\n\"You are a productivity consultant. Create a weekly team sync meeting agenda with the following sections:\n\nBusiness context:\nA digital marketing agency in Singapore's CBD has a fast-paced work environment where priorities shift weekly. The team lead wants a recurring Monday morning meeting to align on key campaigns, deadlines, and blockers. She needs a structured agenda to keep discussions focused and under 30 minutes.\n\nDesired outcome:\nCreate a weekly team sync agenda template.\n\nMy details:\n- Prompt 1 – Weekly Team Sync Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":352,"title":"Prompt 2 – Monthly Project Review Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Beginner","explanation":"Design a monthly project review agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 2 – Monthly Project Review Agenda\"\n\nStarting brief:\n\"You are a project management expert. Draft a monthly project review agenda covering:\n\nBusiness context:\nAn e-learning platform headquartered in Singapore runs multiple projects in parallel. Project managers want a monthly review with the entire product team to check progress, identify resource gaps, and recalibrate timelines.\n\nDesired outcome:\nDesign a monthly project review agenda.\n\nMy details:\n- Prompt 2 – Monthly Project Review Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of projects under review\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":353,"title":"Prompt 3 – Quarterly Strategy Alignment Meeting","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Create a quarterly strategy alignment agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 3 – Quarterly Strategy Alignment Meeting\"\n\nStarting brief:\n\"You are a business strategy facilitator. Create a quarterly strategy meeting agenda that includes:\n\nBusiness context:\nA renewable energy startup based in Singapore's one-north precinct wants leadership and team members aligned every quarter on big-picture goals. The founder believes quarterly strategic recalibration keeps everyone motivated and ensures resources are allocated to the most impactful work.\n\nDesired outcome:\nCreate a quarterly strategy alignment agenda.\n\nMy details:\n- Prompt 3 – Quarterly Strategy Alignment Meeting details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Strategic priorities\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":354,"title":"Prompt 4 – Daily Standup Agenda (Agile/Scrum)","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Design a daily standup meeting agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 4 – Daily Standup Agenda (Agile/Scrum)\"\n\nStarting brief:\n\"You are an Agile coach. Create a daily standup agenda that includes:\n\nBusiness context:\nA software development team based in Singapore's Paya Lebar tech cluster follows Agile methodology. They hold daily 15-minute standups to report on progress, plan for the day, and surface blockers. The Scrum Master wants a standardised agenda to keep the standups sharp and on-track.\n\nDesired outcome:\nDesign a daily standup meeting agenda.\n\nMy details:\n- Prompt 4 – Daily Standup Agenda (Agile/Scrum) details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":355,"title":"Prompt 5 – Brainstorming Session Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Beginner","explanation":"Create a brainstorming session agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 5 – Brainstorming Session Agenda\"\n\nStarting brief:\n\"You are a creative facilitator. Draft a brainstorming meeting agenda that includes:\n\nBusiness context:\nAn ad agency in Singapore's Orchard area needs a structure for creative brainstorming meetings. Without an agenda, discussions become chaotic, and many ideas get lost. The Creative Director wants a format that encourages free-flowing ideas but also documents them for action.\n\nDesired outcome:\nCreate a brainstorming session agenda.\n\nMy details:\n- Prompt 5 – Brainstorming Session Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Topic or challenge\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":356,"title":"Prompt 6 – All Hands Company Meeting Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Beginner","explanation":"Design an all-hands meeting agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 6 – All Hands Company Meeting Agenda\"\n\nStarting brief:\n\"You are an internal communications strategist. Create a monthly all-hands agenda that includes:\n\nBusiness context:\nA fast-growing healthtech startup based in Singapore's Biopolis precinct wants to hold monthly all-hands meetings to keep employees informed and engaged. These sessions should cover company performance, departmental highlights, and employee recognition.\n\nDesired outcome:\nDesign an all-hands meeting agenda.\n\nMy details:\n- Prompt 6 – All Hands Company Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":357,"title":"Prompt 7 – Cross Functional Collaboration Meeting","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Create a cross-functional meeting agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 7 – Cross Functional Collaboration Meeting\"\n\nStarting brief:\n\"You are a workflow efficiency expert. Draft an agenda for a cross-functional meeting covering:\n\nBusiness context:\nA fashion e-commerce brand headquartered in Singapore often struggles with coordination between design, marketing, and supply chain teams. The COO wants a recurring meeting to ensure smoother collaboration and timely campaign launches.\n\nDesired outcome:\nCreate a cross-functional meeting agenda.\n\nMy details:\n- Prompt 7 – Cross Functional Collaboration Meeting details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Departments involved\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":358,"title":"Prompt 8 – Client Project Kickoff Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Design a client project kickoff agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 8 – Client Project Kickoff Agenda\"\n\nStarting brief:\n\"You are a client success manager. Create a kickoff meeting agenda that includes:\n\nBusiness context:\nA PR agency in Singapore's Tanjong Pagar district wants a structured kickoff agenda for new client projects to ensure smooth onboarding. This agenda should cover introductions, scope, timelines, and communication protocols.\n\nDesired outcome:\nDesign a client project kickoff agenda.\n\nMy details:\n- Prompt 8 – Client Project Kickoff Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client industry\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":359,"title":"Prompt 9 – Remote Team Catch Up Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Create a remote team catch-up agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 9 – Remote Team Catch Up Agenda\"\n\nStarting brief:\n\"You are a remote work consultant. Draft a remote team catch-up agenda with:\n\nBusiness context:\nA content writing team spread across Singapore and the wider Southeast Asia region meets virtually every Friday to maintain connection and share progress. Without a set agenda, these calls drift into unrelated topics. The manager wants a lightweight but structured approach.\n\nDesired outcome:\nCreate a remote team catch-up agenda.\n\nMy details:\n- Prompt 9 – Remote Team Catch Up Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":360,"title":"Prompt 10 – Performance Review Prep Meeting","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Design a performance review prep agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 10 – Performance Review Prep Meeting\"\n\nStarting brief:\n\"You are an HR operations specialist. Create a meeting agenda for pre-performance review alignment that includes:\n\nBusiness context:\nA business process outsourcing company in Singapore's Changi Business Park wants a short pre-appraisal meeting agenda between managers and team leads to align on evaluation criteria before formal reviews. This ensures consistency in scoring and feedback delivery.\n\nDesired outcome:\nDesign a performance review prep agenda.\n\nMy details:\n- Prompt 10 – Performance Review Prep Meeting details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Performance review form\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":361,"title":"Prompt 11 – Product Launch Planning Meeting Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Design a structured agenda for a product launch planning meeting that ensures complete clarity on objectives, responsibilities, deadlines, and risk mitigation strategies. Success means all stakeholders leave the meeting knowing their exact roles,...","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 11 – Product Launch Planning Meeting Agenda\"\n\nStarting brief:\n\"You are a product launch strategist. Create a comprehensive agenda for a cross-functional product launch planning meeting, covering:\n\nBusiness context:\nA mid-sized electronics company headquartered in Singapore is preparing to launch a new smart home device across Singapore and selected Southeast Asian markets within 90 days. The cross-functional launch team includes members from product development, marketing, supply chain, and customer service. In the past, product launches have been delayed due to unclear responsibilities and last-minute coordination issues. The VP of Product wants a detailed kickoff meeting to set the tone, align deliverables, and ensure all...\n\nDesired outcome:\nDesign a structured agenda for a product launch planning meeting that ensures complete clarity on objectives, responsibilities, deadlines, and risk mitigation strategies. Success means all stakeholders leave the meeting knowing their exact roles, timelines, and communication protocols, with no ambiguity.\n\nMy details:\n- Prompt 11 – Product Launch Planning Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Launch date\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":362,"title":"Prompt 12 – Crisis Response Coordination Meeting Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Create a time-bound agenda that allows the team to assess the crisis, take immediate action, and prepare public communication without losing focus. The outcome should be a clear response plan that protects brand reputation and customer trust. Copy-ready...","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 12 – Crisis Response Coordination Meeting Agenda\"\n\nStarting brief:\n\"You are a corporate crisis management consultant. Design a crisis coordination meeting agenda with:\n\nBusiness context:\nA popular food delivery startup in Singapore faced a PR crisis when a video showing poor hygiene at one of its partner kitchens went viral. The leadership team needs to convene urgently with PR, operations, legal, and customer service to address the situation. Past crisis meetings have been chaotic, with overlapping conversations and no clear resolution path. The COO wants a hyper-structured agenda that balances speed with thoroughness.\n\nDesired outcome:\nCreate a time-bound agenda that allows the team to assess the crisis, take immediate action, and prepare public communication without losing focus. The outcome should be a clear response plan that protects brand reputation and customer trust.\n\nMy details:\n- Prompt 12 – Crisis Response Coordination Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Nature and severity of crisis\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":363,"title":"Prompt 13 – Innovation Lab Quarterly Update Meeting Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Develop a presentation-focused meeting agenda that ensures innovation updates are aligned with company goals and help leadership decide which projects to scale, pivot, or discontinue. Copy-ready prompt with placeholders, task steps, output format, and...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 13 – Innovation Lab Quarterly Update Meeting Agenda\"\n\nStarting brief:\n\"You are an innovation program facilitator. Draft a quarterly update agenda for an innovation lab, with the following structure:\n\nBusiness context:\nA Singapore-based fintech company runs an \"Innovation Lab\" where employees experiment with new payment solutions. Every quarter, the lab team presents prototypes, test results, and learnings to senior leadership. In previous updates, presentations have gone off-track, focusing too much on tech details and too little on business impact. The Head of Innovation wants an agenda that keeps the focus on strategic outcomes, scalability, and ROI.\n\nDesired outcome:\nDevelop a presentation-focused meeting agenda that ensures innovation updates are aligned with company goals and help leadership decide which projects to scale, pivot, or discontinue.\n\nMy details:\n- Prompt 13 – Innovation Lab Quarterly Update Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of projects to present\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":364,"title":"Prompt 14 – Remote Team Weekly Sync Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Beginner","explanation":"Create a balanced remote weekly sync agenda that ensures alignment on key priorities, quick resolution of blockers, and some time for team culture building. The outcome should be a shared understanding of priorities and deadlines for the week. Copy-ready...","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 14 – Remote Team Weekly Sync Agenda\"\n\nStarting brief:\n\"You are a remote work facilitator. Design a 45–60 minute remote weekly sync agenda for a distributed SaaS team, covering:\n\nBusiness context:\nA SaaS startup based in Singapore has employees spread across Singapore and the wider Southeast Asia region, working remotely since its inception. While productivity is high, team alignment is slipping — duplicate work, missed deadlines, and miscommunications have become common. The CEO wants to implement a crisp yet structured weekly sync for the whole team to align priorities, surface blockers, and foster some informal bonding. Past attempts at weekly syncs either dragged too long or missed important points.\n\nDesired outcome:\nCreate a balanced remote weekly sync agenda that ensures alignment on key priorities, quick resolution of blockers, and some time for team culture building. The outcome should be a shared understanding of priorities and deadlines for the week.\n\nMy details:\n- Prompt 14 – Remote Team Weekly Sync Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Team size and structure\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":365,"title":"Prompt 15 – Quarterly Business Review (QBR) Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Beginner","explanation":"Create a QBR agenda that balances reviewing past performance with exploring future opportunities, strengthening client trust and upsell potential. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 15 – Quarterly Business Review (QBR) Agenda\"\n\nStarting brief:\n\"You are a client success strategist. Design a Quarterly Business Review agenda for an IT services company, including:\n\nBusiness context:\nA mid-tier IT services firm based in Singapore is introducing Quarterly Business Reviews with its key enterprise clients. In the past, client meetings have been overly tactical, missing the chance to demonstrate strategic value. The account managers need a formal QBR agenda that positions the company as a long-term partner, not just a vendor, and helps surface new business opportunities.\n\nDesired outcome:\nCreate a QBR agenda that balances reviewing past performance with exploring future opportunities, strengthening client trust and upsell potential.\n\nMy details:\n- Prompt 15 – Quarterly Business Review (QBR) Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client KPIs and goals\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":366,"title":"Prompt 16 – Budget Planning Meeting Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Develop an agenda that ensures budget decisions are tied to strategy, not just departmental wish lists. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 16 – Budget Planning Meeting Agenda\"\n\nStarting brief:\n\"You are a financial planning consultant. Create an annual budget planning meeting agenda for a consumer brand, covering:\n\nBusiness context:\nA Singapore-based D2C fashion brand is preparing its annual budget. In the past, finance meetings have been heavily number-focused, leaving little room for strategic discussion. The CFO wants a structured budget planning meeting that encourages department heads to link budget requests directly to measurable business outcomes and marketing ROI.\n\nDesired outcome:\nDevelop an agenda that ensures budget decisions are tied to strategy, not just departmental wish lists.\n\nMy details:\n- Prompt 16 – Budget Planning Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual growth target\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":367,"title":"Prompt 17 – Sales Pipeline Review Meeting Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Create an agenda for a sales pipeline review that focuses on deal velocity, conversion rates, and forecast accuracy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 17 – Sales Pipeline Review Meeting Agenda\"\n\nStarting brief:\n\"You are a sales operations strategist. Draft a monthly sales pipeline review agenda that includes:\n\nBusiness context:\nA B2B SaaS company headquartered in Singapore holds monthly sales pipeline reviews, but they often turn into long debates about individual deals instead of focusing on pipeline health. The VP of Sales wants an agenda that prioritises data-driven insights, identifies bottlenecks, and ensures sales reps leave with clear next steps.\n\nDesired outcome:\nCreate an agenda for a sales pipeline review that focuses on deal velocity, conversion rates, and forecast accuracy.\n\nMy details:\n- Prompt 17 – Sales Pipeline Review Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- CRM data export\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":368,"title":"Prompt 18 – Diversity & Inclusion Committee Meeting Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Design a D&I committee meeting agenda that moves from big-picture goals to concrete next steps, ensuring initiatives are tracked and reported. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 18 – Diversity & Inclusion Committee Meeting Agenda\"\n\nStarting brief:\n\"You are a workplace inclusivity advisor. Create a monthly D&I committee meeting agenda including:\n\nBusiness context:\nA large IT company based in Singapore has formed a Diversity & Inclusion (D&I) committee to drive initiatives across gender balance, accessibility, and inclusive hiring. The first few meetings have lacked focus, with discussions jumping between unrelated topics. The Chief People Officer wants a structured agenda that progresses from strategy to action, while tracking measurable impact over time.\n\nDesired outcome:\nDesign a D&I committee meeting agenda that moves from big-picture goals to concrete next steps, ensuring initiatives are tracked and reported.\n\nMy details:\n- Prompt 18 – Diversity & Inclusion Committee Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company D&I goals\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":369,"title":"Prompt 19 – Marketing Campaign Kick off Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Create a campaign kick-off meeting agenda that sets clear deliverables, timelines, and reporting structures from day one. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 19 – Marketing Campaign Kick off Agenda\"\n\nStarting brief:\n\"You are a marketing operations planner. Draft a 90-minute campaign kick-off meeting agenda including:\n\nBusiness context:\nA lifestyle brand headquartered in Singapore is launching its largest influencer-driven marketing campaign ahead of the Christmas and year-end shopping season. Previous campaign kick-off meetings have been chaotic, with unclear ownership, missed media deadlines, and last-minute creative changes. The CMO wants a kick-off agenda that gets all stakeholders — creative, media buying, influencer management, analytics — aligned before execution starts.\n\nDesired outcome:\nCreate a campaign kick-off meeting agenda that sets clear deliverables, timelines, and reporting structures from day one.\n\nMy details:\n- Prompt 19 – Marketing Campaign Kick off Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Campaign brief\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":370,"title":"Prompt 20 – Product Launch Readiness Review Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Design a readiness review agenda ensuring all departments confirm readiness and dependencies are addressed. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 20 – Product Launch Readiness Review Agenda\"\n\nStarting brief:\n\"You are a product launch coordinator. Draft a 2-hour product launch readiness review agenda including:\n\nBusiness context:\nA Singapore-based consumer electronics company headquartered in one-north is preparing to launch a new smart home device. In the past, launches have faced last-minute hiccups because product, marketing, sales, and customer service teams were not aligned. The COO wants a readiness review meeting that serves as a final checklist before launch.\n\nDesired outcome:\nDesign a readiness review agenda ensuring all departments confirm readiness and dependencies are addressed.\n\nMy details:\n- Prompt 20 – Product Launch Readiness Review Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Launch date\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":371,"title":"Prompt 21 – All Hands Company Update Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Beginner","explanation":"Create an all-hands meeting agenda that balances business updates with team recognition and employee Q&A. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 21 – All Hands Company Update Agenda\"\n\nStarting brief:\n\"You are an internal communications manager. Create a 60-minute all-hands meeting agenda for a fintech company including:\n\nBusiness context:\nA growing fintech company headquartered in Singapore's CBD holds quarterly all-hands meetings but struggles with keeping employees engaged. These sessions often turn into monologues from leadership, with minimal interaction or transparency. The HR team wants an engaging all-hands agenda that updates, inspires, and involves employees.\n\nDesired outcome:\nCreate an all-hands meeting agenda that balances business updates with team recognition and employee Q&A.\n\nMy details:\n- Prompt 21 – All Hands Company Update Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Latest company KPIs\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":372,"title":"Prompt 22 – Agile Sprint Planning Meeting Agenda","category":"Meetings","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Create a sprint planning meeting agenda that sets realistic sprint goals and task allocations while avoiding scope creep. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 22 – Agile Sprint Planning Meeting Agenda\"\n\nStarting brief:\n\"You are a Scrum Master. Draft a 2-hour sprint planning meeting agenda including:\n\nBusiness context:\nA product team based at a Singapore tech firm in one-north follows Scrum but often struggles to keep sprint planning sessions concise. Discussions tend to wander into problem-solving for specific tasks, delaying the overall process. The Scrum Master wants an agenda that structures discussions around priorities and commitments.\n\nDesired outcome:\nCreate a sprint planning meeting agenda that sets realistic sprint goals and task allocations while avoiding scope creep.\n\nMy details:\n- Prompt 22 – Agile Sprint Planning Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Updated backlog\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":373,"title":"Prompt 23 – Crisis Management Meeting Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Advanced","explanation":"Create a fast-paced, solution-oriented crisis meeting agenda. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 23 – Crisis Management Meeting Agenda\"\n\nStarting brief:\n\"You are a crisis communication strategist. Draft a 60-minute crisis management meeting agenda including:\n\nBusiness context:\nA Singapore-based food delivery startup faced a major PR crisis after a viral customer complaint spread across local social media. The leadership team needs a crisis management meeting agenda to coordinate damage control across PR, legal, operations, and customer service.\n\nDesired outcome:\nCreate a fast-paced, solution-oriented crisis meeting agenda.\n\nMy details:\n- Prompt 23 – Crisis Management Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Crisis details and timeline\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":374,"title":"Prompt 24 – Innovation Brainstorm Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Create an innovation brainstorming agenda that channels creativity into practical, testable ideas. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 24 – Innovation Brainstorm Agenda\"\n\nStarting brief:\n\"You are an innovation workshop facilitator. Draft a 2-hour brainstorming meeting agenda including:\n\nBusiness context:\nAn edtech startup headquartered in Singapore wants to hold quarterly innovation sessions to crowdsource ideas from employees for new products and process improvements. Previous attempts at brainstorming have resulted in unfocused discussions and few actionable outcomes.\n\nDesired outcome:\nCreate an innovation brainstorming agenda that channels creativity into practical, testable ideas.\n\nMy details:\n- Prompt 24 – Innovation Brainstorm Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Recent market research\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":375,"title":"Prompt 25 – Customer Feedback Review Meeting Agenda","category":"Customer Comms","source":"Admin & Ops","module":"Team Meeting Agendas","difficulty":"Intermediate","explanation":"Design a customer feedback review agenda that links guest sentiment directly to operational changes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a customer communication specialist who is clear, empathetic, and operationally precise. Help me create a polished, workplace-ready output for this task:\n\"Prompt 25 – Customer Feedback Review Meeting Agenda\"\n\nStarting brief:\n\"You are a customer experience strategist. Create a 90-minute customer feedback review meeting agenda including:\n\nBusiness context:\nA mid-sized hospitality chain collects guest feedback through surveys and online reviews but rarely acts on it systematically. The COO wants a monthly meeting to review customer insights and translate them into service improvements.\n\nDesired outcome:\nDesign a customer feedback review agenda that links guest sentiment directly to operational changes.\n\nMy details:\n- Prompt 25 – Customer Feedback Review Meeting Agenda details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Latest feedback reports\n- customer issue\n- known facts\n- policy or SLA\n- resolution options\n- tone level\n- stakeholders\n- deadline\n- policy or process constraints\n- required tone\n- next action owner\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Acknowledge the customer impact in plain language without overpromising.\n2. Explain the situation using only confirmed facts and avoid blame.\n3. Give clear next steps, timeline, owner, and escalation route.\n4. Create one polished response plus a shorter version for chat or SMS when useful.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Recommended response\n- Short version\n- Internal handling notes\n- Follow-up checklist\n- Risk or compliance notes\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not admit fault, promise compensation, or disclose internal details unless the employee provides approved wording.\n- Check ownership, timelines, policy fit, customer or employee impact, and escalation path.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💬","color":"cat-orange"},{"id":376,"title":"Monthly Expense Categorization for Small Businesses","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Advanced","explanation":"Generate a categorized monthly expense report ready for accounting and compliance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Monthly Expense Categorization for Small Businesses\"\n\nStarting brief:\nYou are a professional accountant. Create a categorized monthly expense report for a small business in Singapore.\n\nBusiness context:\nYou have a 31-year-old entrepreneur running a boutique in Singapore who uses PayNow, bank transfers, and occasional cash payments for business transactions. They struggle to track and categorize monthly expenses, especially distinguishing between personal and business spending. They want a clean breakdown for GST filing and internal tracking.\n\nDesired outcome:\nGenerate a categorized monthly expense report ready for accounting and compliance.\n\nMy details:\n- Monthly Expense Categorization for Small Businesses details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of all transactions with date\n- amount\n- and payment method\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":377,"title":"Bank Statement Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Generate a reconciled statement showing matched and unmatched transactions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Bank Statement Reconciliation\"\n\nStarting brief:\nYou are a certified bookkeeper. Reconcile the given bank statement with the provided invoice list.\n\nBusiness context:\nA 27-year-old freelancer based in Singapore earns from multiple sources — Upwork, Fiverr, and direct clients. Payments come in via PayPal, bank transfers, and PayNow. At month-end, they need to reconcile their bank statement with project invoices to ensure all payments are received and recorded.\n\nDesired outcome:\nGenerate a reconciled statement showing matched and unmatched transactions.\n\nMy details:\n- Bank Statement Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Bank statement (CSV, PDF\n- or Excel)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":378,"title":"Petty Cash Tracking for Retail Stores","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Create a daily petty cash log with balances updated after every transaction. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Petty Cash Tracking for Retail Stores\"\n\nStarting brief:\nYou are a retail accounting specialist. Create a petty cash log for one month.\n\nBusiness context:\nA family-owned stationery shop in a Tampines HDB neighbourhood uses petty cash for small daily expenses — coffee for staff, packaging materials, and urgent stock buys. The store owner often forgets to record cash withdrawals and wants a transparent petty cash ledger to monitor leakage.\n\nDesired outcome:\nCreate a daily petty cash log with balances updated after every transaction.\n\nMy details:\n- Petty Cash Tracking for Retail Stores details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Starting petty cash amount\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":379,"title":"Automating PayNow Payment Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Match PayNow and e-wallet transaction data with daily sales data to confirm no payments are missing. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Automating PayNow Payment Reconciliation\"\n\nStarting brief:\nYou are a fintech reconciliation expert. Match the PayNow and e-wallet transaction log with the daily sales records for the month.\n\nBusiness context:\nA café owner in Singapore accepts payments via multiple e-wallets and QR rails (PayNow, GrabPay, DBS PayLah!). End-of-month reconciliation is messy because transaction IDs differ between the café's billing software and the bank statement. They want an automated way to match digital payments to daily sales.\n\nDesired outcome:\nMatch PayNow and e-wallet transaction data with daily sales data to confirm no payments are missing.\n\nMy details:\n- Automating PayNow Payment Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- PayNow / e-wallet transaction log (CSV/Excel)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":380,"title":"Annual Ledger Cleanup","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Prepare a clean, consistent ledger for the fiscal year. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual Ledger Cleanup\"\n\nStarting brief:\nYou are an accounting data cleanup specialist. Review and clean the provided ledger for FY 2024–25.\n\nBusiness context:\nA 35-year-old manufacturing SME based in Tuas has an annual ledger cluttered with duplicate entries, misspelled vendor names, and inconsistent expense categories. Before the annual audit, they need the ledger cleaned and standardized.\n\nDesired outcome:\nPrepare a clean, consistent ledger for the fiscal year.\n\nMy details:\n- Annual Ledger Cleanup details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":381,"title":"Vendor Payment Tracking","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Maintain a clear vendor payment status sheet for the month. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Vendor Payment Tracking\"\n\nStarting brief:\nYou are an accounts payable specialist. Create a vendor payment tracker for the given month.\n\nBusiness context:\nA 29-year-old procurement manager at a small catering business in Singapore handles 12–15 vendors supplying everything from fresh produce to packaging. Payments are made partly in advance and partly after delivery. She needs a monthly vendor payment tracker to ensure no supplier is overpaid or missed.\n\nDesired outcome:\nMaintain a clear vendor payment status sheet for the month.\n\nMy details:\n- Vendor Payment Tracking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of vendor invoices with amounts and due dates\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":382,"title":"Client Receivables Aging Report","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Generate a receivables aging report categorizing clients by overdue days. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Client Receivables Aging Report\"\n\nStarting brief:\nYou are an accounts receivable analyst. Create an aging report for all unpaid client invoices.\n\nBusiness context:\nA freelance graphic designer based in Singapore works with multiple clients, some paying late. She wants to know how long payments have been pending so she can follow up professionally without losing clients.\n\nDesired outcome:\nGenerate a receivables aging report categorizing clients by overdue days.\n\nMy details:\n- Client Receivables Aging Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client invoice list with issue dates and amounts\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":383,"title":"GST Input Output Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Advanced","explanation":"Reconcile GST input vs. output with discrepancies flagged. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Input Output Reconciliation\"\n\nStarting brief:\nYou are a Singapore GST compliance specialist. Match supplier GST-registered invoices against sales invoices to reconcile input and output GST at the prevailing 9% rate.\n\nBusiness context:\nA boutique clothing brand in Singapore needs to reconcile GST input tax credit from supplier invoices with GST output liability from sales invoices to prepare for the quarterly IRAS GST return.\n\nDesired outcome:\nReconcile GST input vs. output with discrepancies flagged.\n\nMy details:\n- GST Input Output Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase invoices with GST details\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":384,"title":"Foreign Currency Transaction Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Reconcile foreign currency inflows with correct SGD conversions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Foreign Currency Transaction Reconciliation\"\n\nStarting brief:\nYou are a forex accounting specialist. Reconcile foreign currency receipts with invoice amounts and bank credits.\n\nBusiness context:\nA startup in Singapore exports software services and receives payments in USD and EUR. Exchange rates fluctuate, and the finance head needs a monthly reconciliation showing SGD equivalents and forex gain/loss.\n\nDesired outcome:\nReconcile foreign currency inflows with correct SGD conversions.\n\nMy details:\n- Foreign Currency Transaction Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Invoice list with currency and rates used\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":385,"title":"Loan Payment Tracking","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Maintain a monthly loan payment tracker with due dates and outstanding balances. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Loan Payment Tracking\"\n\nStarting brief:\nYou are a business finance tracker. Create a loan repayment schedule for all active loans.\n\nBusiness context:\nA manufacturing unit based in Tuas has 3 active business loans with different banks (DBS, OCBC, UOB). The owner struggles to track monthly instalment dates, amounts, and interest components.\n\nDesired outcome:\nMaintain a monthly loan payment tracker with due dates and outstanding balances.\n\nMy details:\n- Loan Payment Tracking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Loan facility letters or repayment schedules\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":386,"title":"Annual Cash Flow Summary","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Create a visual annual cash flow report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual Cash Flow Summary\"\n\nStarting brief:\nYou are a financial analyst. Summarize annual cash inflows and outflows for the given year.\n\nBusiness context:\nA home bakery in Tampines accepts PayNow and cash payments and spends on ingredients, packaging, and marketing. At year-end, they want a summary showing total inflows vs. outflows.\n\nDesired outcome:\nCreate a visual annual cash flow report.\n\nMy details:\n- Annual Cash Flow Summary details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of all transactions\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":387,"title":"Duplicate Payment Audit","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Identify and flag duplicate payments. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Duplicate Payment Audit\"\n\nStarting brief:\nYou are an audit specialist. Review all supplier payments for possible duplicates.\n\nBusiness context:\nAn NGO based in Singapore suspects that a few suppliers have been accidentally paid twice for the same invoice. They want a review of last year's transactions to confirm.\n\nDesired outcome:\nIdentify and flag duplicate payments.\n\nMy details:\n- Duplicate Payment Audit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Supplier payment register\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":388,"title":"Expense Approval Workflow","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Track expense approval status for each claim. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Expense Approval Workflow\"\n\nStarting brief:\nYou are a process documentation specialist. Create an expense claim tracker.\n\nBusiness context:\nA digital marketing agency in one-north reimburses employee expenses for client work. The accounts team wants a simple approval tracker to avoid delays.\n\nDesired outcome:\nTrack expense approval status for each claim.\n\nMy details:\n- Expense Approval Workflow details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of claims\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":389,"title":"POS Sales vs Bank Credit Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Reconcile POS daily sales to bank deposits. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"POS Sales vs Bank Credit Reconciliation\"\n\nStarting brief:\nYou are a POS reconciliation expert. Match POS transaction list with bank statement credits.\n\nBusiness context:\nA grocery store in Bedok uses a POS terminal for NETS and card transactions but sees delays before money reflects in the bank account. They want to match POS receipts to bank credits.\n\nDesired outcome:\nReconcile POS daily sales to bank deposits.\n\nMy details:\n- POS Sales vs Bank Credit Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- POS transaction report\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":390,"title":"E commerce Payment Gateway Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Match order IDs to payment gateway payouts. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"E commerce Payment Gateway Reconciliation\"\n\nStarting brief:\nYou are an e-commerce finance specialist. Match shipped orders to payment gateway deposits.\n\nBusiness context:\nA Singapore-based seller on Shopee and Lazada gets payouts via Stripe. They want to ensure every order shipped is paid for after deductions.\n\nDesired outcome:\nMatch order IDs to payment gateway payouts.\n\nMy details:\n- E commerce Payment Gateway Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Order shipment report\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":391,"title":"Subscription Payment Tracking","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Track subscription renewals and failed transactions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Subscription Payment Tracking\"\n\nStarting brief:\nYou are a subscription finance tracker. Create a subscription payment log with:\n\nBusiness context:\nA SaaS startup in Paya Lebar charges monthly subscriptions but struggles to track renewals and failed payments.\n\nDesired outcome:\nTrack subscription renewals and failed transactions.\n\nMy details:\n- Subscription Payment Tracking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer subscription database\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":392,"title":"Credit Card Expense Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Match card statement entries to receipts for expense verification. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Credit Card Expense Reconciliation\"\n\nStarting brief:\nYou are a corporate expense auditor. Reconcile credit card transactions to provided receipts.\n\nBusiness context:\nA consultancy in Raffles Place uses a corporate credit card for travel and entertainment expenses. The finance team needs to reconcile card statements with receipts.\n\nDesired outcome:\nMatch card statement entries to receipts for expense verification.\n\nMy details:\n- Credit Card Expense Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Credit card statement\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":393,"title":"Advance Payment Settlement","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Track advance payments and settlement status. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Advance Payment Settlement\"\n\nStarting brief:\nYou are a project finance tracker. Create a log for advances taken and settled.\n\nBusiness context:\nA wedding planner in Singapore takes deposit payments from clients and vendors but struggles to match them to final invoices.\n\nDesired outcome:\nTrack advance payments and settlement status.\n\nMy details:\n- Advance Payment Settlement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of all advances taken\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":394,"title":"Payroll Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Reconcile payroll payouts to bank credits. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Payroll Reconciliation\"\n\nStarting brief:\nYou are a payroll reconciliation specialist. Match payroll register entries with bank transfer statements.\n\nBusiness context:\nA mid-sized international school in Bukit Timah processes monthly salaries but finds mismatches between payroll register and bank transfers.\n\nDesired outcome:\nReconcile payroll payouts to bank credits.\n\nMy details:\n- Payroll Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Payroll register\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":395,"title":"Cheque Clearing Tracker","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Track cheque deposits and clearance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Cheque Clearing Tracker\"\n\nStarting brief:\nYou are a cheque processing tracker. Create a report showing:\n\nBusiness context:\nA construction company in Tuas receives large payments via cheques. They want to track clearing status and bounced cheques.\n\nDesired outcome:\nTrack cheque deposits and clearance.\n\nMy details:\n- Cheque Clearing Tracker details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of cheques received\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":396,"title":"Year End Trial Balance Preparation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Intermediate","explanation":"Prepare a complete trial balance. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Year End Trial Balance Preparation\"\n\nStarting brief:\nYou are an accountant. Prepare a trial balance from provided data.\n\nBusiness context:\nA Singapore-registered NGO needs a trial balance ready for audit but their accounts are scattered across bank statements, receipts, and Excel sheets.\n\nDesired outcome:\nPrepare a complete trial balance.\n\nMy details:\n- Year End Trial Balance Preparation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Ledger data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":397,"title":"Fixed Asset Register Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Reconcile fixed asset register with actual purchases/disposals. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Fixed Asset Register Reconciliation\"\n\nStarting brief:\nYou are an asset accountant. Update the fixed asset register by:\n\nBusiness context:\nA factory in Jurong maintains a fixed asset register but hasn't updated disposals and new purchases this year.\n\nDesired outcome:\nReconcile fixed asset register with actual purchases/disposals.\n\nMy details:\n- Fixed Asset Register Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current asset register\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":398,"title":"Internal Fund Transfer Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Match internal transfers across accounts. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Internal Fund Transfer Reconciliation\"\n\nStarting brief:\n\"You are a treasury reconciliation specialist. Match all internal transfers between bank accounts by date and amount.\n\nBusiness context:\nA company with multiple bank accounts transfers funds internally. They want to match debits in one account with credits in another.\n\nDesired outcome:\nMatch internal transfers across accounts.\n\nMy details:\n- Internal Fund Transfer Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Statements for all accounts\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":399,"title":"Prepaid Expense Amortization","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Beginner","explanation":"Create monthly expense recognition for prepaids. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Prepaid Expense Amortization\"\n\nStarting brief:\nYou are an accountant. Amortize prepaid expenses across relevant months.\n\nBusiness context:\nA firm in Singapore has prepaid annual insurance and software subscriptions. They want monthly amortization entries for accurate books.\n\nDesired outcome:\nCreate monthly expense recognition for prepaids.\n\nMy details:\n- Prepaid Expense Amortization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of prepaid expenses with start/end dates\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":400,"title":"Partner Capital Account Reconciliation","category":"Finance & Ops","source":"Finance","module":"Bookkeeping reconciliation","difficulty":"Advanced","explanation":"Prepare final partner capital balances. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Partner Capital Account Reconciliation\"\n\nStarting brief:\nYou are a partnership accounts specialist. Reconcile capital accounts showing:\n\nBusiness context:\nA Singapore partnership firm needs to reconcile partner capital accounts after profit distribution and withdrawals.\n\nDesired outcome:\nPrepare final partner capital balances.\n\nMy details:\n- Partner Capital Account Reconciliation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Partner agreement terms\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":401,"title":"Pre Funding Startup Valuation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate a pre-funding valuation using multiple methods. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Pre Funding Startup Valuation\"\n\nStarting brief:\n\"You are a startup valuation analyst. Calculate the company's pre-funding valuation using:\n\nBusiness context:\nA 29-year-old founder based in one-north, Singapore runs a SaaS platform for small retailers. She's in talks with angel investors but needs to present a credible pre-funding valuation. The startup has been operational for 18 months, has S$1.8 million in ARR, and is growing at 15% month-on-month. She wants a valuation based on both revenue multiples and the discounted cash flow (DCF) method so she can justify her ask during investor meetings.\n\nDesired outcome:\nCalculate a pre-funding valuation using multiple methods.\n\nMy details:\n- Pre Funding Startup Valuation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current ARR and MRR\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":402,"title":"ROI Calculation for New Product Launch","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI for a product launch over multiple time frames. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI Calculation for New Product Launch\"\n\nStarting brief:\n\"You are a product finance analyst. Calculate ROI for the product launch:\n\nBusiness context:\nA 31-year-old FMCG entrepreneur in Singapore plans to launch a new flavoured beverage line for the Southeast Asia market. She has projected development and marketing costs of S$600,000 and expects to sell 200,000 units in the first year. She wants to know the ROI for year one and over a three-year horizon, factoring in unit price, expected margins, and marketing expenses.\n\nDesired outcome:\nCalculate ROI for a product launch over multiple time frames.\n\nMy details:\n- ROI Calculation for New Product Launch details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Development\n- production\n- and marketing costs\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":403,"title":"Valuation for Business Sale","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate fair market valuation using asset-based and earnings multiples methods. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation for Business Sale\"\n\nStarting brief:\n\"You are a business broker. Calculate valuation using:\n\nBusiness context:\nA 34-year-old restaurateur in Singapore is considering selling his 4-year-old fine dining restaurant in the CBD. He has consistent annual revenues of S$4.5 million with a 15% net profit margin. The buyer wants a fair market valuation considering both the asset value and earnings potential.\n\nDesired outcome:\nCalculate fair market valuation using asset-based and earnings multiples methods.\n\nMy details:\n- Valuation for Business Sale details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Latest P&L statement\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":404,"title":"ROI from Digital Marketing Campaign","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate net ROI from the campaign after all costs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI from Digital Marketing Campaign\"\n\nStarting brief:\n\"You are a marketing ROI analyst. Calculate ROI for the campaign:\n\nBusiness context:\nA 27-year-old D2C brand owner in Singapore ran a 6-month Facebook and Instagram ad campaign costing S$60,000. The campaign generated S$600,000 in sales, but she's unsure of the true ROI after considering product costs, returns, and ad agency fees.\n\nDesired outcome:\nCalculate net ROI from the campaign after all costs.\n\nMy details:\n- ROI from Digital Marketing Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Campaign spend\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":405,"title":"Pre IPO Company Valuation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Estimate pre-IPO valuation using market comparables and DCF. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Pre IPO Company Valuation\"\n\nStarting brief:\n\"You are an investment banker. Calculate valuation using:\n\nBusiness context:\nA 32-year-old CFO at a mid-sized tech firm headquartered in Singapore's one-north precinct is preparing for a possible SGX listing. The company has S$80 million in annual revenue, strong profitability, and significant brand presence across Southeast Asia. He wants a valuation using comparable listed company multiples and DCF to present to investment bankers.\n\nDesired outcome:\nEstimate pre-IPO valuation using market comparables and DCF.\n\nMy details:\n- Pre IPO Company Valuation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical financials for 3–5 years\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":406,"title":"Valuation of Franchise Business","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate the valuation of the franchise considering operational profits and future royalty changes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation of Franchise Business\"\n\nStarting brief:\n\"You are a franchise valuation consultant. Calculate the business value using:\n\nBusiness context:\nA 30-year-old entrepreneur in Singapore operates 3 franchise outlets of a popular coffee chain across Orchard, Tampines, and Jurong East. Each outlet has consistent footfall and steady profits, but the franchisor is changing royalty rates next year. She wants to value her franchise operations to negotiate with a potential buyer who is interested in taking over all three outlets.\n\nDesired outcome:\nCalculate the valuation of the franchise considering operational profits and future royalty changes.\n\nMy details:\n- Valuation of Franchise Business details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Last 3 years' P&L for each outlet\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":407,"title":"ROI for New Manufacturing Equipment","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI and payback period for new equipment investment. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI for New Manufacturing Equipment\"\n\nStarting brief:\n\"You are a manufacturing finance analyst. Calculate:\n\nBusiness context:\nA 28-year-old production manager at a precision engineering plant in Tuas, Singapore is considering buying an advanced CNC machine costing S$400,000. The machine promises higher efficiency and reduced wastage, potentially increasing annual profits by S$85,000. Management wants to know the ROI and payback period before approving the purchase.\n\nDesired outcome:\nCalculate ROI and payback period for new equipment investment.\n\nMy details:\n- ROI for New Manufacturing Equipment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Equipment cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":408,"title":"Startup Valuation for Seed Funding","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Value a pre-revenue startup using alternative valuation methods. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Startup Valuation for Seed Funding\"\n\nStarting brief:\n\"You are a startup funding advisor. Estimate valuation using:\n\nBusiness context:\nA 26-year-old founder in Singapore has built a health-tech app with 50,000 monthly active users across Singapore and Malaysia but limited revenue. She wants a valuation for seed funding discussions using the Berkus method and comparable early-stage startup deals.\n\nDesired outcome:\nValue a pre-revenue startup using alternative valuation methods.\n\nMy details:\n- Startup Valuation for Seed Funding details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- User base and growth rate\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":409,"title":"ROI from Corporate Training Program","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI from training investment using HR metrics. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI from Corporate Training Program\"\n\nStarting brief:\n\"You are an HR analytics consultant. Calculate training ROI:\n\nBusiness context:\nA 33-year-old HR manager at a Singapore-based firm spent S$50,000 on a leadership training program for mid-level managers. She wants to show management the ROI by correlating it to reduced attrition and improved productivity.\n\nDesired outcome:\nCalculate ROI from training investment using HR metrics.\n\nMy details:\n- ROI from Corporate Training Program details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Training costs\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":410,"title":"Valuation for ESOP Pricing","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate FMV for ESOP allotment. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation for ESOP Pricing\"\n\nStarting brief:\n\"You are a corporate finance advisor. Calculate FMV using:\n\nBusiness context:\nA 31-year-old CFO at a fintech startup based in Singapore's CBD needs to determine the fair market value (FMV) of shares for issuing ESOPs to employees, in compliance with Singapore tax laws and IRAS guidelines.\n\nDesired outcome:\nCalculate FMV for ESOP allotment.\n\nMy details:\n- Valuation for ESOP Pricing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company financial statements\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":411,"title":"ROI for Retail Store Renovation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI from store renovation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI for Retail Store Renovation\"\n\nStarting brief:\n\"You are a retail finance consultant. Calculate:\n\nBusiness context:\nA 28-year-old boutique owner with a shop in Singapore's Orchard Road area is planning a S$80,000 renovation to improve store design and customer experience. She expects this to increase footfall by 30% and sales by 20%.\n\nDesired outcome:\nCalculate ROI from store renovation.\n\nMy details:\n- ROI for Retail Store Renovation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Renovation cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":412,"title":"Startup Exit Valuation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Estimate fair acquisition value using market data. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Startup Exit Valuation\"\n\nStarting brief:\n\"You are an M&A analyst. Calculate exit valuation using:\n\nBusiness context:\nA 34-year-old founder in Singapore is negotiating an acquisition offer for his B2B SaaS startup serving clients across Southeast Asia. He needs to know if the offer aligns with industry exit multiples and his company's growth potential.\n\nDesired outcome:\nEstimate fair acquisition value using market data.\n\nMy details:\n- Startup Exit Valuation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current ARR and EBITDA\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":413,"title":"ROI for Solar Panel Installation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI and payback period for solar investment. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI for Solar Panel Installation\"\n\nStarting brief:\n\"You are a sustainability finance analyst. Calculate:\n\nBusiness context:\nA 30-year-old factory owner with a plant in Tuas, Singapore is considering installing rooftop solar panels costing S$180,000 to reduce electricity bills. The panels are expected to save S$32,000 annually.\n\nDesired outcome:\nCalculate ROI and payback period for solar investment.\n\nMy details:\n- ROI for Solar Panel Installation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Installation cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":414,"title":"Franchise ROI Evaluation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Evaluate ROI and feasibility of the franchise. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Franchise ROI Evaluation\"\n\nStarting brief:\n\"You are a franchise ROI consultant. Calculate:\n\nBusiness context:\nA 27-year-old entrepreneur in Singapore is considering buying a fast-food franchise for S$120,000 upfront and S$10,000/month operating costs. Expected monthly revenue is S$20,000.\n\nDesired outcome:\nEvaluate ROI and feasibility of the franchise.\n\nMy details:\n- Franchise ROI Evaluation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Franchise investment cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":415,"title":"Valuation of E commerce Business for Sale","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate e-commerce business valuation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation of E commerce Business for Sale\"\n\nStarting brief:\n\"You are an e-commerce business broker. Calculate valuation using:\n\nBusiness context:\nA 32-year-old e-commerce entrepreneur in Singapore runs a Shopee and Lazada store with S$2 million in annual revenue and S$320,000 profit. She wants to sell the business and needs a valuation based on profit multiples and market comparables.\n\nDesired outcome:\nCalculate e-commerce business valuation.\n\nMy details:\n- Valuation of E commerce Business for Sale details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual revenue and profit\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":416,"title":"ROI of Influencer Marketing","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate influencer marketing ROI. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI of Influencer Marketing\"\n\nStarting brief:\n\"You are a marketing analytics consultant. Calculate:\n\nBusiness context:\nA 26-year-old fashion startup founder in Singapore spent S$40,000 on influencer campaigns with local Instagram and TikTok creators. She wants to measure the ROI by comparing sales generated directly from influencer links vs. the cost.\n\nDesired outcome:\nCalculate influencer marketing ROI.\n\nMy details:\n- ROI of Influencer Marketing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Campaign cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":417,"title":"Valuation for Partnership Buyout","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate a fair buyout value. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation for Partnership Buyout\"\n\nStarting brief:\n\"You are a partnership valuation expert. Calculate buyout value using:\n\nBusiness context:\nA 31-year-old co-owner of a small manufacturing SME based in Tuas, Singapore wants to buy out his partner's 50% stake. He needs a valuation that is fair to both parties using earnings multiples and asset valuations.\n\nDesired outcome:\nCalculate a fair buyout value.\n\nMy details:\n- Valuation for Partnership Buyout details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual profit and assets list\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":418,"title":"ROI for Event Sponsorship","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Evaluate event sponsorship ROI. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI for Event Sponsorship\"\n\nStarting brief:\n\"You are a brand ROI analyst. Calculate:\n\nBusiness context:\nA 28-year-old beverage brand owner in Singapore sponsored a major sports event at the Singapore Sports Hub for S$70,000. She wants to calculate ROI in terms of increased sales and brand awareness.\n\nDesired outcome:\nEvaluate event sponsorship ROI.\n\nMy details:\n- ROI for Event Sponsorship details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sponsorship cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":419,"title":"Liquidation Value Estimation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Estimate liquidation value of assets. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Liquidation Value Estimation\"\n\nStarting brief:\n\"You are an asset valuation consultant. Calculate:\n\nBusiness context:\nA 33-year-old manufacturing business owner in Singapore needs to shut down operations at her Jurong facility and sell assets. She wants to know the liquidation value of machinery, inventory, and other assets for settlement planning.\n\nDesired outcome:\nEstimate liquidation value of assets.\n\nMy details:\n- Liquidation Value Estimation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Asset list with purchase details\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":420,"title":"ROI for R&D Project","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI and NPV for the R&D project. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI for R&D Project\"\n\nStarting brief:\n\"You are a pharma project analyst. Calculate:\n\nBusiness context:\nA 30-year-old pharma company R&D head at a biotech firm in Singapore's Biopolis (one-north) is testing a new drug formulation. The project costs S$700,000 and could generate S$170,000 annually for 8 years if approved.\n\nDesired outcome:\nCalculate ROI and NPV for the R&D project.\n\nMy details:\n- ROI for R&D Project details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":421,"title":"Valuation for Joint Venture Negotiation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Value business for JV equity discussions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation for Joint Venture Negotiation\"\n\nStarting brief:\n\"You are a joint venture valuation advisor. Calculate valuation using:\n\nBusiness context:\nA 29-year-old agri-food business owner in Singapore is forming a joint venture with a regional logistics company. She needs a valuation of her business to determine equity split.\n\nDesired outcome:\nValue business for JV equity discussions.\n\nMy details:\n- Valuation for Joint Venture Negotiation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Business revenue and profits\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":422,"title":"ROI of Employee Wellness Program","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate ROI for wellness programs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI of Employee Wellness Program\"\n\nStarting brief:\n\"You are an HR ROI analyst. Calculate:\n\nBusiness context:\nA 32-year-old HR head at a Singapore company implemented a wellness program costing S$150,000. She wants to evaluate its ROI through reduced sick days and improved productivity.\n\nDesired outcome:\nCalculate ROI for wellness programs.\n\nMy details:\n- ROI of Employee Wellness Program details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Program cost\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":423,"title":"Pre Merger Synergy Valuation","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Calculate synergy value for a merger. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Pre Merger Synergy Valuation\"\n\nStarting brief:\n\"You are an M&A consultant. Calculate:\n\nBusiness context:\nA 34-year-old founder based in one-north Singapore is merging with a competitor. She needs to estimate the additional value generated from synergies like shared distribution and reduced marketing costs.\n\nDesired outcome:\nCalculate synergy value for a merger.\n\nMy details:\n- Pre Merger Synergy Valuation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current cost structures of both companies\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":424,"title":"ROI of Export Market Expansion","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Evaluate export expansion ROI. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ROI of Export Market Expansion\"\n\nStarting brief:\n\"You are an export business analyst. Calculate:\n\nBusiness context:\nA 30-year-old textile exporter in Singapore invested S$400,000 in entering the European market. She wants to know the ROI based on first-year export orders and projected growth.\n\nDesired outcome:\nEvaluate export expansion ROI.\n\nMy details:\n- ROI of Export Market Expansion details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Market entry costs\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":425,"title":"Valuation for Buy Sell Agreement","category":"Finance & Ops","source":"Finance","module":"Business valuation ROI calculation","difficulty":"Advanced","explanation":"Prepare a valuation for a professional services partnership. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Valuation for Buy Sell Agreement\"\n\nStarting brief:\n\"You are a professional services valuation expert. Calculate:\n\nBusiness context:\nA 33-year-old partner in a law firm in the Singapore CBD wants a formal valuation for their buy-sell agreement in case one partner exits. The valuation must consider earnings, client base value, and goodwill.\n\nDesired outcome:\nPrepare a valuation for a professional services partnership.\n\nMy details:\n- Valuation for Buy Sell Agreement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual revenue and profits\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":426,"title":"Monthly Profit & Loss Report for Startup","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create a clean, standardized monthly profit and loss report for a small business. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Monthly Profit & Loss Report for Startup\"\n\nStarting brief:\nYou are a startup finance analyst. Prepare a monthly P&L report in Excel format.\n\nBusiness context:\nA 27-year-old founder in Singapore runs a food delivery cloud kitchen. She receives payments from foodpanda, GrabFood, Deliveroo, and direct orders, while paying for rent, salaries, raw materials, and delivery partners. At month-end, she struggles to put together a P&L because income comes in different formats and expenses are logged inconsistently. She wants a standardized monthly P&L report to track growth and investor readiness.\n\nDesired outcome:\nCreate a clean, standardized monthly profit and loss report for a small business.\n\nMy details:\n- Monthly Profit & Loss Report for Startup details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly sales data by channel\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":427,"title":"Cash Flow Statement for Freelancers","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a monthly cash flow statement with projections. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Cash Flow Statement for Freelancers\"\n\nStarting brief:\nYou are a personal finance tracker. Prepare a cash flow statement for the freelancer.\n\nBusiness context:\nA 29-year-old freelance UI/UX designer in Singapore receives payments from local clients and overseas clients, often months apart. She sometimes faces cash shortages because her expense planning isn't aligned with irregular income. She wants a monthly cash flow statement showing inflows, outflows, and projected balances to plan better.\n\nDesired outcome:\nPrepare a monthly cash flow statement with projections.\n\nMy details:\n- Cash Flow Statement for Freelancers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly income by source\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":428,"title":"Quarterly Investor Update Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create a polished quarterly investor update report with financial metrics. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Quarterly Investor Update Report\"\n\nStarting brief:\nYou are a startup reporting specialist. Create a quarterly investor update with:\n\nBusiness context:\nA 30-year-old co-founder of a SaaS startup in Singapore has seed investors who require quarterly performance updates. They expect financial KPIs, revenue growth, expense ratios, and future plans in a professional, visually appealing format. The founders have raw numbers but no structured presentation.\n\nDesired outcome:\nCreate a polished quarterly investor update report with financial metrics.\n\nMy details:\n- Quarterly Investor Update Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Quarterly financial statements\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":429,"title":"Annual Budget vs. Actual Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a detailed budget vs. actual variance report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual Budget vs. Actual Report\"\n\nStarting brief:\nYou are a budgeting analyst. Prepare an annual budget vs. actual report.\n\nBusiness context:\nA 32-year-old operations head at a digital marketing agency in Singapore prepared an annual budget at the start of the year. Now, management wants to compare actuals with the budget to identify overspending areas and better plan next year's targets.\n\nDesired outcome:\nPrepare a detailed budget vs. actual variance report.\n\nMy details:\n- Annual Budget vs. Actual Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Original annual budget\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":430,"title":"KPI Dashboard for E commerce Store","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Advanced","explanation":"Create a visual KPI dashboard linking sales, expenses, and profitability. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"KPI Dashboard for E commerce Store\"\n\nStarting brief:\nYou are an e-commerce analytics expert. Create a KPI dashboard in Excel/Google Sheets.\n\nBusiness context:\nA 25-year-old online store owner in Singapore sells fashion accessories on Shopify. She wants a financial KPI dashboard showing sales trends, gross margins, and ad spend ROI so she can decide whether to increase marketing budgets.\n\nDesired outcome:\nCreate a visual KPI dashboard linking sales, expenses, and profitability.\n\nMy details:\n- KPI Dashboard for E commerce Store details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales data by day/month\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":431,"title":"Department Wise Expense Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a quarterly department-wise expense report with variance analysis. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Department Wise Expense Report\"\n\nStarting brief:\nYou are a corporate finance analyst. Prepare a department-wise expense report for the quarter.\n\nBusiness context:\nA 31-year-old finance manager at a mid-sized IT company in Singapore needs to present a quarterly expense breakdown by department (HR, Marketing, IT, Operations) to the CEO. Currently, all expenses are in one lump sum, making it hard to see which department is overspending. The CEO wants an easy-to-read report with color-coded variance indicators.\n\nDesired outcome:\nPrepare a quarterly department-wise expense report with variance analysis.\n\nMy details:\n- Department Wise Expense Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Expense data categorized by department\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":432,"title":"GST Collection & Payment Summary","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create a GST collection and payment summary for the month. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Collection & Payment Summary\"\n\nStarting brief:\nYou are a GST accountant. Prepare a monthly GST summary report.\n\nBusiness context:\nA 28-year-old owner of a small electronics store in Singapore wants a monthly GST report summarizing total GST collected from customers and GST paid to suppliers, along with net payable or refundable amounts. This helps him prepare for IRAS GST return filing without last-minute stress.\n\nDesired outcome:\nCreate a GST collection and payment summary for the month.\n\nMy details:\n- GST Collection & Payment Summary details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales invoice list with GST amounts\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":433,"title":"Project Based Profitability Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a profitability report for each active project. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Project Based Profitability Report\"\n\nStarting brief:\nYou are a project finance analyst. Create a profitability report for all projects.\n\nBusiness context:\nA 30-year-old project manager in a construction company in Singapore handles multiple client projects. Management wants to know which projects are most profitable by comparing revenue generated with direct costs and allocated overheads.\n\nDesired outcome:\nPrepare a profitability report for each active project.\n\nMy details:\n- Project Based Profitability Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project revenue and cost data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":434,"title":"Sales Performance Report by Region","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create a region-wise sales performance report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Sales Performance Report by Region\"\n\nStarting brief:\nYou are a sales reporting specialist. Prepare a monthly regional sales report.\n\nBusiness context:\nA 25-year-old sales analyst at a consumer goods company headquartered in Singapore needs to prepare a monthly report showing sales performance across Southeast Asia regions (Singapore, Malaysia, Indonesia, Thailand, Vietnam). The company uses this to adjust regional marketing budgets.\n\nDesired outcome:\nCreate a region-wise sales performance report.\n\nMy details:\n- Sales Performance Report by Region details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly sales data by region\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":435,"title":"Startup Burn Rate & Runway Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create a burn rate and runway report for a startup. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Startup Burn Rate & Runway Report\"\n\nStarting brief:\nYou are a startup finance analyst. Prepare a burn rate and runway calculation.\n\nBusiness context:\nA 27-year-old startup founder based at one-north Singapore needs to present the company's financial health to potential investors. She wants a burn rate (monthly net cash outflow) and runway (months before funds run out) calculation based on current expenses and bank balance.\n\nDesired outcome:\nCreate a burn rate and runway report for a startup.\n\nMy details:\n- Startup Burn Rate & Runway Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Last 6 months' expense data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":436,"title":"Balance Sheet Template for SMEs","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Provide a clean, SME-friendly balance sheet template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Balance Sheet Template for SMEs\"\n\nStarting brief:\nYou are an accounting documentation expert. Create a balance sheet template for SMEs.\n\nBusiness context:\nA 32-year-old owner of a small textile manufacturing unit in Tuas, Singapore needs a professional balance sheet format for bank loan applications. His current records are handwritten and lack standard accounting presentation.\n\nDesired outcome:\nProvide a clean, SME-friendly balance sheet template.\n\nMy details:\n- Balance Sheet Template for SMEs details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Asset and liability lists with values\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":437,"title":"Expense Claim Reimbursement Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare an expense claim reimbursement report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Expense Claim Reimbursement Report\"\n\nStarting brief:\nYou are a corporate HR accountant. Create a monthly employee expense reimbursement report.\n\nBusiness context:\nA 26-year-old HR coordinator in Singapore needs to submit a monthly reimbursement report for employee travel, meals, and office purchases. The finance department requires itemized claims with approval status.\n\nDesired outcome:\nPrepare an expense claim reimbursement report.\n\nMy details:\n- Expense Claim Reimbursement Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Employee expense claim data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":438,"title":"Inventory Valuation Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Advanced","explanation":"Prepare a weighted average cost inventory valuation report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Inventory Valuation Report\"\n\nStarting brief:\nYou are a supply chain finance specialist. Create a quarterly inventory valuation report.\n\nBusiness context:\nA 29-year-old warehouse manager in Tuas, Singapore needs a quarterly inventory valuation for the finance team using the weighted average cost method. This helps determine accurate COGS and year-end stock value for reporting.\n\nDesired outcome:\nPrepare a weighted average cost inventory valuation report.\n\nMy details:\n- Inventory Valuation Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase and sales records\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":439,"title":"Loan Repayment Schedule Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a loan repayment schedule report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Loan Repayment Schedule Report\"\n\nStarting brief:\nYou are a loan accounting expert. Create a loan repayment schedule.\n\nBusiness context:\nA 30-year-old business owner in Singapore has taken multiple loans for equipment purchases. The bank requires a detailed loan repayment schedule showing principal, interest, and outstanding balance each month.\n\nDesired outcome:\nPrepare a loan repayment schedule report.\n\nMy details:\n- Loan Repayment Schedule Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Loan amount\n- tenure\n- and interest rate\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":440,"title":"Profitability Report by Product Line","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a product-line profitability report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Profitability Report by Product Line\"\n\nStarting brief:\nYou are a product finance analyst. Prepare a profitability report for each product line.\n\nBusiness context:\nA 28-year-old FMCG entrepreneur in Singapore sells snacks, beverages, and condiments through supermarkets and online channels. She wants to see which product line has the highest gross and net profitability so she can focus marketing efforts accordingly.\n\nDesired outcome:\nPrepare a product-line profitability report.\n\nMy details:\n- Profitability Report by Product Line details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales data by product line\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":441,"title":"Monthly Management Report for SMEs","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create a monthly management report combining financial and operational KPIs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Monthly Management Report for SMEs\"\n\nStarting brief:\nYou are an SME performance analyst. Prepare a monthly management report.\n\nBusiness context:\nA 33-year-old owner of a 50-employee packaging company based in Tuas wants a monthly management report that summarises the company's performance in a way that's easy to discuss with his leadership team. He wants a mix of financial and operational KPIs, such as revenue, expenses, production volumes, and order fulfilment rates, in a single document that is clear enough for non-finance managers to understand.\n\nDesired outcome:\nCreate a monthly management report combining financial and operational KPIs.\n\nMy details:\n- Monthly Management Report for SMEs details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly sales and expense data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":442,"title":"Fund Utilization Report for Grant Funded Projects","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a quarterly fund utilization report for a grant project. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Fund Utilization Report for Grant Funded Projects\"\n\nStarting brief:\nYou are a charity finance officer. Create a quarterly fund utilization report.\n\nBusiness context:\nA 29-year-old project coordinator at a Singapore-based charity (IPC-registered) has received a S$400,000 grant from Tote Board for a year-long education project. The donor requires quarterly fund utilisation reports showing how much money was spent, in which categories, and how much remains unspent. The format must be transparent and audit-friendly.\n\nDesired outcome:\nPrepare a quarterly fund utilization report for a grant project.\n\nMy details:\n- Fund Utilization Report for Grant Funded Projects details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Grant agreement details\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":443,"title":"Year End Financial Summary for Investors","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Advanced","explanation":"Create a year-end financial performance summary. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Year End Financial Summary for Investors\"\n\nStarting brief:\nYou are a startup investor relations analyst. Prepare an annual financial summary.\n\nBusiness context:\nA 31-year-old founder of an agri-tech startup based in one-north, Singapore needs to send an annual financial summary to existing investors. The report should show key numbers, growth vs. last year, and future projections, while maintaining a clean, professional look for investor confidence.\n\nDesired outcome:\nCreate a year-end financial performance summary.\n\nMy details:\n- Year End Financial Summary for Investors details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual P&L\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":444,"title":"Break Even Analysis Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Calculate break-even point in units and revenue. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Break Even Analysis Report\"\n\nStarting brief:\nYou are a business finance analyst. Prepare a break-even analysis report.\n\nBusiness context:\nA 25-year-old entrepreneur in Singapore is launching a handcrafted jewellery line. She needs a break-even analysis to know how many units she must sell to cover fixed and variable costs. This will guide pricing and marketing spend decisions.\n\nDesired outcome:\nCalculate break-even point in units and revenue.\n\nMy details:\n- Break Even Analysis Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Fixed cost details\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":445,"title":"Comparative Financial Statements","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Create comparative P&L statements for three years. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Comparative Financial Statements\"\n\nStarting brief:\nYou are a corporate reporting analyst. Prepare comparative P&L statements for 3 years.\n\nBusiness context:\nA 34-year-old finance head at a chain of gyms headquartered in Singapore wants side-by-side P&L statements for the last three years to show financial trends during the annual board meeting. The focus is on identifying cost control areas and revenue growth opportunities.\n\nDesired outcome:\nCreate comparative P&L statements for three years.\n\nMy details:\n- Comparative Financial Statements details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- P&L statements for the last 3 years\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":446,"title":"Cost Centre Report for Multi Branch Company","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a branch-wise cost centre report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Cost Centre Report for Multi Branch Company\"\n\nStarting brief:\nYou are a retail finance analyst. Create a monthly cost centre report.\n\nBusiness context:\nA 30-year-old finance manager at a retail chain with stores across Singapore (Orchard, Jurong, Tampines, VivoCity, and Bugis) needs to prepare monthly reports for each store location (cost centre). The head office wants to know which locations are profitable and which are running at a loss.\n\nDesired outcome:\nPrepare a branch-wise cost centre report.\n\nMy details:\n- Cost Centre Report for Multi Branch Company details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales and expense data by branch\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":447,"title":"Expense Ratio Analysis for Mutual Fund House","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare an expense ratio analysis report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Expense Ratio Analysis for Mutual Fund House\"\n\nStarting brief:\nYou are a unit trust reporting analyst. Prepare an expense ratio analysis by fund category.\n\nBusiness context:\nA 28-year-old performance analyst at an asset management firm in Singapore's CBD wants to analyse operating expense ratios for different unit trust categories to ensure they are competitive with industry averages tracked by MAS and Morningstar.\n\nDesired outcome:\nPrepare an expense ratio analysis report.\n\nMy details:\n- Expense Ratio Analysis for Mutual Fund House details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Fund NAV and expense data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":448,"title":"Monthly Sales & Expense Consolidated Report","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a consolidated monthly sales and expense report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Monthly Sales & Expense Consolidated Report\"\n\nStarting brief:\nYou are a multi-business finance analyst. Prepare a monthly consolidated report.\n\nBusiness context:\nA 27-year-old entrepreneur in Singapore runs two separate businesses — a café in Tiong Bahru and an online bakery delivering across the island. She wants a consolidated monthly report combining sales and expenses for both ventures to get a single profitability view.\n\nDesired outcome:\nPrepare a consolidated monthly sales and expense report.\n\nMy details:\n- Monthly Sales & Expense Consolidated Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly sales and expense data for both businesses\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":449,"title":"Variance Analysis for Manufacturing Costs","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Intermediate","explanation":"Prepare a manufacturing cost variance report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Variance Analysis for Manufacturing Costs\"\n\nStarting brief:\nYou are a manufacturing cost analyst. Prepare a quarterly variance report.\n\nBusiness context:\nA 32-year-old production head at a chemical manufacturing plant on Jurong Island wants to analyse the difference between standard cost estimates and actual manufacturing costs for the quarter. This helps in improving cost control measures.\n\nDesired outcome:\nPrepare a manufacturing cost variance report.\n\nMy details:\n- Variance Analysis for Manufacturing Costs details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Standard cost sheet\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":450,"title":"Annual Compliance Reporting Template","category":"Finance & Ops","source":"Finance","module":"Financial reporting templates","difficulty":"Advanced","explanation":"Create a structured compliance and performance annual report template. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual Compliance Reporting Template\"\n\nStarting brief:\nYou are a corporate governance reporting expert. Create an annual compliance and performance report template.\n\nBusiness context:\nA 29-year-old compliance officer at a fintech company headquartered in Singapore needs an annual report format that includes financial performance, compliance activities, and statutory audit summaries for submission to MAS and other regulators.\n\nDesired outcome:\nCreate a structured compliance and performance annual report template.\n\nMy details:\n- Annual Compliance Reporting Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual financial statements\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":451,"title":"Diversification Review for a Young Investor","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Evaluate the diversification of the portfolio and provide sector/asset allocation recommendations. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Diversification Review for a Young Investor\"\n\nStarting brief:\nYou are a MAS-licensed investment advisor. Review the investor's portfolio for diversification across asset classes, sectors, and geographies.\n\nBusiness context:\nYou are assisting a 29-year-old IT professional from Singapore who started investing 5 years ago. His portfolio includes a mix of SGX-listed equities, unit trusts, and a small allocation to gold ETFs. With the recent market volatility, he's unsure if his investments are well-diversified or too concentrated in certain sectors like tech and banking. He wants a clear analysis of his holdings to check if he's managing risk effectively and how he can rebalance for stability.\n\nDesired outcome:\nEvaluate the diversification of the portfolio and provide sector/asset allocation recommendations.\n\nMy details:\n- Diversification Review for a Young Investor details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of current holdings with quantities and purchase prices\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":452,"title":"Mutual Fund Performance Tracker","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Analyze mutual fund performance and recommend corrective actions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Mutual Fund Performance Tracker\"\n\nStarting brief:\nYou are a unit trust analyst. Review the investor's fund portfolio.\n\nBusiness context:\nYou are working with a 32-year-old marketing professional from Singapore who has invested in 8 different unit trusts over the past 3 years through her bank's wealth platform. She regularly adds monthly RSP (Regular Savings Plan) contributions but has never compared their performance against benchmarks or peers. With inflation rising, she wants to know which funds are underperforming and if she should stop or switch her RSPs.\n\nDesired outcome:\nAnalyze mutual fund performance and recommend corrective actions.\n\nMy details:\n- Mutual Fund Performance Tracker details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Fund names and codes\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":453,"title":"Risk Return Analysis of Stock Portfolio","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Calculate and interpret portfolio risk and return metrics. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Risk Return Analysis of Stock Portfolio\"\n\nStarting brief:\nYou are an equity research analyst. Analyze the stock portfolio's historical performance.\n\nBusiness context:\nA 26-year-old engineer from Singapore started direct stock investing during the pandemic and now holds 15 stocks listed on SGX and US exchanges, mostly in mid-cap companies. His returns look impressive, but he suspects the portfolio is riskier than he can handle, especially as he plans to use the money for an HDB BTO down payment in 4 years. He wants a clear view of the portfolio's volatility and whether his returns justify the risks.\n\nDesired outcome:\nCalculate and interpret portfolio risk and return metrics.\n\nMy details:\n- Risk Return Analysis of Stock Portfolio details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Stock holdings with purchase dates and prices\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":454,"title":"Portfolio Stress Test Under Market Crash","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Advanced","explanation":"Simulate a portfolio's performance during a sharp market downturn. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Portfolio Stress Test Under Market Crash\"\n\nStarting brief:\nYou are a financial risk analyst. Perform a stress test on the portfolio to model a 30% equity market drop.\n\nBusiness context:\nYou're working with a 30-year-old business analyst in Singapore who has a S$200,000 portfolio split between equity unit trusts, large-cap stocks, and S-REITs. After hearing about the 2020 COVID market crash, he's anxious about how his portfolio would perform in a sudden 25–30% market fall. He wants to see simulated outcomes and understand if he needs more defensive assets to protect his capital.\n\nDesired outcome:\nSimulate a portfolio's performance during a sharp market downturn.\n\nMy details:\n- Portfolio Stress Test Under Market Crash details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current holdings with market values\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":455,"title":"SIP Portfolio Future Value Projection","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Project future value of an RSP portfolio under multiple return scenarios. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"SIP Portfolio Future Value Projection\"\n\nStarting brief:\nYou are a personal finance planner. Calculate future value of the RSP portfolio under 3 return scenarios (8%, 10%, 12%).\n\nBusiness context:\nA 28-year-old software developer from Singapore invests S$1,500 monthly via a Regular Savings Plan (RSP) into equity unit trusts and wants to see how much she could accumulate in 15 years. She also wants to check how different return assumptions (8%, 10%, 12%) change the final amount.\n\nDesired outcome:\nProject future value of an RSP portfolio under multiple return scenarios.\n\nMy details:\n- SIP Portfolio Future Value Projection details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly RSP amount\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":456,"title":"ESG Portfolio Assessment","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Advanced","explanation":"Assess portfolio for ESG compliance and suggest improvements. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"ESG Portfolio Assessment\"\n\nStarting brief:\nYou are an ESG investment analyst. Review the portfolio holdings and assign ESG ratings (high, medium, low) using available data.\n\nBusiness context:\nA 31-year-old HR manager in Singapore wants her investments to be environmentally and socially responsible. She has a mix of SGX-listed stocks, unit trusts on the Singapore platform, and some US/global ETFs, but isn't sure how ESG-friendly they are. She wants an evaluation of her portfolio based on ESG scores.\n\nDesired outcome:\nAssess portfolio for ESG compliance and suggest improvements.\n\nMy details:\n- ESG Portfolio Assessment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of holdings with ticker/codes\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":457,"title":"Portfolio Overlap Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Identify duplicate stock holdings across multiple funds. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Portfolio Overlap Analysis\"\n\nStarting brief:\nYou are a unit trust data analyst. Perform an overlap analysis across all holdings.\n\nBusiness context:\nA 25-year-old content creator based in Singapore has invested in 6 unit trusts and suspects they might be holding the same stocks. This could lead to over-concentration in certain companies and reduce diversification benefits. She wants to know the degree of portfolio overlap.\n\nDesired outcome:\nIdentify duplicate stock holdings across multiple funds.\n\nMy details:\n- Portfolio Overlap Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of unit trusts in portfolio\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":458,"title":"Sector Rotation Strategy Review","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Evaluate effectiveness of past sector rotation strategy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Sector Rotation Strategy Review\"\n\nStarting brief:\nYou are an equity strategist. Compare past sector allocation returns against the Straits Times Index (STI).\n\nBusiness context:\nA 33-year-old entrepreneur in Singapore actively rotates sectors based on market trends (tech, banks, REITs). He wants a review of his last 3 years' performance versus simply staying invested in a broad index.\n\nDesired outcome:\nEvaluate effectiveness of past sector rotation strategy.\n\nMy details:\n- Sector Rotation Strategy Review details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical sector allocation data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":459,"title":"Asset Allocation Rebalancing Plan","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Create a tax-efficient rebalancing plan to restore target allocation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Asset Allocation Rebalancing Plan\"\n\nStarting brief:\nYou are a portfolio rebalancing advisor. Suggest steps to move from current allocation to target 70/20/10 mix.\n\nBusiness context:\nA 29-year-old finance manager in Singapore targets 70% equity, 20% bonds, and 10% gold allocation. After 2 years of market rallies, his equity allocation has grown to 82%, creating excess exposure to market volatility. He wants a plan to rebalance without triggering large tax liabilities.\n\nDesired outcome:\nCreate a tax-efficient rebalancing plan to restore target allocation.\n\nMy details:\n- Asset Allocation Rebalancing Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current portfolio value by asset class\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":460,"title":"Real Estate vs. Equity Portfolio Contribution","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Advanced","explanation":"Compare performance of real estate and equity holdings. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Real Estate vs. Equity Portfolio Contribution\"\n\nStarting brief:\nYou are a wealth analyst. Calculate and compare total returns from real estate and equity investments over the given period.\n\nBusiness context:\nA 34-year-old architect in Singapore has both a rental condo and an equity portfolio. He wants to know which investment has contributed more to his net worth over the last 5 years, factoring in rental income, price appreciation, dividends, and capital gains.\n\nDesired outcome:\nCompare performance of real estate and equity holdings.\n\nMy details:\n- Real Estate vs. Equity Portfolio Contribution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase price and date for property\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":461,"title":"Dividend Income Forecast","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Advanced","explanation":"Project the expected annual dividend income and payout schedule. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Dividend Income Forecast\"\n\nStarting brief:\nYou are an equity income analyst. Forecast dividend income for the portfolio.\n\nBusiness context:\nA 28-year-old marketing executive in Singapore has gradually built a portfolio of dividend-paying stocks and S-REITs worth around S$15,000. She enjoys receiving passive income but has no clear estimate of how much she can expect over the next 12 months. She wants a forecast that accounts for past dividend trends, announced payouts, and possible changes due to market conditions.\n\nDesired outcome:\nProject the expected annual dividend income and payout schedule.\n\nMy details:\n- Dividend Income Forecast details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of holdings with quantities\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":462,"title":"Inflation Adjusted Return Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Calculate portfolio returns adjusted for inflation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Inflation Adjusted Return Analysis\"\n\nStarting brief:\nYou are a financial analyst. Calculate the portfolio's real annualized return over the given period.\n\nBusiness context:\nA 31-year-old product manager in Singapore is proud of his portfolio returns but realizes inflation might be eroding real gains. Over the last 5 years, his equity and bond investments have earned an average of 7% annually, but Singapore CPI inflation has averaged around 3%. He wants to see his real returns to evaluate true wealth growth.\n\nDesired outcome:\nCalculate portfolio returns adjusted for inflation.\n\nMy details:\n- Inflation Adjusted Return Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical portfolio value by year\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":463,"title":"Portfolio Liquidity Assessment","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Evaluate liquidity of each investment in the portfolio. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Portfolio Liquidity Assessment\"\n\nStarting brief:\nYou are a wealth planner. Assess liquidity for each portfolio component.\n\nBusiness context:\nA 25-year-old MBA student in Singapore holds a mix of CPF Special Account, CPF Investment Scheme, SRS contributions, and equity unit trusts. She plans to start her own business in 3 years and needs to know how quickly she can liquidate her investments if required.\n\nDesired outcome:\nEvaluate liquidity of each investment in the portfolio.\n\nMy details:\n- Portfolio Liquidity Assessment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Full list of investments with start dates\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":464,"title":"RSP Step Up Impact Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Project future value of step-up RSP strategy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"RSP Step Up Impact Analysis\"\n\nStarting brief:\nYou are a unit trust planner. Compare corpus from a fixed RSP vs. 10% annual step-up RSP over 20 years.\n\nBusiness context:\nA 27-year-old banker in Singapore invests S$500/month through a Regular Savings Plan (RSP) into ETFs and unit trusts, and plans to increase contributions by 10% each year as his salary grows. He wants to know the impact of this step-up strategy over 20 years compared to keeping RSP amounts fixed.\n\nDesired outcome:\nProject future value of step-up RSP strategy.\n\nMy details:\n- RSP Step Up Impact Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Base RSP amount\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":465,"title":"Currency Risk Analysis for Global Investments","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Assess portfolio's currency risk exposure. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Currency Risk Analysis for Global Investments\"\n\nStarting brief:\nYou are a forex investment analyst. Analyze currency risk for global holdings.\n\nBusiness context:\nA 34-year-old fashion designer in Singapore has invested in US ETFs and global unit trusts. She's concerned about the effect of SGD/USD movements on her returns, especially as she plans to use the funds locally in Singapore.\n\nDesired outcome:\nAssess portfolio's currency risk exposure.\n\nMy details:\n- Currency Risk Analysis for Global Investments details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of global holdings with currencies\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":466,"title":"Tax Efficiency Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Analyze portfolio for tax efficiency and suggest improvements. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Tax Efficiency Analysis\"\n\nStarting brief:\nYou are a tax-focused investment advisor. Review portfolio returns and tax impact.\n\nBusiness context:\nA 30-year-old chartered accountant in Singapore has investments in equities, bond funds, and fixed deposits. He wants to understand how much tax he is paying on his returns and whether he can improve post-tax gains through tax-efficient instruments.\n\nDesired outcome:\nAnalyze portfolio for tax efficiency and suggest improvements.\n\nMy details:\n- Tax Efficiency Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Investment type\n- holding period\n- returns\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":467,"title":"Historical Drawdown Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Identify maximum historical drawdowns and recovery times. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Historical Drawdown Analysis\"\n\nStarting brief:\nYou are a market risk analyst. Calculate max drawdown for the portfolio over last 10 years.\n\nBusiness context:\nA 26-year-old civil engineer in Singapore wants to see how much his portfolio value could drop in extreme market conditions, based on historical price movements of his holdings over the last 10 years.\n\nDesired outcome:\nIdentify maximum historical drawdowns and recovery times.\n\nMy details:\n- Historical Drawdown Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Historical price data for holdings\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":468,"title":"Portfolio Alignment with Goals","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Match investments to specific life goals. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Portfolio Alignment with Goals\"\n\nStarting brief:\nYou are a goal-based financial planner. Align portfolio with stated financial goals.\n\nBusiness context:\nA 32-year-old lawyer in Singapore has 3 major goals — buying a condo in 5 years, child's university education in 15 years, and retirement in 30 years. She wants to know if her current portfolio allocation supports these timelines.\n\nDesired outcome:\nMatch investments to specific life goals.\n\nMy details:\n- Portfolio Alignment with Goals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current portfolio details\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":469,"title":"Portfolio Cost Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Calculate and summarize portfolio costs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Portfolio Cost Analysis\"\n\nStarting brief:\nYou are a cost-efficiency analyst. Review portfolio for annual costs.\n\nBusiness context:\nA 28-year-old entrepreneur in Singapore suspects that high expense ratio unit trusts and frequent stock trades are eating into his returns. He wants to quantify total annual portfolio costs.\n\nDesired outcome:\nCalculate and summarize portfolio costs.\n\nMy details:\n- Portfolio Cost Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of unit trusts and expense ratios\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":470,"title":"Portfolio Concentration Risk Report","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Assess and visualize portfolio concentration risk. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Portfolio Concentration Risk Report\"\n\nStarting brief:\nYou are a portfolio risk analyst. Create a report showing % allocation to top holdings.\n\nBusiness context:\nA 30-year-old mechanical engineer in Singapore holds 70% of his equity investments in just 3 companies. He wants to understand the risk of such concentration and its effect on volatility.\n\nDesired outcome:\nAssess and visualize portfolio concentration risk.\n\nMy details:\n- Portfolio Concentration Risk Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Portfolio holdings and values\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":471,"title":"Factor Based Portfolio Analysis","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Identify factor exposure of the portfolio. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Factor Based Portfolio Analysis\"\n\nStarting brief:\nYou are a quant analyst. Map portfolio to factor exposures.\n\nBusiness context:\nA 34-year-old fund enthusiast in Singapore follows factor investing (value, momentum, low volatility) but isn't sure which factors his portfolio is tilted towards.\n\nDesired outcome:\nIdentify factor exposure of the portfolio.\n\nMy details:\n- Factor Based Portfolio Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of stocks and weights\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":472,"title":"Retirement Corpus Projection","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Project retirement corpus and identify gaps. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Retirement Corpus Projection\"\n\nStarting brief:\nYou are a retirement planner. Project corpus at retirement age based on current portfolio and contributions.\n\nBusiness context:\nA 29-year-old architect in Singapore wants to retire at 55. She invests in unit trusts and makes voluntary CPF contributions, but isn't sure if her current pace will meet her desired lifestyle.\n\nDesired outcome:\nProject retirement corpus and identify gaps.\n\nMy details:\n- Retirement Corpus Projection details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current portfolio value\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":473,"title":"Reinvestment Strategy for Maturity Proceeds","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Suggest reinvestment options based on risk profile. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Reinvestment Strategy for Maturity Proceeds\"\n\nStarting brief:\nYou are a personal investment consultant. Recommend reinvestment options for maturity proceeds.\n\nBusiness context:\nA 31-year-old dentist in Singapore has a fixed deposit maturing next month and wants to reinvest the amount to improve returns without taking excessive risk.\n\nDesired outcome:\nSuggest reinvestment options based on risk profile.\n\nMy details:\n- Reinvestment Strategy for Maturity Proceeds details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Maturity amount\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":474,"title":"Goal Based SIP Allocation","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Allocate monthly RSP amounts to each goal for optimal growth. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Goal Based SIP Allocation\"\n\nStarting brief:\nYou are an RSP allocation planner. Suggest fund types and amounts for each goal.\n\nBusiness context:\nA 25-year-old fresh graduate working in Singapore wants to start 3 regular savings plans (RSPs) for different goals — a motorbike or COE-supported car downpayment in 3 years, a master's degree in 5 years, and an HDB BTO downpayment in 10 years.\n\nDesired outcome:\nAllocate monthly RSP amounts to each goal for optimal growth.\n\nMy details:\n- Goal Based SIP Allocation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Goal timelines and cost estimates\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":475,"title":"Annual Portfolio Review Report","category":"Finance & Ops","source":"Finance","module":"Investment portfolio analysis","difficulty":"Intermediate","explanation":"Create a comprehensive annual portfolio review. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual Portfolio Review Report\"\n\nStarting brief:\nYou are a portfolio manager. Prepare a full-year review of the portfolio.\n\nBusiness context:\nA 33-year-old finance professional in Singapore makes ad-hoc investments but has never done a full portfolio review. He wants an annual summary that covers performance, asset allocation, risks, and recommendations.\n\nDesired outcome:\nCreate a comprehensive annual portfolio review.\n\nMy details:\n- Annual Portfolio Review Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Portfolio holdings with purchase data\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":476,"title":"Annual Tax Saving Plan for Salaried Employee","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Prepare a personalised tax-saving plan using IRAS-recognised reliefs and deductions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual Tax Saving Plan for Salaried Employee\"\n\nStarting brief:\nYou are a tax consultant. Design a 12-month tax-saving plan for a salaried professional in Singapore.\n\nBusiness context:\nYou are working with a 29-year-old software engineer based in one-north, Singapore, earning S$110,000 per annum. His package includes base salary, AWS, and performance bonuses. While CPF contributions are deducted, he has not fully utilised reliefs such as SRS, CPF top-ups, course fees, or NSman relief. He wants a complete annual tax-saving plan that minimises his liability without risky investments.\n\nDesired outcome:\nPrepare a personalised tax-saving plan using IRAS-recognised reliefs and deductions.\n\nMy details:\n- Annual Tax Saving Plan for Salaried Employee details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Salary breakdown with allowances and bonus\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":477,"title":"GST Return Filing Checklist","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a step-by-step GST F5 return filing checklist. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Return Filing Checklist\"\n\nStarting brief:\nYou are a GST compliance expert. Create a checklist for accurate quarterly GST F5 filing in Singapore.\n\nBusiness context:\nA 32-year-old small business owner in Singapore runs a boutique selling clothes both at a Tampines shopfront and through Instagram. She is GST registered and files quarterly F5 returns but often misses claiming input tax because supplier tax invoices aren't properly tracked. She needs a clear pre-filing checklist to avoid errors.\n\nDesired outcome:\nCreate a step-by-step GST F5 return filing checklist.\n\nMy details:\n- GST Return Filing Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- GST registration number of the business\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":478,"title":"Estimated Tax Calculation for Freelancers","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Prepare an estimated tax provisioning schedule with set-aside amounts and IRAS-aligned milestones. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Estimated Tax Calculation for Freelancers\"\n\nStarting brief:\nYou are a tax advisor. Calculate quarterly estimated tax provisioning for a self-employed person in Singapore based on projected income.\n\nBusiness context:\nA 27-year-old freelance content writer based in Singapore earns income from local clients via PayNow and bank transfers and from foreign clients via PayPal and Wise. Her income is irregular, and she often forgets to set aside funds for her annual income tax, leading to cashflow stress when the IRAS Notice of Assessment arrives. She wants a quarterly estimated tax provisioning plan based on projected earnings.\n\nDesired outcome:\nPrepare an estimated tax provisioning schedule with set-aside amounts and IRAS-aligned milestones.\n\nMy details:\n- Estimated Tax Calculation for Freelancers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Estimated annual income split by quarter\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":479,"title":"Comparing Tax Reliefs vs. Standard Filing","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Help compare tax outcomes with full relief optimisation vs. minimal reliefs to choose what saves the most after factoring liquidity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Comparing Tax Reliefs vs. Standard Filing\"\n\nStarting brief:\nYou are a tax planner. Compare tax outcomes for a Singapore tax resident with full relief optimisation vs. minimal reliefs.\n\nBusiness context:\nA 30-year-old corporate lawyer in Singapore earns S$180,000 per annum and has investments in SRS, voluntary CPF top-ups, and a term life policy. She is unsure whether the time and lock-in cost of fully maxing out reliefs (SRS, CPF top-ups, course fees, parent relief) really beats simply paying tax under the standard resident rates. She wants a side-by-side comparison of her tax liability with vs. without optimised reliefs, considering everything she is eligible for.\n\nDesired outcome:\nHelp compare tax outcomes with full relief optimisation vs. minimal reliefs to choose what saves the most after factoring liquidity.\n\nMy details:\n- Comparing Tax Reliefs vs. Standard Filing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Salary breakdown and other income sources\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":480,"title":"GST Input Tax Maximisation Plan","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a process to ensure maximum GST input tax claims under IRAS rules. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Input Tax Maximisation Plan\"\n\nStarting brief:\nYou are a GST specialist. Create a quarterly input tax maximisation plan for a Singapore GST-registered business.\n\nBusiness context:\nA 28-year-old e-commerce seller in Singapore is GST registered but claims less input tax than possible because many supplier tax invoices are missing or do not meet IRAS' tax invoice requirements. She wants a system to track and maximise input tax claims every quarter.\n\nDesired outcome:\nCreate a process to ensure maximum GST input tax claims under IRAS rules.\n\nMy details:\n- GST Input Tax Maximisation Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Supplier list with GST registration numbers\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":481,"title":"Rental Expense & Housing Benefit Tax Treatment Calculator","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Calculate the taxable value of housing benefits and any allowable deductions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Rental Expense & Housing Benefit Tax Treatment Calculator\"\n\nStarting brief:\nYou are a payroll tax expert. Calculate the taxable housing benefit and any allowable deductions per IRAS rules.\n\nBusiness context:\nA 27-year-old IT professional in Singapore pays S$2,500/month renting a room in a condo near her one-north office. Her employer reimburses part of her rent as a housing allowance. She wants to understand how the rental reimbursement is taxed under IRAS rules and whether she can claim any deductions against it.\n\nDesired outcome:\nCalculate the taxable value of housing benefits and any allowable deductions.\n\nMy details:\n- Rental Expense & Housing Benefit Tax Treatment Calculator details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly base salary\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":482,"title":"Late GST Filing Penalty Estimator","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Calculate GST late submission penalty, surcharge, and interest charges per IRAS rules. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Late GST Filing Penalty Estimator\"\n\nStarting brief:\nYou are a GST compliance calculator. Estimate late submission penalty, 5% surcharge, and additional 2% per month penalty for delayed GST F5 filing in Singapore.\n\nBusiness context:\nA 33-year-old small business owner in Singapore missed filing her GST F5 return for two consecutive quarters due to personal emergencies. She wants to know the exact late submission penalty, 5% surcharge, and additional interest payable before submitting.\n\nDesired outcome:\nCalculate GST late submission penalty, surcharge, and interest charges per IRAS rules.\n\nMy details:\n- Late GST Filing Penalty Estimator details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Filing frequency (quarterly/monthly)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":483,"title":"Freelance Income Tax Filing Template","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a ready-to-use income tax filing template for self-employed persons in Singapore. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Freelance Income Tax Filing Template\"\n\nStarting brief:\nYou are a tax documentation expert. Create an Excel template for self-employed Form B income tax filing aligned to IRAS requirements.\n\nBusiness context:\nA 26-year-old freelance videographer in Singapore earns from both local and international clients. She needs a simple, pre-filled Excel template to record her earnings, expenses, withholding tax (where applicable), and foreign remittances to make her annual Form B filing with IRAS easier.\n\nDesired outcome:\nCreate a ready-to-use income tax filing template for self-employed persons in Singapore.\n\nMy details:\n- Freelance Income Tax Filing Template details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Nature of freelance work (SSIC-aligned)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":484,"title":"InvoiceNow / GST E invoice Implementation Guide","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Provide a step-by-step InvoiceNow / GST e-invoicing implementation guide. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"InvoiceNow / GST E invoice Implementation Guide\"\n\nStarting brief:\nYou are a GST and e-invoicing technology consultant. Create a step-by-step process to implement InvoiceNow (Peppol) e-invoicing for a Singapore GST-registered business.\n\nBusiness context:\nA 30-year-old wholesale distributor in Singapore has crossed S$1 million in annual taxable turnover and is preparing for the IMDA InvoiceNow (Peppol) requirement that IRAS is rolling out for GST-registered businesses. He has no idea how to integrate the network with his current billing software.\n\nDesired outcome:\nProvide a step-by-step InvoiceNow / GST e-invoicing implementation guide.\n\nMy details:\n- InvoiceNow / GST E invoice Implementation Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Billing software details (e.g. Xero, SAP B1\n- NetSuite\n- Quickbooks)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":485,"title":"Tax Provisioning & Reminder System","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Set up an automated tax provisioning, GIRO instalment, and reminder plan. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Tax Provisioning & Reminder System\"\n\nStarting brief:\nYou are a financial automation consultant. Design a reminder system for income tax provisioning and GIRO instalment payments in Singapore.\n\nBusiness context:\nA 34-year-old self-employed interior designer in Singapore often forgets to set aside funds for her annual income tax and GIRO instalments, leading to cashflow strain when the IRAS Notice of Assessment arrives. She wants a system that sends her reminders and pre-calculates each set-aside based on updated income estimates.\n\nDesired outcome:\nSet up an automated tax provisioning, GIRO instalment, and reminder plan.\n\nMy details:\n- Tax Provisioning & Reminder System details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Estimated annual income pattern\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":486,"title":"Health Insurance & MediShield Tax Relief Calculator","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Calculate maximum reliefs claimable for health/life insurance and dependant care under IRAS rules. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Health Insurance & MediShield Tax Relief Calculator\"\n\nStarting brief:\nYou are a personal tax planner. Calculate reliefs claimable for health and life insurance premiums and dependant care for a Singapore tax resident.\n\nBusiness context:\nA 28-year-old teacher in Singapore has bought an Integrated Shield Plan rider for herself and is paying premiums on a private hospitalisation policy for her parents. She is unsure how much tax relief she can claim through her CPF MediSave deductions, life insurance relief, and parent relief.\n\nDesired outcome:\nCalculate maximum reliefs claimable for health/life insurance and dependant care under IRAS rules.\n\nMy details:\n- Health Insurance & MediShield Tax Relief Calculator details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Premium amounts and insured persons\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":487,"title":"Annual GST Reconciliation & Year End Preparation Plan","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a year-end GST reconciliation and Assisted Self-help Kit (ASK) review checklist. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Annual GST Reconciliation & Year End Preparation Plan\"\n\nStarting brief:\nYou are a GST return expert. Create a step-by-step year-end GST reconciliation checklist for a Singapore GST-registered business.\n\nBusiness context:\nA 32-year-old GST-registered trader in Singapore needs to perform his first proper year-end GST reconciliation across all four F5 quarters and prepare supporting documentation in case of an IRAS GST audit or ASK self-review. He wants a clear plan to gather all documents and reconcile data before year-end close.\n\nDesired outcome:\nCreate a year-end GST reconciliation and Assisted Self-help Kit (ASK) review checklist.\n\nMy details:\n- Annual GST Reconciliation & Year End Preparation Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- GST F5 returns filed during the financial year\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":488,"title":"Investment Gains Tax Treatment Calculator","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Determine the Singapore tax treatment of each investment gain and total tax/duty payable. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Investment Gains Tax Treatment Calculator\"\n\nStarting brief:\nYou are a Singapore tax expert. Analyse the tax treatment of all investments sold and stocks/funds disposed of.\n\nBusiness context:\nA 27-year-old equity investor in Singapore has booked profits this year on SGX-listed stocks, US-listed ETFs, unit trusts, and one private property. She wants to know which gains are taxable in Singapore (which generally has no capital gains tax for individuals), how the IRAS \"badges of trade\" test might apply if her trading is frequent, and whether any gains attract Seller's Stamp Duty (SSD) or Additional Buyer's Stamp Duty (ABSD).\n\nDesired outcome:\nDetermine the Singapore tax treatment of each investment gain and total tax/duty payable.\n\nMy details:\n- Investment Gains Tax Treatment Calculator details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase and sale details for each asset\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":489,"title":"GST Reverse Charge Compliance for Imported Services","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a compliance guide for GST Reverse Charge on imported services in Singapore. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Reverse Charge Compliance for Imported Services\"\n\nStarting brief:\nYou are a GST compliance trainer. Prepare a Reverse Charge compliance guide for imported services from overseas suppliers under Singapore GST rules.\n\nBusiness context:\nA 30-year-old event manager in Singapore engages overseas artists and overseas digital service providers (e.g. lighting, livestream platforms, design contractors) for shows held locally. She wants to ensure proper GST treatment under the Reverse Charge regime that applies to GST-registered businesses receiving imported services and the Overseas Vendor Registration regime where relevant.\n\nDesired outcome:\nCreate a compliance guide for GST Reverse Charge on imported services in Singapore.\n\nMy details:\n- GST Reverse Charge Compliance for Imported Services details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Nature of imported service\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":490,"title":"Payroll Statutory Deduction Calculation (CPF & SDL)","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Calculate monthly and annual statutory payroll deductions and contributions. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Payroll Statutory Deduction Calculation (CPF & SDL)\"\n\nStarting brief:\nYou are a payroll tax advisor. Calculate monthly and annual CPF (employee + employer) and Skills Development Levy for a Singapore-employed individual.\n\nBusiness context:\nA 25-year-old designer in Singapore works for a private firm and earns S$4,500/month. She wants to understand her monthly statutory payroll deductions — employee CPF contribution — and what her employer pays on top (employer CPF and Skills Development Levy), so she can reconcile her payslip and annual IR8A.\n\nDesired outcome:\nCalculate monthly and annual statutory payroll deductions and contributions.\n\nMy details:\n- Payroll Statutory Deduction Calculation (CPF & SDL) details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Monthly salary\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":491,"title":"Tax Planning for First Time Home Buyer","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Prepare a year-wise tax and CPF benefit plan for a first-time home buyer. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Tax Planning for First Time Home Buyer\"\n\nStarting brief:\nYou are a Singapore housing loan and tax specialist. For the given home loan details, prepare a plan to maximise reliefs and CPF utilisation in the current and following years.\n\nBusiness context:\nA 30-year-old banking professional in Singapore has just booked her first private condominium unit worth S$1.2 million in the Tampines area, with a bank loan sanctioned for 75% of the value (within MAS LTV limits). She is aware that there are reliefs and grants available — including the use of CPF Ordinary Account funds for downpayment and monthly instalments, the Buyer's Stamp Duty (BSD) structure, and the property tax owner-occupier rates — but she's unsure how to optimise these in the first year since her...\n\nDesired outcome:\nPrepare a year-wise tax and CPF benefit plan for a first-time home buyer.\n\nMy details:\n- Tax Planning for First Time Home Buyer details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Loan offer letter with disbursement / instalment start date\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":492,"title":"Non Resident Tax Compliance Checklist","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a comprehensive cross-border tax compliance checklist for a Singapore tax resident / non-resident with Singapore income sources. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Non Resident Tax Compliance Checklist\"\n\nStarting brief:\nYou are a Singapore cross-border taxation consultant. Prepare a checklist for annual tax compliance for a non-resident or overseas-posted individual with Singapore income and assets.\n\nBusiness context:\nA 33-year-old software engineer who is a Singapore citizen is currently working on assignment in the United Kingdom but still has investments back home — a CPF Investment Scheme portfolio, Singapore-listed REITs and unit trusts, and a private condo in Bishan that she rents out. She files her UK taxes from abroad but often misses details about the Singapore-UK Double Taxation Agreement (DTA), repatriation of rental proceeds, and rental income reporting to IRAS. She needs a consolidated annual checklist to ensure...\n\nDesired outcome:\nCreate a comprehensive cross-border tax compliance checklist for a Singapore tax resident / non-resident with Singapore income sources.\n\nMy details:\n- Non Resident Tax Compliance Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Country of current residence and posting period\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":493,"title":"GST Compliance Calendar for Startups","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a GST and corporate tax compliance calendar tailored for Singapore startups. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Compliance Calendar for Startups\"\n\nStarting brief:\nYou are a Singapore business compliance advisor. Prepare a full-year GST and corporate income tax compliance calendar for a newly registered Singapore startup.\n\nBusiness context:\nA 26-year-old founder of a D2C skincare startup based in one-north, Singapore is newly GST-registered with IRAS and unsure about filing timelines, estimated chargeable income (ECI) due dates, and annual compliance requirements with ACRA. She needs a startup-friendly GST + corporate tax compliance calendar that her team can follow to avoid missing deadlines.\n\nDesired outcome:\nCreate a GST and corporate tax compliance calendar tailored for Singapore startups.\n\nMy details:\n- GST Compliance Calendar for Startups details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- GST filing frequency (monthly / quarterly)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":494,"title":"Property Disposal & Stamp Duty Planning","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Advise on the best strategy for redeploying property sale proceeds with minimal stamp duty leakage. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Property Disposal & Stamp Duty Planning\"\n\nStarting brief:\nYou are a Singapore property tax and stamp duty planner. Recommend the best approach for the seller to reinvest sale proceeds into a new residential property.\n\nBusiness context:\nA 32-year-old doctor in Singapore recently sold an inherited landed property and realised a substantial gain of around S$800,000. She wants to use the proceeds to purchase a new private residential property but is confused about how Seller's Stamp Duty (SSD), Buyer's Stamp Duty (BSD), and Additional Buyer's Stamp Duty (ABSD) will apply to her situation. She also wants guidance on timelines and documentation to avoid unnecessary stamp duty exposure.\n\nDesired outcome:\nAdvise on the best strategy for redeploying property sale proceeds with minimal stamp duty leakage.\n\nMy details:\n- Property Disposal & Stamp Duty Planning details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sale & Purchase agreement details (date\n- sale price)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":495,"title":"GST Registration vs Voluntary Deregistration Evaluation","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Compare staying on standard GST registration versus deregistration / alternative IRAS schemes, and suggest the best choice. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Registration vs Voluntary Deregistration Evaluation\"\n\nStarting brief:\nYou are a Singapore GST advisor. Evaluate whether continuing standard GST registration is beneficial for the business, versus deregistration or applying for an alternative IRAS scheme.\n\nBusiness context:\nA 27-year-old café owner in the Tiong Bahru area has an annual turnover of around S$1.2 million and is GST-registered. With many of his suppliers being small unregistered vendors and most of his customers being end consumers, he is unsure whether being GST-registered is still net-beneficial, or whether he should restructure operations and consider voluntary deregistration if his rolling 12-month turnover dips below the S$1 million threshold. He also wants clarity on the simplified Gross Margin Scheme and the Major...\n\nDesired outcome:\nCompare staying on standard GST registration versus deregistration / alternative IRAS schemes, and suggest the best choice.\n\nMy details:\n- GST Registration vs Voluntary Deregistration Evaluation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Annual turnover (SGD)\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":496,"title":"Charitable Donation Tax Deduction Planner","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Optimise donation amounts for maximum charitable tax deduction. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Charitable Donation Tax Deduction Planner\"\n\nStarting brief:\nYou are a Singapore charitable tax benefit consultant. For the given donations, calculate total eligible deduction and recommend an optimised giving structure.\n\nBusiness context:\nA 25-year-old corporate employee working in the Marina Bay CBD regularly donates to local charities but is unaware of how the 250% tax deduction for donations to Institutions of a Public Character (IPCs) works. She wants to know which of her donations actually qualify, how to structure giving for maximum tax benefit, and how donations interact with the Personal Income Tax Relief Cap of S$80,000.\n\nDesired outcome:\nOptimise donation amounts for maximum charitable tax deduction.\n\nMy details:\n- Charitable Donation Tax Deduction Planner details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of donations with charity name, IPC status\n- donation amount\n- and date\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":497,"title":"GST Input Tax Reconciliation Workflow","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a quarterly GST input tax reconciliation workflow. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Input Tax Reconciliation Workflow\"\n\nStarting brief:\nYou are a Singapore GST reconciliation expert. Develop a quarterly process to match input tax in the purchase register against supplier tax invoices and InvoiceNow / Peppol data.\n\nBusiness context:\nA 29-year-old electronics retailer in Singapore files GST F5 returns quarterly with IRAS but often faces input tax mismatches because suppliers issue tax invoices late, send credit notes, or fail to comply with InvoiceNow / e-invoicing requirements. She wants an automated process to reconcile input tax claimed in her accounting books with supplier tax invoices and the InvoiceNow / Peppol records before she submits each F5.\n\nDesired outcome:\nCreate a quarterly GST input tax reconciliation workflow.\n\nMy details:\n- GST Input Tax Reconciliation Workflow details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase register for the quarter\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":498,"title":"Salary Structure Optimisation for Tax Savings","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Design a tax-optimised salary structure under Singapore tax rules. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Salary Structure Optimisation for Tax Savings\"\n\nStarting brief:\nYou are a Singapore payroll tax planner. Suggest changes to remuneration components to reduce taxable income without lowering net take-home pay.\n\nBusiness context:\nA 30-year-old sales manager working in Singapore receives a fixed annual package but can request changes to remuneration components during his annual review. He wants to restructure his package to reduce taxable employment income — possibly by adjusting fixed vs variable mix, opting into the SRS (Supplementary Retirement Scheme), making voluntary CPF top-ups, and structuring eligible reimbursements (e.g. transport, mobile, professional development) — without reducing in-hand pay.\n\nDesired outcome:\nDesign a tax-optimised salary structure under Singapore tax rules.\n\nMy details:\n- Salary Structure Optimisation for Tax Savings details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current package structure with all components\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":499,"title":"GST Refund Claim for Exporters","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Guide through GST refund claims and zero-rating compliance for Singapore exporters. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"GST Refund Claim for Exporters\"\n\nStarting brief:\nYou are a Singapore GST export compliance advisor. Create a step-by-step guide to claim a refund of net input tax on zero-rated export supplies through the GST F5.\n\nBusiness context:\nA 28-year-old lifestyle goods exporter based in Singapore ships products to Europe and the US. She incurs GST on local raw material purchases but exports finished goods as zero-rated supplies under IRAS rules. She wants to claim a refund of the accumulated input tax quickly and without errors, and is also evaluating whether the Major Exporter Scheme (MES) would suit her cash-flow profile.\n\nDesired outcome:\nGuide through GST refund claims and zero-rating compliance for Singapore exporters.\n\nMy details:\n- GST Refund Claim for Exporters details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchase tax invoices with GST paid\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":500,"title":"Pre Filing Personal Tax Health Check","category":"Finance & Ops","source":"Finance","module":"Tax planning GST compliance","difficulty":"Advanced","explanation":"Create a pre-filing personal tax readiness checklist for Singapore taxpayers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a finance and operations analyst who prioritizes accuracy, controls, and business usefulness. Help me create a polished, workplace-ready output for this task:\n\"Pre Filing Personal Tax Health Check\"\n\nStarting brief:\nYou are a Singapore personal tax consultant. Prepare a pre-filing tax readiness checklist for salaried individuals filing through myTax Portal.\n\nBusiness context:\nA 33-year-old HR manager in Singapore files her personal income tax return with IRAS every April but often scrambles last minute to verify her auto-included income, donations, and reliefs, leading to missed deductions. She wants a \"tax health check\" three months before the filing deadline so she can prepare everything in advance and review her draft assessment in myTax Portal calmly.\n\nDesired outcome:\nCreate a pre-filing personal tax readiness checklist for Singapore taxpayers.\n\nMy details:\n- Pre Filing Personal Tax Health Check details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Salary structure and IR8A / employer AIS submission summary\n- period or transaction scope\n- source system or file\n- currency or unit\n- approval rules\n- known exceptions\n- period covered\n- currency\n- source data\n- assumptions\n- approval or control requirements\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. State the objective, data needed, assumptions, and control checks first.\n2. Organize calculations, reconciliations, or operational steps in a clear sequence.\n3. Highlight variance drivers, exceptions, and follow-up owners.\n4. Provide a plain-English management summary after the detailed work.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Objective and assumptions\n- Calculation or process table\n- Exceptions and variance notes\n- Control or reconciliation checklist\n- Management summary and next actions\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent figures, tax rules, policies, or approvals. Mark unverified values and recommend source checks.\n- Flag assumptions, formulas, reconciliations, control gaps, and numbers that need verification.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"💰","color":"cat-mint"},{"id":501,"title":"Connecting Multiple APIs for Unified Data","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are an API Integration Engineer with expertise in REST (Representational State Transfer) and GraphQL APIs. I want to create a single automated workflow that combines data from Google Sheets, Shopify, and Google Analytics APIs. Your task: -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Connecting Multiple APIs for Unified Data\"\n\nStarting brief:\nPrompt 1 — Connecting Multiple APIs for Unified Data \"You are an API Integration Engineer with expertise in REST (Representational State Transfer) and GraphQL APIs. I want to create a single automated workflow that combines data from Google Sheets, Shopify, and Google Analytics APIs. Your task: - Authenticate each API using OAuth 2.0 and store tokens securely. - Pull product sales data from Shopify, website traffic data from Google Analytics, and inventory data from Google Sheets. - Merge the datasets on product ID and date fields for unified reporting. - Schedule the workflow to run daily at midnight using a cron job or cloud scheduler. - Include logging for errors and success status. Output format: Python script with step-by-step API calls, merged dataset output as CSV, and instructions for deployment in a cloud environment (AWS Lambda or Google Cloud Functions).\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Connecting Multiple APIs for Unified Data details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":502,"title":"Automating Social Media Posting via API","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Social Media Automation Specialist experienced with the Meta Graph API, LinkedIn API, and Twitter API (now X API). I manage 3 platforms and want to post the same content automatically at scheduled times. Your task: - Authenticate all platform...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Social Media Posting via API\"\n\nStarting brief:\nPrompt 2 — Automating Social Media Posting via API \"You are a Social Media Automation Specialist experienced with the Meta Graph API, LinkedIn API, and Twitter API (now X API). I manage 3 platforms and want to post the same content automatically at scheduled times. Your task: - Authenticate all platform APIs and handle rate limits. - Create a reusable function that posts text, images, and videos from a single JSON file. - Add an option to customise captions per platform for optimal engagement. - Schedule posts using a job scheduler (like APScheduler in Python). - Log post IDs and engagement metrics for tracking. Output format: Python automation script + setup instructions + sample JSON template for post content.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Social Media Posting via API details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":503,"title":"Automating Data Entry from Web Forms to CRM","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a CRM Workflow Automation Engineer skilled in HubSpot, Salesforce, and Zoho CRM APIs. I receive customer leads from a website form and want them automatically added to my CRM with tags for campaign tracking. Your task: - Set up a webhook to...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Data Entry from Web Forms to CRM\"\n\nStarting brief:\nPrompt 3 — Automating Data Entry from Web Forms to CRM \"You are a CRM Workflow Automation Engineer skilled in HubSpot, Salesforce, and Zoho CRM APIs. I receive customer leads from a website form and want them automatically added to my CRM with tags for campaign tracking. Your task: - Set up a webhook to receive form submissions in real time. - Transform form data into the CRM's required JSON format. - Use the CRM API to create a new lead record with appropriate tags (e.g., \"WebForm2024\"). - Send a confirmation email to the lead using the CRM's email API. - Log each successful lead creation in a Google Sheet via API. Output format: API workflow diagram + example webhook handler code + CRM API call scripts.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Data Entry from Web Forms to CRM details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":504,"title":"Email Marketing Automation with API","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are an Email Marketing Automation Expert familiar with Mailchimp, SendGrid, and ActiveCampaign APIs. I want to send a weekly newsletter automatically using my Google Sheets contact list. Your task: - Connect Google Sheets API to read subscriber list....","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Email Marketing Automation with API\"\n\nStarting brief:\nYou are an Email Marketing Automation Expert familiar with Mailchimp, SendGrid, and ActiveCampaign APIs. I want to send a weekly newsletter automatically using my Google Sheets contact list. Your task: - Connect Google Sheets API to read subscriber list. - Connect the chosen email service API and authenticate securely. - Pull the email template from a stored HTML file. - Send emails in batches to avoid exceeding API rate limits. - Update the Google Sheet with a \"last sent\" timestamp for each contact. Output format: Python/Node.js script + deployment guide + API keys & secrets handling instructions.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Email Marketing Automation with API details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":505,"title":"Automating File Backups to Cloud Storage","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Cloud Automation Engineer skilled in AWS S3, Google Drive, and Dropbox APIs. I have a folder on my local machine containing financial reports that must be backed up daily to all three cloud platforms. Your task: - Authenticate with all three...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating File Backups to Cloud Storage\"\n\nStarting brief:\nPrompt 5 — Automating File Backups to Cloud Storage \"You are a Cloud Automation Engineer skilled in AWS S3, Google Drive, and Dropbox APIs. I have a folder on my local machine containing financial reports that must be backed up daily to all three cloud platforms. Your task: - Authenticate with all three cloud APIs. - Compress the local folder into a timestamped ZIP file. - Upload the ZIP file to each cloud platform. - Send an email notification with file URLs after successful upload. - Log the backup details in a CSV file for auditing. Output format: Shell/Python script + setup instructions + automation scheduling plan.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating File Backups to Cloud Storage details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":506,"title":"Real Time Stock Price Tracker with Alerts","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"Real-Time Stock Price Tracker with Alerts \"You are a Financial Data Automation Specialist experienced in Alpha Vantage, Yahoo Finance, and TradingView APIs. I want to track live stock prices for a watchlist of 10 SGX-listed companies (Straits Times Index...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Real Time Stock Price Tracker with Alerts\"\n\nStarting brief:\nPrompt 6 — Real-Time Stock Price Tracker with Alerts \"You are a Financial Data Automation Specialist experienced in Alpha Vantage, Yahoo Finance, and TradingView APIs. I want to track live stock prices for a watchlist of 10 SGX-listed companies (Straits Times Index constituents) and receive alerts when prices change more than ±3% in a day. Your task: - Connect to the stock price API with authentication. - Create a script to fetch and store real-time prices every 5 minutes. - Compare the current price with the opening price for percentage change. - Trigger an email/SMS alert when the ±3% threshold is crossed. - Store all intraday data in a CSV for end-of-day analysis. Output format: Python script + CSV logging + alert system integration plan. Input Files & Code Section: - API Key file (api_keys.json) for Alpha Vantage/Yahoo Finance. - watchlist.csv containing SGX ticker symbols. -...\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Real Time Stock Price Tracker with Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":507,"title":"Automating PDF Invoice Creation from Sales Data","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Document Automation Engineer skilled in ReportLab, wkhtmltopdf, and Google Docs API. I have daily sales data in CSV format and need automatically generated PDF invoices sent to customers. Your task: - Read the CSV to fetch customer details,...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating PDF Invoice Creation from Sales Data\"\n\nStarting brief:\nPrompt 7 — Automating PDF Invoice Creation from Sales Data \"You are a Document Automation Engineer skilled in ReportLab, wkhtmltopdf, and Google Docs API. I have daily sales data in CSV format and need automatically generated PDF invoices sent to customers. Your task: - Read the CSV to fetch customer details, products, and prices. - Generate a branded PDF invoice for each customer. - Save the invoice locally and in Google Drive. - Email the invoice to the customer with a personalised message. - Log invoice status (sent, pending, failed) in a Google Sheet. Output format: Python script + invoice PDF template + Google Drive integration guide. Input Files & Code Section: - sales_data.csv with customer and order details. - invoice_template.html for branding. - API credentials for Google Drive and Gmail.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating PDF Invoice Creation from Sales Data details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":508,"title":"Weather Based Automation for Agriculture","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"Weather-Based Automation for Agriculture \"You are an Agricultural IoT Automation Specialist skilled in OpenWeatherMap API and smart irrigation systems. I want to automate irrigation based on real-time weather data. Your task: - Connect to the...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Weather Based Automation for Agriculture\"\n\nStarting brief:\nPrompt 8 — Weather-Based Automation for Agriculture \"You are an Agricultural IoT Automation Specialist skilled in OpenWeatherMap API and smart irrigation systems. I want to automate irrigation based on real-time weather data. Your task: - Connect to the OpenWeatherMap API to fetch daily forecasts. - If rainfall probability is >70%, delay irrigation by 24 hours. - If temperature >35°C, schedule an extra watering cycle. - Send an SMS to the farmer confirming the decision. - Log all actions in a daily report file. Output format: IoT control script + weather API integration + action logging. Input Files & Code Section: - API key file for OpenWeatherMap. - farm_config.json with field size, crop type, and irrigation limits. Placeholder for SMS gateway integration code.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Weather Based Automation for Agriculture details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":509,"title":"Automating YouTube Video Uploads","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a YouTube API Automation Specialist. I want to upload videos from a folder to YouTube with titles, descriptions, and tags automatically pulled from a CSV file. Your task: - Authenticate using YouTube Data API v3 with OAuth 2.0. - Loop through a...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating YouTube Video Uploads\"\n\nStarting brief:\nPrompt 9 — Automating YouTube Video Uploads \"You are a YouTube API Automation Specialist. I want to upload videos from a folder to YouTube with titles, descriptions, and tags automatically pulled from a CSV file. Your task: - Authenticate using YouTube Data API v3 with OAuth 2.0. - Loop through a folder containing video files. - Read metadata from a CSV (title, description, tags, privacyStatus). - Upload each video with the corresponding metadata. - Log upload IDs and publish status. Output format: Python script + CSV metadata mapping + OAuth setup guide. Input Files & Code Section: - video_metadata.csv with columns for each video. - Folder path for video files. client_secret.json for OAuth credentials.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating YouTube Video Uploads details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":510,"title":"Daily Currency Conversion Automation","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Currency Data Automation Specialist. I want to fetch daily SGD to USD, EUR, and GBP exchange rates and update them in my Google Sheet automatically. Your task: - Connect to a currency exchange API (e.g., ExchangeRate-API). - Fetch latest...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Daily Currency Conversion Automation\"\n\nStarting brief:\nPrompt 10 — Daily Currency Conversion Automation \"You are a Currency Data Automation Specialist. I want to fetch daily SGD to USD, EUR, and GBP exchange rates and update them in my Google Sheet automatically. Your task: - Connect to a currency exchange API (e.g., ExchangeRate-API). - Fetch latest conversion rates for SGD to target currencies. - Write data to a specific Google Sheets cell range. - Include timestamp of last update. - Schedule script to run daily at 8 AM SGT. Output format: Python script + Google Sheets API integration + scheduler setup guide. Input Files & Code Section: - API key file for ExchangeRate-API. - Google Sheets spreadsheet ID. config.json for target currency list.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Daily Currency Conversion Automation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":511,"title":"Automating Job Application Tracking","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Job Search Workflow Automation Engineer. I want an automated job application tracker that consolidates applications from LinkedIn Jobs and JobStreet Singapore using their APIs/webhooks. Copy-ready prompt with placeholders, task steps, output...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Job Application Tracking\"\n\nStarting brief:\n\"You are a Job Search Workflow Automation Engineer. I want an automated job application tracker that consolidates applications from LinkedIn Jobs and JobStreet Singapore using their APIs/webhooks.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Job Application Tracking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":512,"title":"Automating Property Price Tracking for Investment","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Real Estate Data Automation Specialist skilled in integrating PropertyGuru, 99.co, and SRX APIs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Property Price Tracking for Investment\"\n\nStarting brief:\n\"You are a Real Estate Data Automation Specialist skilled in integrating PropertyGuru, 99.co, and SRX APIs.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Property Price Tracking for Investment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":513,"title":"Automating Invoice Payment Reminders","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Business Workflow Automation Specialist. I want to automate client payment reminders using QuickBooks API and Gmail API. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Invoice Payment Reminders\"\n\nStarting brief:\n\"You are a Business Workflow Automation Specialist. I want to automate client payment reminders using QuickBooks API and Gmail API.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Invoice Payment Reminders details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":514,"title":"Automating Resume Screening for Recruitment","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Recruitment Automation Specialist. I want to integrate Google Drive API and an NLP model to process incoming resumes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Resume Screening for Recruitment\"\n\nStarting brief:\n\"You are a Recruitment Automation Specialist. I want to integrate Google Drive API and an NLP model to process incoming resumes.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Resume Screening for Recruitment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":515,"title":"Automating YouTube Comment Sentiment Analysis","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Social Media Analytics Automation Engineer. I want a system that fetches my YouTube video comments weekly, analyses sentiment, and creates a dashboard. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating YouTube Comment Sentiment Analysis\"\n\nStarting brief:\n\"You are a Social Media Analytics Automation Engineer. I want a system that fetches my YouTube video comments weekly, analyses sentiment, and creates a dashboard.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating YouTube Comment Sentiment Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":516,"title":"Automating E commerce Inventory Updates Across Platforms","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are an E-commerce API Integration Specialist. I want a single source of truth for my inventory, updated across Shopee, Lazada, and Shopify in real time. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating E commerce Inventory Updates Across Platforms\"\n\nStarting brief:\n\"You are an E-commerce API Integration Specialist. I want a single source of truth for my inventory, updated across Shopee, Lazada, and Shopify in real time.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating E commerce Inventory Updates Across Platforms details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":517,"title":"Automating Customer Support Ticket Categorisation","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Customer Service Workflow Automation Engineer. I want to integrate Gmail API, NLP (Natural Language Processing), and a ticketing system API (like Zendesk). Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Customer Support Ticket Categorisation\"\n\nStarting brief:\n\"You are a Customer Service Workflow Automation Engineer. I want to integrate Gmail API, NLP (Natural Language Processing), and a ticketing system API (like Zendesk).\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Customer Support Ticket Categorisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":518,"title":"Automating Daily Stock Market Newsletter","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Financial Automation Developer. I want a daily 7:30 AM SGT newsletter combining stock prices, market news, and a short AI-generated analysis. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Daily Stock Market Newsletter\"\n\nStarting brief:\n\"You are a Financial Automation Developer. I want a daily 7:30 AM SGT newsletter combining stock prices, market news, and a short AI-generated analysis.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Daily Stock Market Newsletter details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":519,"title":"Automating Attendance Tracking with Face Recognition","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are an AI-Driven HR Automation Specialist. I want a face recognition attendance tracker that integrates with Zoho People API. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Attendance Tracking with Face Recognition\"\n\nStarting brief:\n\"You are an AI-Driven HR Automation Specialist. I want a face recognition attendance tracker that integrates with Zoho People API.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Attendance Tracking with Face Recognition details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":520,"title":"Automating Podcast Transcription and Upload","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Content Automation Engineer. I want an automation that listens for new podcast episodes, transcribes them, and publishes to my WordPress blog. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Podcast Transcription and Upload\"\n\nStarting brief:\n\"You are a Content Automation Engineer. I want an automation that listens for new podcast episodes, transcribes them, and publishes to my WordPress blog.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Podcast Transcription and Upload details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":521,"title":"Automating Business KPI Dashboard Updates","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Business Intelligence Automation Specialist. I want an automated data pipeline feeding my Power BI dashboard daily. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Business KPI Dashboard Updates\"\n\nStarting brief:\n\"You are a Business Intelligence Automation Specialist. I want an automated data pipeline feeding my Power BI dashboard daily.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Business KPI Dashboard Updates details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":522,"title":"Automating Legal Document Generation","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Legal Tech Automation Specialist. I want an API-based system that populates legal document templates from a client database. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Legal Document Generation\"\n\nStarting brief:\n\"You are a Legal Tech Automation Specialist. I want an API-based system that populates legal document templates from a client database.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Legal Document Generation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":523,"title":"Automating Food Delivery Order Processing","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Food Tech API Integration Specialist. I want a centralised order management system pulling data from foodpanda, GrabFood, and my website. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Food Delivery Order Processing\"\n\nStarting brief:\n\"You are a Food Tech API Integration Specialist. I want a centralised order management system pulling data from foodpanda, GrabFood, and my website.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Food Delivery Order Processing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":524,"title":"Automating Social Media Comment Replies","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Social Media Engagement Automation Engineer. I want to use Instagram Graph API and NLP to auto-reply to comments. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Social Media Comment Replies\"\n\nStarting brief:\n\"You are a Social Media Engagement Automation Engineer. I want to use Instagram Graph API and NLP to auto-reply to comments.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Social Media Comment Replies details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":525,"title":"Automating YouTube to Instagram Clip Conversion","category":"CRM & Projects","source":"IT & Data","module":"API Integration Automation","difficulty":"Advanced","explanation":"\"You are a Video Content Automation Specialist. I want to pull my latest YouTube videos, create 60-second highlights, auto-caption them, and upload to Instagram. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating YouTube to Instagram Clip Conversion\"\n\nStarting brief:\n\"You are a Video Content Automation Specialist. I want to pull my latest YouTube videos, create 60-second highlights, auto-caption them, and upload to Instagram.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating YouTube to Instagram Clip Conversion details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":526,"title":"Code Review & Optimisation Plan","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a senior software engineer with expertise in [programming language/framework]. I have a codebase for a [type of application — e.g., e-commerce site, chatbot, mobile app] that works but runs slowly. Review the code for: - Inefficient loops or...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Code Review & Optimisation Plan\"\n\nStarting brief:\nPrompt 1 — Code Review & Optimisation Plan \"You are a senior software engineer with expertise in [programming language/framework]. I have a codebase for a [type of application — e.g., e-commerce site, chatbot, mobile app] that works but runs slowly. Review the code for: - Inefficient loops or redundant logic. - Poor memory management. - Opportunities to replace custom code with standard libraries. - Security vulnerabilities (SQL injection, XSS). - Best practices for scalability. Provide output in 2 sections: a table of issues (with line numbers & problem description) and an optimised code snippet for each fix.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Code Review & Optimisation Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":527,"title":"Bug Reproduction & Fix Documentation","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a QA (Quality Assurance) automation tester and developer. I have a bug where [describe bug behaviour] in my [framework/app type]. Create a debugging report that includes: - Exact steps to reproduce the bug. - Screenshots or logs showing the issue....","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Bug Reproduction & Fix Documentation\"\n\nStarting brief:\nPrompt 2 — Bug Reproduction & Fix Documentation \"You are a QA (Quality Assurance) automation tester and developer. I have a bug where [describe bug behaviour] in my [framework/app type]. Create a debugging report that includes: - Exact steps to reproduce the bug. - Screenshots or logs showing the issue. - The suspected root cause in the code. - The corrected code segment. - Unit test cases to ensure the bug doesn't reappear. Output in debugging report format with code blocks.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Bug Reproduction & Fix Documentation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":528,"title":"Multi Language Code Conversion","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"Multi-Language Code Conversion \"You are a cross-platform developer. Convert my [programming language] code for [feature/function] into [target language], ensuring: - Exact feature parity. - Proper syntax & library usage in the target language. - Equivalent...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Multi Language Code Conversion\"\n\nStarting brief:\nPrompt 3 — Multi-Language Code Conversion \"You are a cross-platform developer. Convert my [programming language] code for [feature/function] into [target language], ensuring: - Exact feature parity. - Proper syntax & library usage in the target language. - Equivalent performance or better. - Inline comments explaining logic. - A quick performance test script in the target language. Output in side-by-side original vs converted code format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Multi Language Code Conversion details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":529,"title":"Algorithm Efficiency Upgrade","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a competitive programming expert. My current [sorting/searching/matching/etc.] algorithm in [language] works but is slow on large datasets. Optimise it by: - Suggesting a faster algorithm (e.g., replacing bubble sort with merge sort). - Explaining...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Algorithm Efficiency Upgrade\"\n\nStarting brief:\nPrompt 4 — Algorithm Efficiency Upgrade \"You are a competitive programming expert. My current [sorting/searching/matching/etc.] algorithm in [language] works but is slow on large datasets. Optimise it by: - Suggesting a faster algorithm (e.g., replacing bubble sort with merge sort). - Explaining time & space complexity differences. - Providing optimised code. - Writing performance benchmarks comparing both versions. Output in comparative performance report format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Algorithm Efficiency Upgrade details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":530,"title":"Debugging API Integration Issues","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are an API integration specialist. My app in [language/framework] fails to fetch data from [API name] correctly. Diagnose the problem by: - Reviewing my API request code. - Checking authentication & endpoint issues. - Suggesting correct request format...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Debugging API Integration Issues\"\n\nStarting brief:\nPrompt 5 — Debugging API Integration Issues \"You are an API integration specialist. My app in [language/framework] fails to fetch data from [API name] correctly. Diagnose the problem by: - Reviewing my API request code. - Checking authentication & endpoint issues. - Suggesting correct request format with example. - Adding error handling for network failures. - Writing a test function to validate the fix. Output in debugging log + corrected code block.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Debugging API Integration Issues details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":531,"title":"Code Refactoring for Readability & Maintainability","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a senior code architect. Refactor my [language/framework] code for [feature/function] so it is: - Easier to read with proper indentation & naming conventions. - Modularised into reusable functions or classes. - Documented with meaningful comments....","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Code Refactoring for Readability & Maintainability\"\n\nStarting brief:\nPrompt 6 — Code Refactoring for Readability & Maintainability \"You are a senior code architect. Refactor my [language/framework] code for [feature/function] so it is: - Easier to read with proper indentation & naming conventions. - Modularised into reusable functions or classes. - Documented with meaningful comments. - Compliant with [specific coding standard, e.g., PEP8 for Python]. - Unit tested to ensure functionality remains unchanged. Output in before/after code comparison format with a change log.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Code Refactoring for Readability & Maintainability details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":532,"title":"Legacy Code Modernisation Plan","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a legacy systems upgrade specialist. My [old programming language or framework] code needs to be upgraded to [modern equivalent] while preserving functionality. Include: - Identification of outdated functions/libraries. - Recommended replacements...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Legacy Code Modernisation Plan\"\n\nStarting brief:\nPrompt 7 — Legacy Code Modernisation Plan \"You are a legacy systems upgrade specialist. My [old programming language or framework] code needs to be upgraded to [modern equivalent] while preserving functionality. Include: - Identification of outdated functions/libraries. - Recommended replacements & modern equivalents. - Compatibility concerns with the new environment. - Performance benefits after modernisation. - Step-by-step migration plan with testing checkpoints. Output in legacy-to-modern migration report format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Legacy Code Modernisation Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":533,"title":"Continuous Integration (CI) Debugging Setup","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a DevOps engineer. Configure a CI pipeline for my [language/framework] project to automatically run code linting, unit tests, and integration tests whenever code is pushed. Include: - Recommended CI tool (GitHub Actions, Jenkins, GitLab CI). -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Continuous Integration (CI) Debugging Setup\"\n\nStarting brief:\nPrompt 8 — Continuous Integration (CI) Debugging Setup \"You are a DevOps engineer. Configure a CI pipeline for my [language/framework] project to automatically run code linting, unit tests, and integration tests whenever code is pushed. Include: - Recommended CI tool (GitHub Actions, Jenkins, GitLab CI). - Pipeline configuration script. - Test coverage reporting setup. - Common CI errors & how to fix them. - Notification integration (Slack/Email) for failed builds. Output in pipeline YAML file + setup guide.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Continuous Integration (CI) Debugging Setup details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":534,"title":"Memory Leak Detection & Fix","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a performance optimisation engineer. Analyse my [language/framework] application for memory leaks and: - Identify possible causes from code structure. - Suggest profiling tools (Valgrind, Perf, Chrome DevTools). - Provide a step-by-step method to...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Memory Leak Detection & Fix\"\n\nStarting brief:\nPrompt 9 — Memory Leak Detection & Fix \"You are a performance optimisation engineer. Analyse my [language/framework] application for memory leaks and: - Identify possible causes from code structure. - Suggest profiling tools (Valgrind, Perf, Chrome DevTools). - Provide a step-by-step method to reproduce memory growth. - Fix the leak with corrected code examples. - Suggest long-term prevention strategies. Output in diagnostic report + corrected code samples.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Memory Leak Detection & Fix details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":535,"title":"Multi Threading Bug Resolution","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"Multi-Threading Bug Resolution \"You are a concurrency programming specialist. My [language/framework] application faces race conditions and deadlocks. Include: - Detailed explanation of the issue. - Steps to identify which thread is causing the block. -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Multi Threading Bug Resolution\"\n\nStarting brief:\nPrompt 10 — Multi-Threading Bug Resolution \"You are a concurrency programming specialist. My [language/framework] application faces race conditions and deadlocks. Include: - Detailed explanation of the issue. - Steps to identify which thread is causing the block. - Corrected thread-safe code. - Recommended locking or async patterns. - Performance benchmarks after fix. Output in bug analysis + updated code format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Multi Threading Bug Resolution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":536,"title":"Automated Unit Test Generation","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a test automation engineer. Write automated unit test scripts for my [language/framework] code covering [feature/function]. Include: - Test cases for normal, boundary, and error conditions. - Assertions for expected output. - Mock data creation. -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automated Unit Test Generation\"\n\nStarting brief:\nPrompt 11 — Automated Unit Test Generation \"You are a test automation engineer. Write automated unit test scripts for my [language/framework] code covering [feature/function]. Include: - Test cases for normal, boundary, and error conditions. - Assertions for expected output. - Mock data creation. - Code coverage percentage target (e.g., >80%). - How to run tests in CI/CD pipeline. Output in ready-to-run test script format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automated Unit Test Generation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":537,"title":"SQL Query Debugging & Optimisation","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a database performance engineer. Optimise my slow SQL queries for [database type: MySQL, PostgreSQL, etc.]. Include: - Query execution plan analysis. - Indexing strategy. - Query rewriting for speed. - Caching recommendations. - Before/after...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"SQL Query Debugging & Optimisation\"\n\nStarting brief:\nPrompt 12 — SQL Query Debugging & Optimisation \"You are a database performance engineer. Optimise my slow SQL queries for [database type: MySQL, PostgreSQL, etc.]. Include: - Query execution plan analysis. - Indexing strategy. - Query rewriting for speed. - Caching recommendations. - Before/after execution time comparison. Output in query optimisation report with revised SQL statements.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- SQL Query Debugging & Optimisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":538,"title":"Cross Browser Bug Fix Plan","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"Cross-Browser Bug Fix Plan \"You are a front-end debugging expert. My web app works on Chrome but fails in Firefox & Safari. Include: - List of browser compatibility issues. - Code fixes using cross-browser safe APIs. - CSS vendor prefixing guide. -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Cross Browser Bug Fix Plan\"\n\nStarting brief:\nPrompt 13 — Cross-Browser Bug Fix Plan \"You are a front-end debugging expert. My web app works on Chrome but fails in Firefox & Safari. Include: - List of browser compatibility issues. - Code fixes using cross-browser safe APIs. - CSS vendor prefixing guide. - Polyfill recommendations for unsupported features. - Testing checklist for all major browsers. Output in browser compatibility report + fixed code snippets.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Cross Browser Bug Fix Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":539,"title":"API Rate Limit Error Resolution","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are an API performance consultant. My app hits rate limits when fetching data from [API name]. Include: - How to detect rate limit headers. - Backoff strategies & caching techniques. - Batch request examples. - Code modifications for retry logic. -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"API Rate Limit Error Resolution\"\n\nStarting brief:\nPrompt 14 — API Rate Limit Error Resolution \"You are an API performance consultant. My app hits rate limits when fetching data from [API name]. Include: - How to detect rate limit headers. - Backoff strategies & caching techniques. - Batch request examples. - Code modifications for retry logic. - Test scenarios to confirm the fix. Output in rate limit handling guide + updated code.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- API Rate Limit Error Resolution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":540,"title":"Deployment Bug Fix Checklist","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a deployment engineer. My application works locally but fails in production. Include: - Environment variable checks. - Dependency version mismatches. - Server configuration issues. - Build process verification. - Automated rollback setup. Output...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Deployment Bug Fix Checklist\"\n\nStarting brief:\nPrompt 15 — Deployment Bug Fix Checklist \"You are a deployment engineer. My application works locally but fails in production. Include: - Environment variable checks. - Dependency version mismatches. - Server configuration issues. - Build process verification. - Automated rollback setup. Output in deployment debugging checklist format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Deployment Bug Fix Checklist details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":541,"title":"Version Control Conflict Resolution","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a Git (Version Control) expert. Resolve merge conflicts in my [repository name] while ensuring no functionality loss. Include: - Step-by-step conflict resolution process. - Commit best practices to avoid future issues. - Branch management...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Version Control Conflict Resolution\"\n\nStarting brief:\nPrompt 16 — Version Control Conflict Resolution \"You are a Git (Version Control) expert. Resolve merge conflicts in my [repository name] while ensuring no functionality loss. Include: - Step-by-step conflict resolution process. - Commit best practices to avoid future issues. - Branch management guidelines. - Git command examples for common scenarios. Output in merge resolution guide with Git commands.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Version Control Conflict Resolution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":542,"title":"Security Vulnerability Patch Plan","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a cybersecurity code auditor. Review my [language/framework] code for vulnerabilities like SQL injection, XSS, and CSRF. Include: - Vulnerability list with risk levels. - Code patches with secure alternatives. - OWASP (Open Web Application...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Security Vulnerability Patch Plan\"\n\nStarting brief:\nPrompt 17 — Security Vulnerability Patch Plan \"You are a cybersecurity code auditor. Review my [language/framework] code for vulnerabilities like SQL injection, XSS, and CSRF. Include: - Vulnerability list with risk levels. - Code patches with secure alternatives. - OWASP (Open Web Application Security Project) best practice checklist. - Security testing tools list. Output in vulnerability report + patched code samples.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Security Vulnerability Patch Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":543,"title":"Cloud Function Debugging Guide","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a cloud application developer. Debug my [AWS Lambda / Google Cloud Function / Azure Function] which is failing intermittently. Include: - Log analysis methods. - Error pattern detection. - Code changes for reliability. - Testing with local...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Cloud Function Debugging Guide\"\n\nStarting brief:\nPrompt 18 — Cloud Function Debugging Guide \"You are a cloud application developer. Debug my [AWS Lambda / Google Cloud Function / Azure Function] which is failing intermittently. Include: - Log analysis methods. - Error pattern detection. - Code changes for reliability. - Testing with local emulators. - Deployment steps after fix. Output in debugging flowchart + corrected function code.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Cloud Function Debugging Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":544,"title":"Mobile App Crash Analysis","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a mobile app debugging expert. Analyse my [Android/iOS] app for crash reports related to [feature/function]. Include: - Crash log interpretation. - Root cause identification. - Code corrections. - Device-specific fixes. - Testing plan for all OS...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Mobile App Crash Analysis\"\n\nStarting brief:\nPrompt 19 — Mobile App Crash Analysis \"You are a mobile app debugging expert. Analyse my [Android/iOS] app for crash reports related to [feature/function]. Include: - Crash log interpretation. - Root cause identification. - Code corrections. - Device-specific fixes. - Testing plan for all OS versions. Output in crash report + updated code block.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Mobile App Crash Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":545,"title":"Real Time Error Monitoring Setup","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"Real-Time Error Monitoring Setup \"You are a site reliability engineer. Set up a real-time error tracking system for my [language/framework] app. Include: - Recommended monitoring tools (Sentry, New Relic, Datadog). - Setup steps for integration. - Error...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Real Time Error Monitoring Setup\"\n\nStarting brief:\nPrompt 20 — Real-Time Error Monitoring Setup \"You are a site reliability engineer. Set up a real-time error tracking system for my [language/framework] app. Include: - Recommended monitoring tools (Sentry, New Relic, Datadog). - Setup steps for integration. - Error categorisation for alerts. - Dashboard layout suggestions. - Weekly reporting format. Output in tool setup guide + dashboard screenshot mockup.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Real Time Error Monitoring Setup details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":546,"title":"Data Processing Script Debugging","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a data engineer. My Python ETL (Extract, Transform, Load) script fails at the transformation stage. Include: - Step-by-step debugging for data type mismatches. - Handling null values & schema changes. - Logging setup for error tracking. -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Data Processing Script Debugging\"\n\nStarting brief:\nPrompt 21 — Data Processing Script Debugging \"You are a data engineer. My Python ETL (Extract, Transform, Load) script fails at the transformation stage. Include: - Step-by-step debugging for data type mismatches. - Handling null values & schema changes. - Logging setup for error tracking. - Optimised data transformation logic. - Unit tests for validation. Output in debugging report + corrected script.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Data Processing Script Debugging details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":547,"title":"Infinite Loop Prevention in Code","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a software safety expert. Analyse my [language] code for infinite loop risks and fix them. Include: - Detection of loops without termination conditions. - Corrected loop conditions. - Safeguards to prevent reoccurrence. - Performance benchmarks...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Infinite Loop Prevention in Code\"\n\nStarting brief:\nPrompt 22 — Infinite Loop Prevention in Code \"You are a software safety expert. Analyse my [language] code for infinite loop risks and fix them. Include: - Detection of loops without termination conditions. - Corrected loop conditions. - Safeguards to prevent reoccurrence. - Performance benchmarks after fix. Output in before/after code format.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Infinite Loop Prevention in Code details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":548,"title":"Automated Code Documentation Generator","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a documentation automation consultant. Set up an auto-documentation system for my [language/framework] project. Include: - Recommended tools (e.g., JSDoc, Sphinx). - Integration into CI/CD pipeline. - Style guide for consistent doc formatting. -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automated Code Documentation Generator\"\n\nStarting brief:\nPrompt 23 — Automated Code Documentation Generator \"You are a documentation automation consultant. Set up an auto-documentation system for my [language/framework] project. Include: - Recommended tools (e.g., JSDoc, Sphinx). - Integration into CI/CD pipeline. - Style guide for consistent doc formatting. - Sample generated documentation. Output in documentation setup guide + example output.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automated Code Documentation Generator details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":549,"title":"Debugging Scheduler & Cron Job Failures","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a backend engineer. My scheduled tasks in [language/framework] fail intermittently. Include: - Log analysis to find failure points. - Corrected cron expressions. - Error handling logic. - Monitoring alerts setup. - Retry mechanism. Output in...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Debugging Scheduler & Cron Job Failures\"\n\nStarting brief:\nPrompt 24 — Debugging Scheduler & Cron Job Failures \"You are a backend engineer. My scheduled tasks in [language/framework] fail intermittently. Include: - Log analysis to find failure points. - Corrected cron expressions. - Error handling logic. - Monitoring alerts setup. - Retry mechanism. Output in debugging report + fixed scheduling script.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Debugging Scheduler & Cron Job Failures details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":550,"title":"Codebase Technical Debt Reduction Plan","category":"CRM & Projects","source":"IT & Data","module":"Coding Debugging","difficulty":"Advanced","explanation":"\"You are a senior software architect. Analyse my [language/framework] codebase for technical debt and create a 3-month cleanup roadmap. Include: - List of outdated dependencies. - Code smells & fixes. - Testing coverage improvement. - Refactoring...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Codebase Technical Debt Reduction Plan\"\n\nStarting brief:\nYou are a senior software architect. Analyse my [language/framework] codebase for technical debt and create a 3-month cleanup roadmap. Include: - List of outdated dependencies. - Code smells & fixes. - Testing coverage improvement. - Refactoring priorities. - Risk mitigation plan. Output in technical debt report + phased action plan.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Codebase Technical Debt Reduction Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":551,"title":"Automating Security Log Monitoring","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Cybersecurity Automation Engineer. I want a script that scans server logs in real time and alerts me of suspicious activity such as failed login attempts, unusual IP addresses, or data spikes. Copy-ready prompt with placeholders, task steps,...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Security Log Monitoring\"\n\nStarting brief:\n\"You are a Cybersecurity Automation Engineer. I want a script that scans server logs in real time and alerts me of suspicious activity such as failed login attempts, unusual IP addresses, or data spikes.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Security Log Monitoring details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":552,"title":"Automating Data Backup with Encryption","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Data Security Engineer. I want an automated backup system that encrypts files before uploading them to cloud storage (AWS S3, Google Drive). Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Data Backup with Encryption\"\n\nStarting brief:\n\"You are a Data Security Engineer. I want an automated backup system that encrypts files before uploading them to cloud storage (AWS S3, Google Drive).\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Data Backup with Encryption details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":553,"title":"Automating Phishing Email Detection","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Email Security Automation Specialist. I want to integrate Gmail API with an AI phishing detection model. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Phishing Email Detection\"\n\nStarting brief:\n\"You are an Email Security Automation Specialist. I want to integrate Gmail API with an AI phishing detection model.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Phishing Email Detection details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":554,"title":"Automating GDPR Data Deletion Requests","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Privacy Compliance Automation Expert. I want a workflow that processes GDPR deletion requests automatically. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating GDPR Data Deletion Requests\"\n\nStarting brief:\n\"You are a Privacy Compliance Automation Expert. I want a workflow that processes GDPR deletion requests automatically.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating GDPR Data Deletion Requests details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":555,"title":"Automating Vulnerability Scans","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Security Scan Automation Engineer. I want to run daily vulnerability scans and generate reports automatically. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Vulnerability Scans\"\n\nStarting brief:\n\"You are a Security Scan Automation Engineer. I want to run daily vulnerability scans and generate reports automatically.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Vulnerability Scans details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":556,"title":"Automating Two Factor Authentication (2FA) Setup for All Users","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Identity & Access Management Automation Specialist. I want to roll out mandatory Two-Factor Authentication for all company accounts in Google Workspace. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Two Factor Authentication (2FA) Setup for All Users\"\n\nStarting brief:\n\"You are an Identity & Access Management Automation Specialist. I want to roll out mandatory Two-Factor Authentication for all company accounts in Google Workspace.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Two Factor Authentication (2FA) Setup for All Users details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":557,"title":"Automating Data Breach Monitoring with Dark Web Scans","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Threat Intelligence Automation Engineer. I want to integrate HaveIBeenPwned API and a dark web monitoring API to scan for leaked email/password combinations. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Data Breach Monitoring with Dark Web Scans\"\n\nStarting brief:\n\"You are a Threat Intelligence Automation Engineer. I want to integrate HaveIBeenPwned API and a dark web monitoring API to scan for leaked email/password combinations.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Data Breach Monitoring with Dark Web Scans details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":558,"title":"Automating Role Based Access Control (RBAC) Updates","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Access Control Automation Expert. I want an integration between our HR system and internal application APIs to update user permissions automatically. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Role Based Access Control (RBAC) Updates\"\n\nStarting brief:\n\"You are an Access Control Automation Expert. I want an integration between our HR system and internal application APIs to update user permissions automatically.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Role Based Access Control (RBAC) Updates details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":559,"title":"Automating Security Awareness Quizzes","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Security Training Automation Specialist. I want a system that emails a short quiz to employees each month and records their scores. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Security Awareness Quizzes\"\n\nStarting brief:\n\"You are a Security Training Automation Specialist. I want a system that emails a short quiz to employees each month and records their scores.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Security Awareness Quizzes details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":560,"title":"Automating SSL Certificate Expiry Alerts","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Web Security Automation Engineer. I want a system that checks SSL certificate expiry dates for a list of domains. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating SSL Certificate Expiry Alerts\"\n\nStarting brief:\n\"You are a Web Security Automation Engineer. I want a system that checks SSL certificate expiry dates for a list of domains.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating SSL Certificate Expiry Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":561,"title":"Automating Endpoint Device Compliance Checks","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Endpoint Security Automation Engineer. I want a system that verifies employee device compliance (OS version, antivirus status, firewall enabled) every time they connect to the company network. Copy-ready prompt with placeholders, task steps,...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Endpoint Device Compliance Checks\"\n\nStarting brief:\n\"You are an Endpoint Security Automation Engineer. I want a system that verifies employee device compliance (OS version, antivirus status, firewall enabled) every time they connect to the company network.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Endpoint Device Compliance Checks details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":562,"title":"Automating Sensitive File Access Alerts","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a File Access Monitoring Specialist. I want an automation that detects and alerts whenever certain high-security files are accessed. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Sensitive File Access Alerts\"\n\nStarting brief:\n\"You are a File Access Monitoring Specialist. I want an automation that detects and alerts whenever certain high-security files are accessed.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Sensitive File Access Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":563,"title":"Automating Database Security Audits","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Database Security Automation Expert. I want a script that scans for vulnerabilities in our MySQL/PostgreSQL databases and generates a security report. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Database Security Audits\"\n\nStarting brief:\n\"You are a Database Security Automation Expert. I want a script that scans for vulnerabilities in our MySQL/PostgreSQL databases and generates a security report.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Database Security Audits details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":564,"title":"Automating USB Device Restrictions","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Endpoint Device Control Automation Specialist. I want a system that blocks all USB devices except approved company drives. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating USB Device Restrictions\"\n\nStarting brief:\n\"You are an Endpoint Device Control Automation Specialist. I want a system that blocks all USB devices except approved company drives.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating USB Device Restrictions details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":565,"title":"Automating Password Expiry Reminders","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Account Security Automation Specialist. I want to integrate with Active Directory (AD) to send reminders before password expiry. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Password Expiry Reminders\"\n\nStarting brief:\n\"You are an Account Security Automation Specialist. I want to integrate with Active Directory (AD) to send reminders before password expiry.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Password Expiry Reminders details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":566,"title":"Automating Encrypted File Sharing","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Secure File Transfer Automation Expert. I want to encrypt files and send them via a secure download link that expires after 48 hours. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Encrypted File Sharing\"\n\nStarting brief:\n\"You are a Secure File Transfer Automation Expert. I want to encrypt files and send them via a secure download link that expires after 48 hours.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Encrypted File Sharing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":567,"title":"Automating Insider Threat Detection","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an Insider Threat Monitoring Specialist. I want a system that flags abnormal access activity by employees. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Insider Threat Detection\"\n\nStarting brief:\n\"You are an Insider Threat Monitoring Specialist. I want a system that flags abnormal access activity by employees.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Insider Threat Detection details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":568,"title":"Automating Compliance Document Management","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Compliance Automation Specialist. I want a system that fetches logs, audit reports, and policy documents from multiple systems into one folder. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Compliance Document Management\"\n\nStarting brief:\n\"You are a Compliance Automation Specialist. I want a system that fetches logs, audit reports, and policy documents from multiple systems into one folder.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Compliance Document Management details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":569,"title":"Automating Ransomware Simulation Drills","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Cybersecurity Training Automation Engineer. I want a script that simulates a ransomware infection without actually encrypting files. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Ransomware Simulation Drills\"\n\nStarting brief:\n\"You are a Cybersecurity Training Automation Engineer. I want a script that simulates a ransomware infection without actually encrypting files.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Ransomware Simulation Drills details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":570,"title":"Automating API Security Testing","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are an API Security Testing Specialist. I want a script that runs OWASP API Security Top 10 checks on all company APIs. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating API Security Testing\"\n\nStarting brief:\n\"You are an API Security Testing Specialist. I want a script that runs OWASP API Security Top 10 checks on all company APIs.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating API Security Testing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":571,"title":"Automating Cloud Security Policy Enforcement","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Cloud Security Automation Specialist. I want a system that scans all files in Google Drive/AWS S3 for public access and restricts them to approved users only. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Cloud Security Policy Enforcement\"\n\nStarting brief:\n\"You are a Cloud Security Automation Specialist. I want a system that scans all files in Google Drive/AWS S3 for public access and restricts them to approved users only.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Cloud Security Policy Enforcement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":572,"title":"Automating Incident Response Playbook Execution","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Security Incident Automation Engineer. I want a system that executes predefined playbook actions when a breach is detected. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Incident Response Playbook Execution\"\n\nStarting brief:\n\"You are a Security Incident Automation Engineer. I want a system that executes predefined playbook actions when a breach is detected.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Incident Response Playbook Execution details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":573,"title":"Automating Encrypted Chat for Sensitive Communications","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Secure Communications Automation Specialist. I want a tool that creates an encrypted chat room that expires after 24 hours. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Encrypted Chat for Sensitive Communications\"\n\nStarting brief:\n\"You are a Secure Communications Automation Specialist. I want a tool that creates an encrypted chat room that expires after 24 hours.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Encrypted Chat for Sensitive Communications details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":574,"title":"Automating Malware File Scanning for Uploads","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a File Security Automation Engineer. I want an integration that scans each uploaded file with a malware detection API before it's stored. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Malware File Scanning for Uploads\"\n\nStarting brief:\n\"You are a File Security Automation Engineer. I want an integration that scans each uploaded file with a malware detection API before it's stored.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Malware File Scanning for Uploads details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":575,"title":"Automating Security Patch Deployment","category":"CRM & Projects","source":"IT & Data","module":"Cybersecurity Data Privacy","difficulty":"Advanced","explanation":"\"You are a Patch Management Automation Specialist. I want a script that applies critical security patches across all systems as soon as they're available. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automating Security Patch Deployment\"\n\nStarting brief:\n\"You are a Patch Management Automation Specialist. I want a script that applies critical security patches across all systems as soon as they're available.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automating Security Patch Deployment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":576,"title":"Full Exploratory Data Analysis (EDA) with Actionable Insights","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Senior Data Analyst with expertise in Python (Pandas, NumPy, Matplotlib, Seaborn) and data storytelling. I have a dataset in CSV format containing sales data for a Singapore retail chain (2018–2024) with 50,000 rows and 12 columns (date, outlet,...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Full Exploratory Data Analysis (EDA) with Actionable Insights\"\n\nStarting brief:\nPrompt 1 — Full Exploratory Data Analysis (EDA) with Actionable Insights \"You are a Senior Data Analyst with expertise in Python (Pandas, NumPy, Matplotlib, Seaborn) and data storytelling. I have a dataset in CSV format containing sales data for a Singapore retail chain (2018–2024) with 50,000 rows and 12 columns (date, outlet, category, units sold, price, discount, etc.). Your task: - Import and inspect the dataset to understand structure, data types, and column meanings. - Generate summary statistics for both numerical and categorical columns, highlighting anomalies. - Detect missing values, quantify them column-wise, and suggest domain-specific imputation or removal strategies. - Identify outliers using both statistical (Z-score, IQR) and visual (boxplots) methods, explaining potential business causes. - Create a correlation heatmap for numerical features and explain the top 5...\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Full Exploratory Data Analysis (EDA) with Actionable Insights details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":577,"title":"Interactive KPI Dashboard for Decision Makers","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"Interactive KPI Dashboard for Decision-Makers \"You are a Business Intelligence (BI) Dashboard Expert skilled in Power BI, Tableau, and Google Data Studio. I have quarterly sales data for multiple product categories across Singapore for the last 5 years....","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Interactive KPI Dashboard for Decision Makers\"\n\nStarting brief:\nPrompt 2 — Interactive KPI Dashboard for Decision-Makers \"You are a Business Intelligence (BI) Dashboard Expert skilled in Power BI, Tableau, and Google Data Studio. I have quarterly sales data for multiple product categories across Singapore for the last 5 years. Your task: - Identify 5–7 key performance indicators (KPIs) relevant to retail business health (e.g., total revenue, gross margin, average order value, conversion rate). - Design an interactive dashboard layout showing KPIs as cards at the top, trend charts in the middle, and filters (by time, category, location) on the side. - Include drill-down capability so a user can click on a KPI and view detailed breakdowns by category, region, or month. - Add a geographic heatmap showing sales distribution across Singapore districts (CBD, Orchard, Jurong, Tampines, Woodlands, etc.), with hover tooltips. - Include an export-to-PDF...\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Interactive KPI Dashboard for Decision Makers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":578,"title":"Predictive Sales Forecasting with Model Comparison","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Data Scientist specialising in forecasting. I have monthly sales data for an e-commerce platform from January 2018 to December 2024. Your task: - Perform time-series decomposition to analyse trend, seasonality, and residual components. - Build...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Predictive Sales Forecasting with Model Comparison\"\n\nStarting brief:\nPrompt 3 — Predictive Sales Forecasting with Model Comparison \"You are a Data Scientist specialising in forecasting. I have monthly sales data for an e-commerce platform from January 2018 to December 2024. Your task: - Perform time-series decomposition to analyse trend, seasonality, and residual components. - Build at least two forecasting models (ARIMA/SARIMA and Facebook Prophet). - Compare model performance using RMSE (Root Mean Squared Error) and MAPE (Mean Absolute Percentage Error). - Plot actual vs predicted sales for both models and highlight differences. - Provide recommendations for which model to deploy, along with a 12-month sales forecast. Output format: A Python Jupyter Notebook with all code, plots, and a Markdown cell comparing models with business-friendly explanations.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Predictive Sales Forecasting with Model Comparison details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":579,"title":"Automated Data Cleaning and Preprocessing Script","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Data Preprocessing Automation Specialist skilled in Python and Pandas. I have a CSV file containing a mix of numerical, categorical, and datetime fields, with missing values and inconsistent formats. Your task: - Write a reusable Python script...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Automated Data Cleaning and Preprocessing Script\"\n\nStarting brief:\nPrompt 4 — Automated Data Cleaning and Preprocessing Script \"You are a Data Preprocessing Automation Specialist skilled in Python and Pandas. I have a CSV file containing a mix of numerical, categorical, and datetime fields, with missing values and inconsistent formats. Your task: - Write a reusable Python script to detect and handle missing values using mean/median/mode or forward-fill/backward-fill depending on the column type. - Remove duplicate rows and flag near-duplicates for manual review. - Normalise numerical columns (min-max or z-score scaling) and encode categorical columns (label or one-hot encoding as appropriate). - Convert date columns to proper datetime format and extract features (day, month, year, day-of-week). - Save the cleaned dataset to a new CSV file with a timestamped filename. Output format: A fully commented Python script that can be reused for different...\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Automated Data Cleaning and Preprocessing Script details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":580,"title":"Business Data Storytelling for Stakeholder Reports","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Business Data Storyteller with experience in creating executive summaries from analytical results. I have analysed customer purchase behaviour for my online store and want to present findings to the leadership team. Your task: - Frame the...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Business Data Storytelling for Stakeholder Reports\"\n\nStarting brief:\nPrompt 5 — Business Data Storytelling for Stakeholder Reports \"You are a Business Data Storyteller with experience in creating executive summaries from analytical results. I have analysed customer purchase behaviour for my online store and want to present findings to the leadership team. Your task: - Frame the analysis as a story — starting with the problem, key findings, and implications. - Select only the 5–7 most impactful visuals from the analysis, ensuring they are simple and easy to understand. - Explain each chart in 1–2 sentences highlighting what matters for the business. - Conclude with 3 actionable recommendations, each tied to a business outcome (e.g., revenue growth, cost saving). - Create a 2-slide PowerPoint layout that can be used in a leadership meeting. Output format: A concise text storyboard + slide content that a non-technical executive can understand at a glance.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Business Data Storytelling for Stakeholder Reports details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":581,"title":"Real Time Data Monitoring and Alerts","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"Real-Time Data Monitoring and Alerts \"You are a Real-Time Data Monitoring Specialist skilled in tools like Grafana, Kibana, and Power BI Streaming Dataflows. I operate a logistics company with live GPS and delivery data flowing in every 15 seconds. Your...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Real Time Data Monitoring and Alerts\"\n\nStarting brief:\nPrompt 6 — Real-Time Data Monitoring and Alerts \"You are a Real-Time Data Monitoring Specialist skilled in tools like Grafana, Kibana, and Power BI Streaming Dataflows. I operate a logistics company with live GPS and delivery data flowing in every 15 seconds. Your task: - Design a real-time dashboard that displays vehicle location, delivery status, and delays in near real-time. - Implement colour-coded alerts for deliveries delayed beyond SLA (Service Level Agreement) thresholds. - Add trend visualisations for daily delivery count, average delivery time, and % on-time rate. - Integrate automated alerts via email and SMS for key managers when KPIs cross thresholds. - Ensure the system can handle data spikes (e.g., festival season). Output format: A visual architecture diagram + tool integration plan + example SQL queries for alert generation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Real Time Data Monitoring and Alerts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":582,"title":"Sentiment Analysis of Customer Feedback","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are an NLP (Natural Language Processing) Specialist with expertise in Python libraries like NLTK, SpaCy, and Transformers. I have 50,000 customer reviews collected over 2 years. Your task: - Clean and preprocess the text (remove stopwords, lemmatise,...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Sentiment Analysis of Customer Feedback\"\n\nStarting brief:\nPrompt 7 — Sentiment Analysis of Customer Feedback \"You are an NLP (Natural Language Processing) Specialist with expertise in Python libraries like NLTK, SpaCy, and Transformers. I have 50,000 customer reviews collected over 2 years. Your task: - Clean and preprocess the text (remove stopwords, lemmatise, handle emojis). - Classify sentiment into positive, neutral, and negative categories using a pre-trained BERT model. - Create visualisations: - Sentiment distribution pie chart. - Monthly sentiment trend line chart. - Word cloud for each sentiment category. - Identify top 5 positive and top 5 negative themes with example reviews. - Provide actionable recommendations for product/service improvement based on sentiment patterns. Output format: A Jupyter Notebook with code, charts, and a Markdown insights summary.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Sentiment Analysis of Customer Feedback details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":583,"title":"Comparative Category Performance Report","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"\"You are a Business Performance Analyst. I have category-wise sales data for 10 product categories over the last 3 years. Your task: - Calculate YoY (Year-over-Year) and MoM (Month-over-Month) growth rates for each category. - Rank categories based on...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Comparative Category Performance Report\"\n\nStarting brief:\nPrompt 8 — Comparative Category Performance Report \"You are a Business Performance Analyst. I have category-wise sales data for 10 product categories over the last 3 years. Your task: - Calculate YoY (Year-over-Year) and MoM (Month-over-Month) growth rates for each category. - Rank categories based on revenue, profit margin, and units sold. - Create a dashboard view showing category trends side-by-side. - Highlight top 3 performing categories and bottom 3 lagging categories. - Suggest category-level actions to boost sales and margins for underperformers. Output format: A comparative analysis table + dashboard layout mockup + 1-page action plan.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Comparative Category Performance Report details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":584,"title":"Correlation and Causation Testing","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Data Scientist with a focus on statistical inference. I have a dataset on marketing spend (TV, social media, influencer, print) and corresponding sales figures. Your task: - Calculate correlation coefficients for each marketing channel vs sales....","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Correlation and Causation Testing\"\n\nStarting brief:\nPrompt 9 — Correlation and Causation Testing \"You are a Data Scientist with a focus on statistical inference. I have a dataset on marketing spend (TV, social media, influencer, print) and corresponding sales figures. Your task: - Calculate correlation coefficients for each marketing channel vs sales. - Perform hypothesis testing to check statistical significance (p-values). - Run a multiple regression analysis to see which channels predict sales best. - Visualise results using scatter plots and regression lines. - Provide a plain-language explanation of findings for non-technical stakeholders. Output format: Jupyter Notebook with plots + regression output table + simplified insights brief.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Correlation and Causation Testing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":585,"title":"Customer Churn Prediction and Retention Strategy","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Customer Analytics Expert specialising in churn modelling. I have SaaS customer data including sign-up date, usage frequency, support tickets, and payment history. Your task: - Define churn for my business context (e.g., inactive for 60 days). -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Customer Churn Prediction and Retention Strategy\"\n\nStarting brief:\nPrompt 10 — Customer Churn Prediction and Retention Strategy \"You are a Customer Analytics Expert specialising in churn modelling. I have SaaS customer data including sign-up date, usage frequency, support tickets, and payment history. Your task: - Define churn for my business context (e.g., inactive for 60 days). - Engineer predictive features from usage and payment history. - Build a classification model (Logistic Regression, Random Forest, or XGBoost) to predict churn probability. - Evaluate using accuracy, precision, recall, and ROC-AUC. - Suggest retention strategies for the top 20% at-risk customers. Output format: Python Notebook with code + confusion matrix + strategic retention plan.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Customer Churn Prediction and Retention Strategy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":586,"title":"Data Visualization Best Practices Guide","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"\"You are a Data Visualization Trainer. Prepare a best practices guide for visualising financial performance data for stakeholders. Your task: - Recommend which chart types to use for time-series, category comparison, and part-to-whole analysis. - Suggest...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Data Visualization Best Practices Guide\"\n\nStarting brief:\nPrompt 11 — Data Visualization Best Practices Guide \"You are a Data Visualization Trainer. Prepare a best practices guide for visualising financial performance data for stakeholders. Your task: - Recommend which chart types to use for time-series, category comparison, and part-to-whole analysis. - Suggest an accessible, colour-blind-friendly palette. - Explain how to avoid misleading scales and data distortion. - Include 3 examples of excellent visualisations and explain why they work. - Provide 3 poor visualisation examples and show corrected versions. Output format: A 5-page PDF guide with do's and don'ts + visual examples.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Data Visualization Best Practices Guide details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":587,"title":"Multi Dataset Integration Workflow","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"Multi-Dataset Integration Workflow \"You are a Data Integration Specialist skilled in ETL (Extract, Transform, Load) processes. I have three datasets: - Customer demographics (Excel) - Purchase history (CSV) - Web analytics data (Google Analytics export)...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Multi Dataset Integration Workflow\"\n\nStarting brief:\nPrompt 12 — Multi-Dataset Integration Workflow \"You are a Data Integration Specialist skilled in ETL (Extract, Transform, Load) processes. I have three datasets: - Customer demographics (Excel) - Purchase history (CSV) - Web analytics data (Google Analytics export) Your task: - Identify common keys for merging datasets. - Clean and standardise column formats and naming. - Join datasets into a master table. - Perform initial descriptive analysis on combined data. - Suggest 3 insights achievable only after combining data. Output format: Python Notebook with ETL code + final merged dataset snapshot + insight summary.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Multi Dataset Integration Workflow details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":588,"title":"Interactive Geo Spatial Sales Mapping","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"Interactive Geo-Spatial Sales Mapping \"You are a GIS (Geographic Information Systems) Analyst. I have planning-area-level sales data for Singapore (and selected Southeast Asian markets) for the past 12 months. Your task: - Create an interactive map showing...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Interactive Geo Spatial Sales Mapping\"\n\nStarting brief:\nPrompt 13 — Interactive Geo-Spatial Sales Mapping \"You are a GIS (Geographic Information Systems) Analyst. I have planning-area-level sales data for Singapore (and selected Southeast Asian markets) for the past 12 months. Your task: - Create an interactive map showing sales density across Singapore planning areas (and optionally key SEA cities) using a colour gradient. - Add filters for month, product category, and sales rep. - Display area-level tooltips with key KPIs (revenue in S$, units sold, growth rate). - Enable comparison mode for two selected planning areas or regional markets. - Provide export options (PNG, PDF). Output format: Dashboard implementation guide + sample data visualisation screenshot.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Interactive Geo Spatial Sales Mapping details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":589,"title":"Industry Benchmark Comparison with Gap Analysis","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"\"You are a Market Intelligence Analyst specialising in competitive benchmarking. I have my company’s quarterly performance metrics for revenue, gross margin, and customer acquisition rate, and I have benchmark data for top 5 competitors. Your task: -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Industry Benchmark Comparison with Gap Analysis\"\n\nStarting brief:\nPrompt 14 — Industry Benchmark Comparison with Gap Analysis \"You are a Market Intelligence Analyst specialising in competitive benchmarking. I have my company's quarterly performance metrics for revenue, gross margin, and customer acquisition rate, and I have benchmark data for top 5 competitors. Your task: - Normalise all data for fair comparison (e.g., currency conversion, adjusting for fiscal year differences). - Create comparative bar charts showing my company vs each competitor for each KPI (Key Performance Indicator). - Calculate % variance from industry average for each KPI. - Identify areas where my company is above average and where it's lagging. - Provide 5 targeted recommendations to close performance gaps. Output format: A 2-page PDF competitive report with visual comparisons, an executive summary, and a prioritised action list.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Industry Benchmark Comparison with Gap Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":590,"title":"Data Pipeline Performance Optimisation Plan","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Data Engineer experienced in optimising ETL (Extract, Transform, Load) pipelines for speed and efficiency. I have a nightly pipeline that ingests sales, inventory, and customer data into a central warehouse. Your task: - Profile the current...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Data Pipeline Performance Optimisation Plan\"\n\nStarting brief:\nPrompt 15 — Data Pipeline Performance Optimisation Plan \"You are a Data Engineer experienced in optimising ETL (Extract, Transform, Load) pipelines for speed and efficiency. I have a nightly pipeline that ingests sales, inventory, and customer data into a central warehouse. Your task: - Profile the current pipeline to identify slow queries, inefficient joins, and bottleneck processes. - Recommend improvements in query optimisation, indexing, and caching. - Suggest parallelisation or batch processing strategies to reduce runtime. - Propose monitoring tools to track pipeline health and error rates. - Provide an example optimised SQL query and ETL script snippet. Output format: A technical optimisation plan with a \"before vs after\" runtime projection chart and sample code.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Data Pipeline Performance Optimisation Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":591,"title":"Social Media Engagement Analytics Dashboard","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Digital Analytics Expert skilled in API integrations and BI dashboarding. I have social media engagement data from Facebook, Instagram, and LinkedIn for the past 12 months. Your task: - Create a unified dashboard showing platform-wise engagement...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Social Media Engagement Analytics Dashboard\"\n\nStarting brief:\nPrompt 16 — Social Media Engagement Analytics Dashboard \"You are a Digital Analytics Expert skilled in API integrations and BI dashboarding. I have social media engagement data from Facebook, Instagram, and LinkedIn for the past 12 months. Your task: - Create a unified dashboard showing platform-wise engagement metrics (likes, comments, shares, saves). - Add a filter to view engagement by post type (video, carousel, single image, story). - Highlight top 10 performing posts across all platforms with engagement breakdown. - Add follower growth trend lines for each platform. - Include an insights section suggesting which content format drives the highest engagement. Output format: Dashboard wireframe + API integration guide + engagement insights report.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Social Media Engagement Analytics Dashboard details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":592,"title":"Real Estate Market Analysis with Investment Insights","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Real Estate Data Analyst with expertise in property market trends. I have a dataset of property sales in [city] for the last 5 years with columns for location, property type, size, sale price, and date. Your task: - Analyse price trends by...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Real Estate Market Analysis with Investment Insights\"\n\nStarting brief:\nPrompt 17 — Real Estate Market Analysis with Investment Insights \"You are a Real Estate Data Analyst with expertise in property market trends. I have a dataset of property sales in [city] for the last 5 years with columns for location, property type, size, sale price, and date. Your task: - Analyse price trends by property type (apartment, villa, plot). - Map high-growth neighbourhoods using price appreciation over time. - Identify seasonality patterns in sales volume. - Calculate ROI projections for top 5 emerging areas. - Provide investment recommendations for buyers targeting high rental yield vs capital appreciation. Output format: A PDF market report with heatmaps, trend charts, and a 1-page \"Investor Recommendations\" summary.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Real Estate Market Analysis with Investment Insights details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":593,"title":"Healthcare Operational Efficiency Analysis","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"\"You are a Healthcare Data Analyst working on hospital efficiency improvement. I have anonymised patient visit data, bed occupancy records, and treatment timelines for the past 2 years. Your task: - Calculate average patient wait time, treatment time, and...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Healthcare Operational Efficiency Analysis\"\n\nStarting brief:\nPrompt 18 — Healthcare Operational Efficiency Analysis \"You are a Healthcare Data Analyst working on hospital efficiency improvement. I have anonymised patient visit data, bed occupancy records, and treatment timelines for the past 2 years. Your task: - Calculate average patient wait time, treatment time, and discharge time. - Create bed occupancy rate visualisations by department. - Identify peak patient inflow periods and staffing shortages. - Suggest scheduling optimisations to reduce bottlenecks. - Recommend operational changes to improve patient throughput without compromising care quality. Output format: A dashboard layout plan + operational improvement report.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Healthcare Operational Efficiency Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":594,"title":"Sales Funnel Drop off Analysis","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"Sales Funnel Drop-off Analysis \"You are a Marketing Data Analyst focused on conversion rate optimisation. I have e-commerce funnel data for the last quarter showing visits, product views, add-to-cart events, checkout starts, and purchases. Your task: -...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Sales Funnel Drop off Analysis\"\n\nStarting brief:\nPrompt 19 — Sales Funnel Drop-off Analysis \"You are a Marketing Data Analyst focused on conversion rate optimisation. I have e-commerce funnel data for the last quarter showing visits, product views, add-to-cart events, checkout starts, and purchases. Your task: - Calculate conversion rates for each funnel stage. - Identify the stage with the highest drop-off rate and quantify the loss in potential revenue. - Analyse patterns in drop-off by device type, browser, and traffic source. - Suggest at least 5 tactics to improve conversions at the weakest stage. - Provide a visual funnel chart showing current vs projected performance if improvements are implemented. Output format: A funnel analysis dashboard + improvement recommendation document.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Sales Funnel Drop off Analysis details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":595,"title":"Education Performance Dashboard for Institutions","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are an Education Analytics Specialist. I have school-level student performance data for grades, attendance, and extracurricular participation across multiple branches. Your task: - Create visualisations showing average performance by subject and grade...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Education Performance Dashboard for Institutions\"\n\nStarting brief:\nPrompt 20 — Education Performance Dashboard for Institutions \"You are an Education Analytics Specialist. I have school-level student performance data for grades, attendance, and extracurricular participation across multiple branches. Your task: - Create visualisations showing average performance by subject and grade level. - Add attendance heatmaps highlighting periods of low attendance. - Identify correlations between extracurricular participation and academic performance. - Highlight top 5 branches in overall performance and bottom 5 for improvement focus. - Recommend targeted interventions for low-performing schools. Output format: Dashboard wireframe + insights brief for school management.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Education Performance Dashboard for Institutions details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":596,"title":"Energy Consumption Pattern Analysis for Cost Saving","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are an Energy Data Analyst. I have hourly electricity consumption data for a manufacturing facility over 24 months. Your task: - Identify peak and off-peak consumption periods. - Analyse seasonal patterns in energy usage. - Quantify potential savings...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Energy Consumption Pattern Analysis for Cost Saving\"\n\nStarting brief:\nPrompt 21 — Energy Consumption Pattern Analysis for Cost Saving \"You are an Energy Data Analyst. I have hourly electricity consumption data for a manufacturing facility over 24 months. Your task: - Identify peak and off-peak consumption periods. - Analyse seasonal patterns in energy usage. - Quantify potential savings from shifting operations to off-peak hours. - Suggest renewable energy integration opportunities. - Create a projection model for energy cost savings over the next 12 months. Output format: PDF energy audit report + visual trend charts + savings projection table.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Energy Consumption Pattern Analysis for Cost Saving details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":597,"title":"Market Basket Analysis for Cross Selling","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"Market Basket Analysis for Cross-Selling \"You are a Retail Data Mining Specialist. I have point-of-sale transaction data with item-level details for the past 12 months. Your task: - Use association rule mining (Apriori or FP-Growth) to identify frequent...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Market Basket Analysis for Cross Selling\"\n\nStarting brief:\nPrompt 22 — Market Basket Analysis for Cross-Selling \"You are a Retail Data Mining Specialist. I have point-of-sale transaction data with item-level details for the past 12 months. Your task: - Use association rule mining (Apriori or FP-Growth) to identify frequent item combinations. - Calculate support, confidence, and lift for each rule. - Highlight top 10 product pairs with highest cross-sell potential. - Suggest bundle offers based on analysis. - Project potential revenue increase from implementing top 3 bundles. Output format: Association rules table + actionable cross-sell strategy document.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Market Basket Analysis for Cross Selling details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":598,"title":"Website Traffic and Conversion Analytics","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Advanced","explanation":"\"You are a Web Analytics Consultant. I have Google Analytics data for my e-commerce site over the past 6 months. Your task: - Identify top 5 traffic sources and their respective conversion rates. - Analyse bounce rate, average session duration, and pages...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Website Traffic and Conversion Analytics\"\n\nStarting brief:\nPrompt 23 — Website Traffic and Conversion Analytics \"You are a Web Analytics Consultant. I have Google Analytics data for my e-commerce site over the past 6 months. Your task: - Identify top 5 traffic sources and their respective conversion rates. - Analyse bounce rate, average session duration, and pages per session. - Map the customer journey from landing page to purchase. - Highlight underperforming landing pages and suggest optimisation strategies. - Provide projected improvement metrics if changes are implemented. Output format: Data Studio dashboard layout + optimisation recommendations report.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Website Traffic and Conversion Analytics details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":599,"title":"Manufacturing Process Efficiency Visualisation","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"\"You are a Manufacturing Data Engineer. I have IoT sensor data for multiple machines in a production line over the past year. Your task: - Visualise machine uptime/downtime as a Gantt chart. - Identify bottlenecks in production flow. - Calculate defect...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Manufacturing Process Efficiency Visualisation\"\n\nStarting brief:\nPrompt 24 — Manufacturing Process Efficiency Visualisation \"You are a Manufacturing Data Engineer. I have IoT sensor data for multiple machines in a production line over the past year. Your task: - Visualise machine uptime/downtime as a Gantt chart. - Identify bottlenecks in production flow. - Calculate defect rates per machine and per shift. - Recommend preventive maintenance schedules. - Suggest workflow changes to increase throughput without adding resources. Output format: Factory floor dashboard layout + process improvement plan.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Manufacturing Process Efficiency Visualisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":600,"title":"Financial Performance Storytelling for Investors","category":"CRM & Projects","source":"IT & Data","module":"Data Analysis Visualization","difficulty":"Intermediate","explanation":"\"You are a Financial Data Storyteller. I have quarterly income statements, balance sheets, and cash flow statements for the past 3 years. Your task: - Visualise revenue, gross profit, and net profit trends over time. - Calculate key financial ratios (ROE,...","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Financial Performance Storytelling for Investors\"\n\nStarting brief:\nYou are a Financial Data Storyteller. I have quarterly income statements, balance sheets, and cash flow statements for the past 3 years. Your task: - Visualise revenue, gross profit, and net profit trends over time. - Calculate key financial ratios (ROE, ROA, current ratio, debt-to-equity) and explain their meaning. - Highlight major changes in expenses or revenue sources. - Provide a year-over-year growth summary. - Frame findings in a narrative that inspires investor confidence. Output format: Investor-ready slide deck with visuals, ratio analysis, and growth narrative.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Financial Performance Storytelling for Investors details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":601,"title":"Creating a Step by Step User Guide for a Mobile App","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a User Experience Documentation Specialist. I need you to create a beginner-friendly setup guide for our budgeting mobile app. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating a Step by Step User Guide for a Mobile App\"\n\nStarting brief:\nYou are a User Experience Documentation Specialist. I need you to create a beginner-friendly setup guide for our budgeting mobile app.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating a Step by Step User Guide for a Mobile App details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":602,"title":"Generating API Documentation for a Developer Portal","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Technical API Documentation Expert. I want you to create API docs for our food delivery API. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Generating API Documentation for a Developer Portal\"\n\nStarting brief:\nYou are a Technical API Documentation Expert. I want you to create API docs for our food delivery API.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Generating API Documentation for a Developer Portal details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":603,"title":"Writing Release Notes for a SaaS Platform","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Product Communications Writer. I want you to create release notes for our SaaS analytics platform that both inform and excite customers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Writing Release Notes for a SaaS Platform\"\n\nStarting brief:\nYou are a Product Communications Writer. I want you to create release notes for our SaaS analytics platform that both inform and excite customers.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Writing Release Notes for a SaaS Platform details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":604,"title":"Creating Onboarding Guides for a CRM Tool","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Intermediate","explanation":"You are a CRM Onboarding Documentation Specialist. I want an onboarding manual that helps sales reps transition from spreadsheets to our CRM. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Onboarding Guides for a CRM Tool\"\n\nStarting brief:\nYou are a CRM Onboarding Documentation Specialist. I want an onboarding manual that helps sales reps transition from spreadsheets to our CRM.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Onboarding Guides for a CRM Tool details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":605,"title":"Creating a Knowledge Base Article for a Common Support Issue","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Beginner","explanation":"You are a Knowledge Base Content Specialist. I want you to create a help article for \"How to Reset Your Password\" for our e-commerce platform. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating a Knowledge Base Article for a Common Support Issue\"\n\nStarting brief:\nYou are a Knowledge Base Content Specialist. I want you to create a help article for \"How to Reset Your Password\" for our e-commerce platform.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating a Knowledge Base Article for a Common Support Issue details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":606,"title":"Creating Interactive Tutorials for a Project Management Tool","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Product Education Content Developer. I need you to create in-app interactive tutorials for our project management platform. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Interactive Tutorials for a Project Management Tool\"\n\nStarting brief:\nYou are a Product Education Content Developer. I need you to create in-app interactive tutorials for our project management platform.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Interactive Tutorials for a Project Management Tool details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":607,"title":"Writing Compliance & Policy Documentation","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Regulatory Documentation Specialist. I want you to create compliance and privacy policies for our fintech app. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Writing Compliance & Policy Documentation\"\n\nStarting brief:\nYou are a Regulatory Documentation Specialist. I want you to create compliance and privacy policies for our fintech app.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Writing Compliance & Policy Documentation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":608,"title":"Documenting API Integration for Third Party Partners","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Partner Integration Documentation Engineer. I want you to create a full integration manual for our payment API. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Documenting API Integration for Third Party Partners\"\n\nStarting brief:\nYou are a Partner Integration Documentation Engineer. I want you to create a full integration manual for our payment API.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Documenting API Integration for Third Party Partners details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":609,"title":"Creating Internal Developer Documentation","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Intermediate","explanation":"You are an Internal Engineering Documentation Specialist. I want a central developer handbook for our engineering team. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Internal Developer Documentation\"\n\nStarting brief:\nYou are an Internal Engineering Documentation Specialist. I want a central developer handbook for our engineering team.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Internal Developer Documentation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":610,"title":"Writing Feature Comparison Guides","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Beginner","explanation":"You are a Competitive Product Documentation Writer. I want a feature comparison document between our tool and top 3 competitors. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Writing Feature Comparison Guides\"\n\nStarting brief:\nYou are a Competitive Product Documentation Writer. I want a feature comparison document between our tool and top 3 competitors.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Writing Feature Comparison Guides details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":611,"title":"Creating Troubleshooting Flowcharts","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Technical Troubleshooting Documentation Designer. I want to create visual flowcharts for common problems with our SaaS tool. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Troubleshooting Flowcharts\"\n\nStarting brief:\nYou are a Technical Troubleshooting Documentation Designer. I want to create visual flowcharts for common problems with our SaaS tool.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Troubleshooting Flowcharts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":612,"title":"Creating Voice & Tone Guidelines","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Content Style Guide Specialist. I want a voice & tone guideline document for our documentation team. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Voice & Tone Guidelines\"\n\nStarting brief:\nYou are a Content Style Guide Specialist. I want a voice & tone guideline document for our documentation team.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Voice & Tone Guidelines details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":613,"title":"Writing Contextual Tooltips for a Web Application","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a UX Microcopy Documentation Specialist. I want you to create clear, concise tooltips for our SaaS dashboard. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Writing Contextual Tooltips for a Web Application\"\n\nStarting brief:\nYou are a UX Microcopy Documentation Specialist. I want you to create clear, concise tooltips for our SaaS dashboard.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Writing Contextual Tooltips for a Web Application details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":614,"title":"Creating a Quick Start Guide for a Developer SDK Software Development Kit","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Developer Onboarding Documentation Expert. I want a quick start guide for our JavaScript SDK. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating a Quick Start Guide for a Developer SDK Software Development Kit\"\n\nStarting brief:\nYou are a Developer Onboarding Documentation Expert. I want a quick start guide for our JavaScript SDK.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating a Quick Start Guide for a Developer SDK Software Development Kit details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":615,"title":"Documenting Accessibility Features for Users with Disabilities","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Intermediate","explanation":"You are an Accessibility Documentation Specialist. I want an accessibility features guide for our learning platform. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Documenting Accessibility Features for Users with Disabilities\"\n\nStarting brief:\nYou are an Accessibility Documentation Specialist. I want an accessibility features guide for our learning platform.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Documenting Accessibility Features for Users with Disabilities details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":616,"title":"Creating Interactive FAQs with Search Functionality","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Help Center Experience Designer. I want to turn our static FAQ page into an interactive, searchable database. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Interactive FAQs with Search Functionality\"\n\nStarting brief:\nYou are a Help Center Experience Designer. I want to turn our static FAQ page into an interactive, searchable database.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Interactive FAQs with Search Functionality details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":617,"title":"Writing Maintenance Manuals for Hardware Products","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Hardware Technical Writer. I want a maintenance manual for our smart home thermostat. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Writing Maintenance Manuals for Hardware Products\"\n\nStarting brief:\nYou are a Hardware Technical Writer. I want a maintenance manual for our smart home thermostat.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Writing Maintenance Manuals for Hardware Products details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":618,"title":"Documenting Multi Language Product Instructions","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Multilingual Documentation Specialist. I want product instructions for our kitchen appliance in English, Mandarin, and Malay (with a Tamil version planned next). Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Documenting Multi Language Product Instructions\"\n\nStarting brief:\nYou are a Multilingual Documentation Specialist. I want product instructions for our kitchen appliance in English, Mandarin, and Malay (with a Tamil version planned next).\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Documenting Multi Language Product Instructions details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":619,"title":"Creating How To Videos for Common Tasks","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Beginner","explanation":"You are a Video Documentation Producer. I want 5 short (under 2 mins each) tutorial videos for our e-learning platform. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating How To Videos for Common Tasks\"\n\nStarting brief:\nYou are a Video Documentation Producer. I want 5 short (under 2 mins each) tutorial videos for our e-learning platform.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating How To Videos for Common Tasks details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":620,"title":"Creating an API Changelog Page","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are an API Documentation Manager. I want a live API changelog page for our developer portal. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating an API Changelog Page\"\n\nStarting brief:\nYou are an API Documentation Manager. I want a live API changelog page for our developer portal.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating an API Changelog Page details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":621,"title":"Writing Internal Product Playbooks for Support Staff","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Intermediate","explanation":"You are a Support Operations Documentation Specialist. I want to create internal playbooks for handling common customer issues. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Writing Internal Product Playbooks for Support Staff\"\n\nStarting brief:\nYou are a Support Operations Documentation Specialist. I want to create internal playbooks for handling common customer issues.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Writing Internal Product Playbooks for Support Staff details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":622,"title":"Documenting Integration with Popular Third Party Tools","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are a Third-Party Integration Documentation Specialist. I want guides for integrating our platform with Slack, Google Sheets, and Zapier. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Documenting Integration with Popular Third Party Tools\"\n\nStarting brief:\nYou are a Third-Party Integration Documentation Specialist. I want guides for integrating our platform with Slack, Google Sheets, and Zapier.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Documenting Integration with Popular Third Party Tools details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":623,"title":"Creating Printable Cheat Sheets for Power Users","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Beginner","explanation":"You are a Productivity Documentation Designer. I want a one-page quick reference cheat sheet for our desktop productivity app. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating Printable Cheat Sheets for Power Users\"\n\nStarting brief:\nYou are a Productivity Documentation Designer. I want a one-page quick reference cheat sheet for our desktop productivity app.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating Printable Cheat Sheets for Power Users details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":624,"title":"Creating User Story Based Tutorials","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Beginner","explanation":"You are a Scenario-Based Learning Documentation Specialist. I want tutorials that walk through tasks using real customer scenarios. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating User Story Based Tutorials\"\n\nStarting brief:\nYou are a Scenario-Based Learning Documentation Specialist. I want tutorials that walk through tasks using real customer scenarios.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating User Story Based Tutorials details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":625,"title":"Creating AI Assisted Product Guides","category":"CRM & Projects","source":"IT & Data","module":"Product Documentation User Guides","difficulty":"Advanced","explanation":"You are an AI-Enhanced Documentation Designer. I want a product guide template that AI can fill with user-specific tips. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a project and CRM operations specialist who turns requirements into practical execution steps. Help me create a polished, workplace-ready output for this task:\n\"Creating AI Assisted Product Guides\"\n\nStarting brief:\nYou are an AI-Enhanced Documentation Designer. I want a product guide template that AI can fill with user-specific tips.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a usable project, CRM, automation, or process artifact\n\nMy details:\n- Creating AI Assisted Product Guides details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- business objective\n- system involved\n- stakeholders\n- current workflow\n- constraints or dependencies\n- system or tool name\n- current process or problem\n- users affected\n- security or access constraints\n- definition of done\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the current state, desired state, and measurable success criteria.\n2. Break the work into steps, owners, dependencies, risks, and verification gates.\n3. Include user-facing impact and data/process impact separately.\n4. Suggest a small first implementation slice when the request is broad.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Scope summary\n- Workflow or implementation steps\n- Acceptance criteria\n- Risk and dependency table\n- Verification checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not assume system access, field names, APIs, or approvals. Ask for confirmation where needed.\n- Check security, privacy, permissions, rollback, and user-impact assumptions before acting.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚙️","color":"cat-teal"},{"id":626,"title":"New Lead Welcome & Warm Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a B2B CRM Lead Nurturing Specialist. Create a 4-email welcome and warm-up sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"New Lead Welcome & Warm Up\"\n\nStarting brief:\nYou are a B2B CRM Lead Nurturing Specialist. Create a 4-email welcome and warm-up sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- New Lead Welcome & Warm Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product/service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":627,"title":"Post Event Follow Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are an Event Lead Follow-Up Specialist. Write a 3-email follow-up sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Post Event Follow Up\"\n\nStarting brief:\nYou are an Event Lead Follow-Up Specialist. Write a 3-email follow-up sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Post Event Follow Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Event name & date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":628,"title":"Abandoned Quote Follow Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Sales Recovery Email Expert. Create a 3-email sequence for abandoned quotes that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Abandoned Quote Follow Up\"\n\nStarting brief:\nYou are a Sales Recovery Email Expert. Create a 3-email sequence for abandoned quotes that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Abandoned Quote Follow Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Quote details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":629,"title":"Dormant Client Re Engagement","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a Client Re-Engagement Specialist. Build a 2-email + 1-call sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Dormant Client Re Engagement\"\n\nStarting brief:\nYou are a Client Re-Engagement Specialist. Build a 2-email + 1-call sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Dormant Client Re Engagement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Past services used\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":630,"title":"Post Purchase Upsell Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Post-Purchase CRM Upsell Expert. Design a 3-email upsell sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Post Purchase Upsell Sequence\"\n\nStarting brief:\nYou are a Post-Purchase CRM Upsell Expert. Design a 3-email upsell sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Post Purchase Upsell Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Advanced course details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":631,"title":"Payment Reminder Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a Payment Reminder Specialist. Build a 3-touch reminder sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Payment Reminder Sequence\"\n\nStarting brief:\nYou are a Payment Reminder Specialist. Build a 3-touch reminder sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Payment Reminder Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client name\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":632,"title":"Free Trial Expiry Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Trial Conversion Specialist. Design a 4-email countdown sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Free Trial Expiry Sequence\"\n\nStarting brief:\nYou are a Trial Conversion Specialist. Design a 4-email countdown sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Free Trial Expiry Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Trial length\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":633,"title":"After Sales Support Follow Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Advanced","explanation":"You are a Customer Support Follow-Up Specialist. Write a 3-step follow-up that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"After Sales Support Follow Up\"\n\nStarting brief:\nYou are a Customer Support Follow-Up Specialist. Write a 3-step follow-up that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- After Sales Support Follow Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product model\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":634,"title":"Webinar Attendee Follow Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Webinar Conversion Specialist. Build a 3-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Webinar Attendee Follow Up\"\n\nStarting brief:\nYou are a Webinar Conversion Specialist. Build a 3-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Webinar Attendee Follow Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Webinar topic\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":635,"title":"Lost Deal Follow Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a Lost Deal Recovery Specialist. Create a 2-touch follow-up that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Lost Deal Follow Up\"\n\nStarting brief:\nYou are a Lost Deal Recovery Specialist. Create a 2-touch follow-up that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Lost Deal Follow Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Prospect name\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":636,"title":"High Value Lead Priority Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a High-Ticket CRM Specialist. Design a 5-step sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"High Value Lead Priority Sequence\"\n\nStarting brief:\nYou are a High-Ticket CRM Specialist. Design a 5-step sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- High Value Lead Priority Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Buyer budget range\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":637,"title":"Service Renewal Reminder","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Renewal Retention Specialist. Create a 3-email reminder series that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Service Renewal Reminder\"\n\nStarting brief:\nYou are a Renewal Retention Specialist. Create a 3-email reminder series that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Service Renewal Reminder details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Renewal date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":638,"title":"Client Feedback Collection","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Client Experience Specialist. Write a single follow-up email that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Client Feedback Collection\"\n\nStarting brief:\nYou are a Client Experience Specialist. Write a single follow-up email that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Client Feedback Collection details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client name\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":639,"title":"Seasonal Greeting + Soft Offer","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Festive CRM Outreach Specialist. Write a greeting email that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Seasonal Greeting + Soft Offer\"\n\nStarting brief:\nYou are a Festive CRM Outreach Specialist. Write a greeting email that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Seasonal Greeting + Soft Offer details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Festival name\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":640,"title":"Upsell to Existing Client","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a CRM Upsell Specialist. Build a 2-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Upsell to Existing Client\"\n\nStarting brief:\nYou are a CRM Upsell Specialist. Build a 2-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Upsell to Existing Client details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Existing service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":641,"title":"Upsell After Positive Customer Support Interaction","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Advanced","explanation":"You are a Post-Support Upsell Specialist. Create a 2-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Upsell After Positive Customer Support Interaction\"\n\nStarting brief:\nYou are a Post-Support Upsell Specialist. Create a 2-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Upsell After Positive Customer Support Interaction details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Support ticket summary\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":642,"title":"Client Onboarding Progress Check In","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Advanced","explanation":"You are a Client Success CRM Specialist. Build a 3-touch follow-up that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Client Onboarding Progress Check In\"\n\nStarting brief:\nYou are a Client Success CRM Specialist. Build a 3-touch follow-up that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Client Onboarding Progress Check In details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Onboarding checklist\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":643,"title":"Anniversary or Milestone Celebration","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Customer Relationship Building Specialist. Write a 1-email celebration template that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Anniversary or Milestone Celebration\"\n\nStarting brief:\nYou are a Customer Relationship Building Specialist. Write a 1-email celebration template that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Anniversary or Milestone Celebration details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Milestone type/date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":644,"title":"Post Complaint Satisfaction Follow Up","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a Customer Recovery Specialist. Create a 2-step follow-up that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Post Complaint Satisfaction Follow Up\"\n\nStarting brief:\nYou are a Customer Recovery Specialist. Create a 2-step follow-up that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Post Complaint Satisfaction Follow Up details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Complaint details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":645,"title":"Webinar Non Attendee Nurture Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a Missed Webinar Conversion Specialist. Create a 3-email series that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Webinar Non Attendee Nurture Sequence\"\n\nStarting brief:\nYou are a Missed Webinar Conversion Specialist. Create a 3-email series that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Webinar Non Attendee Nurture Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Webinar topic\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":646,"title":"Follow Up After Free Resource Download","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Lead Magnet Nurture Specialist. Design a 4-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Follow Up After Free Resource Download\"\n\nStarting brief:\nYou are a Lead Magnet Nurture Specialist. Design a 4-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Follow Up After Free Resource Download details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Lead magnet title/link\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":647,"title":"Follow Up After Networking Event","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Intermediate","explanation":"You are a Networking Follow-Up Expert. Write a single email template that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Follow Up After Networking Event\"\n\nStarting brief:\nYou are a Networking Follow-Up Expert. Write a single email template that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Follow Up After Networking Event details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Event name/date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":648,"title":"Follow Up After Service Demo","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Demo Conversion Specialist. Create a 3-email follow-up that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Follow Up After Service Demo\"\n\nStarting brief:\nYou are a Demo Conversion Specialist. Create a 3-email follow-up that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Follow Up After Service Demo details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Demo date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":649,"title":"VIP Client Retention Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a VIP Client Relationship Manager. Build a 3-touch sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"VIP Client Retention Sequence\"\n\nStarting brief:\nYou are a VIP Client Relationship Manager. Build a 3-touch sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- VIP Client Retention Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client travel preferences\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":650,"title":"Renewal Upsell Sequence","category":"Sales & Marketing","source":"Marketing","module":"CRM follow up sequences","difficulty":"Beginner","explanation":"You are a Renewal Upsell Specialist. Design a 3-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Renewal Upsell Sequence\"\n\nStarting brief:\nYou are a Renewal Upsell Specialist. Design a 3-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Renewal Upsell Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Renewal date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":651,"title":"Welcome Email Sequence for New Subscribers","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are an Email Marketing Strategist. Create a 3-email welcome sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Welcome Email Sequence for New Subscribers\"\n\nStarting brief:\nYou are an Email Marketing Strategist. Create a 3-email welcome sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Welcome Email Sequence for New Subscribers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Brand name & USP (Unique Selling Proposition)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":652,"title":"Abandoned Cart Recovery Email Series","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Cart Recovery Email Specialist. Build a 3-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Abandoned Cart Recovery Email Series\"\n\nStarting brief:\nYou are a Cart Recovery Email Specialist. Build a 3-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Abandoned Cart Recovery Email Series details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":653,"title":"Re engagement Campaign for Inactive Subscribers","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are an Email Re-engagement Specialist. Create a 3-email win-back campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Re engagement Campaign for Inactive Subscribers\"\n\nStarting brief:\nYou are an Email Re-engagement Specialist. Create a 3-email win-back campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Re engagement Campaign for Inactive Subscribers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Brand name & offer details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":654,"title":"Festival Themed Promotional Campaign","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Seasonal Email Campaign Specialist. Build a 5-day Chinese New Year email campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Festival Themed Promotional Campaign\"\n\nStarting brief:\nYou are a Seasonal Email Campaign Specialist. Build a 5-day Chinese New Year email campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Festival Themed Promotional Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sale start & end date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":655,"title":"B2B Newsletter for Industry Authority","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a B2B Email Content Strategist. Create a weekly newsletter template that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"B2B Newsletter for Industry Authority\"\n\nStarting brief:\nYou are a B2B Email Content Strategist. Create a weekly newsletter template that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- B2B Newsletter for Industry Authority details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":656,"title":"Educational Email Course","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are an Email Course Designer. Create a 7-day educational email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Educational Email Course\"\n\nStarting brief:\nYou are an Email Course Designer. Create a 7-day educational email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Educational Email Course details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Course topic outline\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":657,"title":"Product Launch Email Sequence","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Product Launch Email Strategist. Build a 5-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Product Launch Email Sequence\"\n\nStarting brief:\nYou are a Product Launch Email Strategist. Build a 5-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Product Launch Email Sequence details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product features & USP\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":658,"title":"Webinar Registration & Reminder Series","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Webinar Email Funnel Expert. Create a 4-email series that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Webinar Registration & Reminder Series\"\n\nStarting brief:\nYou are a Webinar Email Funnel Expert. Create a 4-email series that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Webinar Registration & Reminder Series details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Webinar topic & date\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":659,"title":"Customer Feedback Request Emails","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Customer Feedback Email Specialist. Write a 2-email feedback request campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Customer Feedback Request Emails\"\n\nStarting brief:\nYou are a Customer Feedback Email Specialist. Write a 2-email feedback request campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Customer Feedback Request Emails details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":660,"title":"Upsell Email Campaign","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are an Upsell Email Strategist. Build a 3-email upsell sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Upsell Email Campaign\"\n\nStarting brief:\nYou are an Upsell Email Strategist. Build a 3-email upsell sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Upsell Email Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Basic vs premium features\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":661,"title":"Festival Giveaway Email Campaign","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Giveaway Email Campaign Specialist. Create a 3-email giveaway sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Festival Giveaway Email Campaign\"\n\nStarting brief:\nYou are a Giveaway Email Campaign Specialist. Create a 3-email giveaway sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Festival Giveaway Email Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Giveaway prize details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":662,"title":"Cross Sell Email Campaign","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Cross-Sell Email Specialist. Build a 2-email campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Cross Sell Email Campaign\"\n\nStarting brief:\nYou are a Cross-Sell Email Specialist. Build a 2-email campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Cross Sell Email Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Past purchase history\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":663,"title":"Loyalty Program Onboarding Series","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Loyalty Program Email Specialist. Create a 3-email onboarding series that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Loyalty Program Onboarding Series\"\n\nStarting brief:\nYou are a Loyalty Program Email Specialist. Create a 3-email onboarding series that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Loyalty Program Onboarding Series details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Loyalty program details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":664,"title":"Monthly Newsletter with Industry Insights","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a B2B Newsletter Writer. Create a monthly email newsletter that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Monthly Newsletter with Industry Insights\"\n\nStarting brief:\nYou are a B2B Newsletter Writer. Create a monthly email newsletter that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Monthly Newsletter with Industry Insights details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":665,"title":"Refill Reminder Email for Consumable Products","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Product Refill Email Specialist. Build a 2-email reminder sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Refill Reminder Email for Consumable Products\"\n\nStarting brief:\nYou are a Product Refill Email Specialist. Build a 2-email reminder sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Refill Reminder Email for Consumable Products details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product refill cycle\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":666,"title":"Seasonal Product Clearance Sale","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Seasonal Sales Email Expert. Create a 4-email clearance campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Seasonal Product Clearance Sale\"\n\nStarting brief:\nYou are a Seasonal Sales Email Expert. Create a 4-email clearance campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Seasonal Product Clearance Sale details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Discount percentage\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":667,"title":"Customer Onboarding for SaaS","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a SaaS Onboarding Email Specialist. Build a 5-email sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Customer Onboarding for SaaS\"\n\nStarting brief:\nYou are a SaaS Onboarding Email Specialist. Build a 5-email sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Customer Onboarding for SaaS details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Key SaaS features\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":668,"title":"Thank You Email for First Purchase","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Customer Loyalty Email Specialist. Write a single thank-you email that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Thank You Email for First Purchase\"\n\nStarting brief:\nYou are a Customer Loyalty Email Specialist. Write a single thank-you email that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Thank You Email for First Purchase details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Customer first name\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":669,"title":"Early Access VIP Sale","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a VIP Campaign Email Strategist. Build a 2-email early access campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Early Access VIP Sale\"\n\nStarting brief:\nYou are a VIP Campaign Email Strategist. Build a 2-email early access campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Early Access VIP Sale details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Discount percentage\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":670,"title":"Post Purchase Upsell Series","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Post-Purchase Email Strategist. Create a 3-email upsell sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Post Purchase Upsell Series\"\n\nStarting brief:\nYou are a Post-Purchase Email Strategist. Create a 3-email upsell sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Post Purchase Upsell Series details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Purchased product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":671,"title":"Milestone Celebration Email","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Customer Milestone Email Specialist. Write a celebratory email that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Milestone Celebration Email\"\n\nStarting brief:\nYou are a Customer Milestone Email Specialist. Write a celebratory email that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Milestone Celebration Email details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Milestone type\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":672,"title":"Flash Sale Announcement","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Flash Sale Email Specialist. Build a 2-email flash sale sequence that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Flash Sale Announcement\"\n\nStarting brief:\nYou are a Flash Sale Email Specialist. Build a 2-email flash sale sequence that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Flash Sale Announcement details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sale start/end time\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":673,"title":"Event Invitation Email","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are an  Specialist. Write a single email that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Event Invitation Email\"\n\nStarting brief:\nYou are an Event Invitation Email Specialist. Write a single email that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Event Invitation Email details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Event details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":674,"title":"Survey Participation Email","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Survey Email Specialist. Create an email that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Survey Participation Email\"\n\nStarting brief:\nYou are a Survey Email Specialist. Create an email that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Survey Participation Email details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Survey link\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":675,"title":"Holiday Greeting Email","category":"Sales & Marketing","source":"Marketing","module":"Email Marketing Campaigns","difficulty":"Intermediate","explanation":"You are a Corporate Greetings Email Specialist. Write a festive holiday greeting that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Holiday Greeting Email\"\n\nStarting brief:\nYou are a Corporate Greetings Email Specialist. Write a festive holiday greeting that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Holiday Greeting Email details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Company name\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":676,"title":"High CTR Ad Copy for a New Product Launch","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are a Performance Ad Copywriter. Write 5 ad copy variants for my product launch that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"High CTR Ad Copy for a New Product Launch\"\n\nStarting brief:\nYou are a Performance Ad Copywriter. Write 5 ad copy variants for my product launch that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- High CTR Ad Copy for a New Product Launch details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product name: [Insert]\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":677,"title":"Targeting Strategy for First Time Home Buyers","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Paid Ads Targeting Expert. Design a targeting strategy for first-time home buyers that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Targeting Strategy for First Time Home Buyers\"\n\nStarting brief:\nYou are a Paid Ads Targeting Expert. Design a targeting strategy for first-time home buyers that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Targeting Strategy for First Time Home Buyers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Location: [Insert]\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":678,"title":"Ad Copy Testing Plan for Multiple Audiences","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are an A/B Testing Specialist. Build an ad copy testing plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Ad Copy Testing Plan for Multiple Audiences\"\n\nStarting brief:\nYou are an A/B Testing Specialist. Build an ad copy testing plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Ad Copy Testing Plan for Multiple Audiences details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Audience profiles\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":679,"title":"Festival Campaign Ad Ideas","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Festival Campaign Specialist. For my jewellery store, create ad copy and targeting ideas that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Festival Campaign Ad Ideas\"\n\nStarting brief:\nYou are a Festival Campaign Specialist. For my jewellery store, create ad copy and targeting ideas that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Festival Campaign Ad Ideas details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":680,"title":"Retargeting Campaign Copy & Targeting","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Advanced","explanation":"You are a Retargeting Campaign Strategist. Design a retargeting campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Retargeting Campaign Copy & Targeting\"\n\nStarting brief:\nYou are a Retargeting Campaign Strategist. Design a retargeting campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Retargeting Campaign Copy & Targeting details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Website analytics data\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":681,"title":"Location Based Ad Targeting for Local Businesses","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Local Ads Targeting Specialist. Build a campaign for my café that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Location Based Ad Targeting for Local Businesses\"\n\nStarting brief:\nYou are a Local Ads Targeting Specialist. Build a campaign for my café that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Location Based Ad Targeting for Local Businesses details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Location coordinates\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":682,"title":"Emotional Storytelling in Ad Copy","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Storytelling Ad Copy Expert. Write ad copy for my campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Emotional Storytelling in Ad Copy\"\n\nStarting brief:\nYou are a Storytelling Ad Copy Expert. Write ad copy for my campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Emotional Storytelling in Ad Copy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Cause details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":683,"title":"Competitor Ad Analysis & Replication","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Competitor Ads Analyst. Analyse my competitors' ads and create a plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Competitor Ad Analysis & Replication\"\n\nStarting brief:\nYou are a Competitor Ads Analyst. Analyse my competitors' ads and create a plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Competitor Ad Analysis & Replication details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Competitor names/links\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":684,"title":"Ad Copy for Different Stages of Buyer Journey","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are a Buyer Journey Ad Strategist. Create ad copy for each stage that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Ad Copy for Different Stages of Buyer Journey\"\n\nStarting brief:\nYou are a Buyer Journey Ad Strategist. Create ad copy for each stage that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Ad Copy for Different Stages of Buyer Journey details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":685,"title":"Split Testing Ad Headlines for Maximum CTR","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Headline Testing Specialist. Create 10 ad headline variations for my campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Split Testing Ad Headlines for Maximum CTR\"\n\nStarting brief:\nYou are a Headline Testing Specialist. Create 10 ad headline variations for my campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Split Testing Ad Headlines for Maximum CTR details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Campaign goal\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":686,"title":"Multi Language Ad Copy for Indian Markets","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Multilingual Ad Copy Expert. Write ad copy for my campaign in English, Mandarin, Malay, and Tamil that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Multi Language Ad Copy for Indian Markets\"\n\nStarting brief:\nYou are a Multilingual Ad Copy Expert. Write ad copy for my campaign in English, Mandarin, Malay, and Tamil that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Multi Language Ad Copy for Indian Markets details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product/service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":687,"title":"Ads for Lead Generation Funnels","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are a Lead Generation Ads Strategist. Create ad copy and targeting ideas that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Ads for Lead Generation Funnels\"\n\nStarting brief:\nYou are a Lead Generation Ads Strategist. Create ad copy and targeting ideas that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Ads for Lead Generation Funnels details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Business niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":688,"title":"Crisis or Urgent Sales Campaign Ads","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are an Urgency Ad Specialist. Build ads that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Crisis or Urgent Sales Campaign Ads\"\n\nStarting brief:\nYou are an Urgency Ad Specialist. Build ads that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Crisis or Urgent Sales Campaign Ads details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":689,"title":"Video Script Ideas for Facebook/YouTube Ads","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are a Video Ad Script Writer. Write 3 video ad scripts that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Video Script Ideas for Facebook/YouTube Ads\"\n\nStarting brief:\nYou are a Video Ad Script Writer. Write 3 video ad scripts that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Video Script Ideas for Facebook/YouTube Ads details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product features\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":690,"title":"Carousel Ad Copy for Product Catalogues","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are a Carousel Ads Specialist. Write copy for each carousel card that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Carousel Ad Copy for Product Catalogues\"\n\nStarting brief:\nYou are a Carousel Ads Specialist. Write copy for each carousel card that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Carousel Ad Copy for Product Catalogues details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product list\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":691,"title":"Google Responsive Search Ads Plan","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Advanced","explanation":"You are a Google RSA Copy Specialist. Build a list of: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Google Responsive Search Ads Plan\"\n\nStarting brief:\nYou are a Google RSA Copy Specialist. Build a list of:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Google Responsive Search Ads Plan details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service area\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":692,"title":"Ad Copy for Retargeting Abandoned Carts","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Beginner","explanation":"You are a Cart Recovery Ad Expert. Create 5 ad copy variations that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Ad Copy for Retargeting Abandoned Carts\"\n\nStarting brief:\nYou are a Cart Recovery Ad Expert. Create 5 ad copy variations that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Ad Copy for Retargeting Abandoned Carts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Cart product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":693,"title":"Ads for High Value Client Acquisition","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Luxury Marketing Ad Specialist. Build a campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Ads for High Value Client Acquisition\"\n\nStarting brief:\nYou are a Luxury Marketing Ad Specialist. Build a campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Ads for High Value Client Acquisition details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":694,"title":"Festival Specific Ad Targeting Playbook","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Festival Ads Planner. For my business, create: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Festival Specific Ad Targeting Playbook\"\n\nStarting brief:\nYou are a Festival Ads Planner. For my business, create:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Festival Specific Ad Targeting Playbook details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product categories\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":695,"title":"Lookalike Audience Expansion Strategy","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Lookalike Audience Specialist. Create a plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Lookalike Audience Expansion Strategy\"\n\nStarting brief:\nYou are a Lookalike Audience Specialist. Create a plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Lookalike Audience Expansion Strategy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current audience data\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":696,"title":"Copy for Seasonal Sales Clearance","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Clearance Campaign Expert. Write ad copy that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Copy for Seasonal Sales Clearance\"\n\nStarting brief:\nYou are a Clearance Campaign Expert. Write ad copy that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Copy for Seasonal Sales Clearance details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product types\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":697,"title":"Ads for App Install Campaigns","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are an App Marketing Specialist. Build ads that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Ads for App Install Campaigns\"\n\nStarting brief:\nYou are an App Marketing Specialist. Build ads that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Ads for App Install Campaigns details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- App features\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":698,"title":"Crisis PR Ad Campaign","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Brand Reputation Ads Specialist. Create an ad campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Crisis PR Ad Campaign\"\n\nStarting brief:\nYou are a Brand Reputation Ads Specialist. Create an ad campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Crisis PR Ad Campaign details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Positive customer reviews\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":699,"title":"Dynamic Ads for Real Time Inventory","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Advanced","explanation":"You are a Dynamic Ads Expert. Create a strategy for event ticket ads that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Dynamic Ads for Real Time Inventory\"\n\nStarting brief:\nYou are a Dynamic Ads Expert. Create a strategy for event ticket ads that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Dynamic Ads for Real Time Inventory details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Event details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":700,"title":"Full Funnel Ad Campaign Blueprint","category":"Sales & Marketing","source":"Marketing","module":"Facebook Google ad Copy Targeting Ideas","difficulty":"Intermediate","explanation":"You are a Full-Funnel Ads Strategist. Build a campaign that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Full Funnel Ad Campaign Blueprint\"\n\nStarting brief:\nYou are a Full-Funnel Ads Strategist. Build a campaign that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Full Funnel Ad Campaign Blueprint details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":701,"title":"Foundational SEO Keyword Research for a New Blog","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an SEO Research Strategist. Based on my blog niche and target audience, perform keyword research that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Foundational SEO Keyword Research for a New Blog\"\n\nStarting brief:\nYou are an SEO Research Strategist. Based on my blog niche and target audience, perform keyword research that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Foundational SEO Keyword Research for a New Blog details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog topic/niche: Sustainable living in Singapore\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":702,"title":"Blog Content Calendar Based on Keyword Clusters","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Keyword Clustering & Content Planning Expert. Based on my keyword list, create a blog content calendar that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Blog Content Calendar Based on Keyword Clusters\"\n\nStarting brief:\nYou are a Keyword Clustering & Content Planning Expert. Based on my keyword list, create a blog content calendar that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Blog Content Calendar Based on Keyword Clusters details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Keyword list (Excel/CSV)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":703,"title":"Competitor Gap Analysis for SEO Advantage","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an SEO Gap Analysis Specialist. Analyse the top 5 competitors in my niche and: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Competitor Gap Analysis for SEO Advantage\"\n\nStarting brief:\nYou are an SEO Gap Analysis Specialist. Analyse the top 5 competitors in my niche and:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Competitor Gap Analysis for SEO Advantage details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Competitor URLs (list)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":704,"title":"SEO Strategy for Evergreen vs. Trending Content","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Content Lifecycle SEO Planner. Create a keyword strategy that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"SEO Strategy for Evergreen vs. Trending Content\"\n\nStarting brief:\nYou are a Content Lifecycle SEO Planner. Create a keyword strategy that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- SEO Strategy for Evergreen vs. Trending Content details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche: Personal finance in Singapore (CPF, HDB, BTO\n- investing\n- tax via IRAS)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":705,"title":"Local SEO Keyword Optimisation for Blog Posts","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Local SEO Keyword Strategist. For my travel blog, create a local SEO plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Local SEO Keyword Optimisation for Blog Posts\"\n\nStarting brief:\nYou are a Local SEO Keyword Strategist. For my travel blog, create a local SEO plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Local SEO Keyword Optimisation for Blog Posts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of target destinations (e.g.\n- Sentosa, JB\n- Bintan\n- Batam\n- Penang, KL\n- Bali)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":706,"title":"Long Tail Keyword Strategy for Fast Ranking","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Long-Tail SEO Specialist. For my blog niche, create a long-tail keyword strategy that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Long Tail Keyword Strategy for Fast Ranking\"\n\nStarting brief:\nYou are a Long-Tail SEO Specialist. For my blog niche, create a long-tail keyword strategy that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Long Tail Keyword Strategy for Fast Ranking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche & audience profile (Singapore-based working professionals, HDB-friendly home setups)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":707,"title":"Seasonal Keyword Calendar for Singapore Festivals","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Seasonal SEO Planner. Create a festival keyword calendar that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Seasonal Keyword Calendar for Singapore Festivals\"\n\nStarting brief:\nYou are a Seasonal SEO Planner. Create a festival keyword calendar that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Seasonal Keyword Calendar for Singapore Festivals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche: DIY crafts & décor\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":708,"title":"Keyword Mapping for Blog Categories","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an SEO Category Mapping Expert. For my blog, create a keyword map that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Keyword Mapping for Blog Categories\"\n\nStarting brief:\nYou are an SEO Category Mapping Expert. For my blog, create a keyword map that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Keyword Mapping for Blog Categories details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog categories list\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":709,"title":"Blog Post SEO Blueprint for a New Keyword","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an SEO Blog Post Architect. For the keyword [insert keyword], create a post blueprint that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Blog Post SEO Blueprint for a New Keyword\"\n\nStarting brief:\nYou are an SEO Blog Post Architect. For the keyword [insert keyword], create a post blueprint that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Blog Post SEO Blueprint for a New Keyword details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Target keyword\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":710,"title":"Competitive SERP Analysis for Keyword Ranking","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a SERP Competitor Analyst. For the keyword [insert keyword], analyse: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Competitive SERP Analysis for Keyword Ranking\"\n\nStarting brief:\nYou are a SERP Competitor Analyst. For the keyword [insert keyword], analyse:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Competitive SERP Analysis for Keyword Ranking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Keyword to analyse\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":711,"title":"Keyword Strategy for Voice Search Optimisation","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Voice Search SEO Specialist. For my blog niche, create a keyword strategy that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Keyword Strategy for Voice Search Optimisation\"\n\nStarting brief:\nYou are a Voice Search SEO Specialist. For my blog niche, create a keyword strategy that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Keyword Strategy for Voice Search Optimisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":712,"title":"Keyword Prioritisation Based on ROI Potential","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Advanced","explanation":"You are an SEO ROI Analyst. Prioritise my keyword list by: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Keyword Prioritisation Based on ROI Potential\"\n\nStarting brief:\nYou are an SEO ROI Analyst. Prioritise my keyword list by:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Keyword Prioritisation Based on ROI Potential details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Keyword list (Excel)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":713,"title":"Evergreen Blog Series Plan from Keywords","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an Evergreen Content Planner. Based on my keyword list, create a 10-part blog series that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Evergreen Blog Series Plan from Keywords\"\n\nStarting brief:\nYou are an Evergreen Content Planner. Based on my keyword list, create a 10-part blog series that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Evergreen Blog Series Plan from Keywords details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Keyword list (Excel)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":714,"title":"Blog Re Optimisation Using New Keywords","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Content Refresh Strategist. For my existing blog posts, suggest: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Blog Re Optimisation Using New Keywords\"\n\nStarting brief:\nYou are a Content Refresh Strategist. For my existing blog posts, suggest:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Blog Re Optimisation Using New Keywords details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- List of blog URLs\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":715,"title":"Keyword Strategy for Niche Micro Topics","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Micro-Niche SEO Specialist. For my niche, identify: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Keyword Strategy for Niche Micro Topics\"\n\nStarting brief:\nYou are a Micro-Niche SEO Specialist. For my niche, identify:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Keyword Strategy for Niche Micro Topics details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Main niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":716,"title":"Backlink Keyword Strategy for Blog Growth","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Backlink SEO Strategist. Based on my niche, identify: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Backlink Keyword Strategy for Blog Growth\"\n\nStarting brief:\nYou are a Backlink SEO Strategist. Based on my niche, identify:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Backlink Keyword Strategy for Blog Growth details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":717,"title":"Low Competition, High Intent Keywords","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Keyword Intent Analyst. Create a keyword list that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Low Competition, High Intent Keywords\"\n\nStarting brief:\nYou are a Keyword Intent Analyst. Create a keyword list that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Low Competition, High Intent Keywords details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Business niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":718,"title":"Multilingual Keyword Strategy for Singapore Markets","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Multilingual SEO Planner. For my blog, create a keyword plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Multilingual Keyword Strategy for Singapore Markets\"\n\nStarting brief:\nYou are a Multilingual SEO Planner. For my blog, create a keyword plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Multilingual Keyword Strategy for Singapore Markets details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":719,"title":"Evergreen & Trending Keyword Mix for YouTube Integration","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Advanced","explanation":"You are a Cross-Platform SEO Strategist. Create a keyword plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Evergreen & Trending Keyword Mix for YouTube Integration\"\n\nStarting brief:\nYou are a Cross-Platform SEO Strategist. Create a keyword plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Evergreen & Trending Keyword Mix for YouTube Integration details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":720,"title":"Internal Linking Opportunities from Keyword Clusters","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an Internal Linking SEO Specialist. Based on my keyword clusters, create an internal linking map that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Internal Linking Opportunities from Keyword Clusters\"\n\nStarting brief:\nYou are an Internal Linking SEO Specialist. Based on my keyword clusters, create an internal linking map that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Internal Linking Opportunities from Keyword Clusters details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Keyword cluster list\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":721,"title":"Featured Snippet Targeting with Keywords","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Featured Snippet Optimisation Expert. For my blog, identify: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Featured Snippet Targeting with Keywords\"\n\nStarting brief:\nYou are a Featured Snippet Optimisation Expert. For my blog, identify:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Featured Snippet Targeting with Keywords details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":722,"title":"Keyword Strategy for Google Discover","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Google Discover SEO Strategist. For my niche, create a Discover-optimised plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Keyword Strategy for Google Discover\"\n\nStarting brief:\nYou are a Google Discover SEO Strategist. For my niche, create a Discover-optimised plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Keyword Strategy for Google Discover details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":723,"title":"Keyword Strategy for Affiliate Blog Monetisation","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are an Affiliate SEO Strategist. For my blog, identify: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Keyword Strategy for Affiliate Blog Monetisation\"\n\nStarting brief:\nYou are an Affiliate SEO Strategist. For my blog, identify:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Keyword Strategy for Affiliate Blog Monetisation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Affiliate products/services list\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":724,"title":"SERP Volatility Tracking for Keywords","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Advanced","explanation":"You are a SERP Volatility Analyst. For my keyword list, create a tracking plan that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"SERP Volatility Tracking for Keywords\"\n\nStarting brief:\nYou are a SERP Volatility Analyst. For my keyword list, create a tracking plan that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- SERP Volatility Tracking for Keywords details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Keyword list (Excel)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":725,"title":"Evergreen SEO Growth Plan for 12 Months","category":"Sales & Marketing","source":"Marketing","module":"SEO Keyword Research Blog Planning","difficulty":"Intermediate","explanation":"You are a Long-Term SEO Planner. Build a keyword-based SEO roadmap that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Evergreen SEO Growth Plan for 12 Months\"\n\nStarting brief:\nYou are a Long-Term SEO Planner. Build a keyword-based SEO roadmap that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Evergreen SEO Growth Plan for 12 Months details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Blog niche\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":726,"title":"Custom Pitch Deck for B2B SaaS Product","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a B2B SaaS Pitch Deck Expert. Create a 12-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Custom Pitch Deck for B2B SaaS Product\"\n\nStarting brief:\nYou are a B2B SaaS Pitch Deck Expert. Create a 12-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Custom Pitch Deck for B2B SaaS Product details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry type (e.g.\n- manufacturing\n- retail)\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":727,"title":"Investor Pitch for Early Stage Startup","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Startup Pitch Advisor. Build a 10-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Investor Pitch for Early Stage Startup\"\n\nStarting brief:\nYou are a Startup Pitch Advisor. Build a 10-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Investor Pitch for Early Stage Startup details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Market research data\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":728,"title":"Objection Handling: “Your Price is Too High”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Sales Objection Handling Coach. Draft a 5-step objection handling script for the price objection that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “Your Price is Too High”\"\n\nStarting brief:\nYou are a Sales Objection Handling Coach. Draft a 5-step objection handling script for the price objection that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “Your Price is Too High” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":729,"title":"Pitch Deck for Strategic Partnerships","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Partnership Proposal Expert. Create a 7-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Strategic Partnerships\"\n\nStarting brief:\nYou are a Partnership Proposal Expert. Create a 7-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Strategic Partnerships details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Sales data\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":730,"title":"Objection Handling: “We Already Have a Vendor”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Competitive Replacement Specialist. Write a 4-step objection handling script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We Already Have a Vendor”\"\n\nStarting brief:\nYou are a Competitive Replacement Specialist. Write a 4-step objection handling script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We Already Have a Vendor” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service differentiators\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":731,"title":"Pitch Deck for Nonprofit Fundraising","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Nonprofit Fundraising Strategist. Create an 8-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Nonprofit Fundraising\"\n\nStarting brief:\nYou are a Nonprofit Fundraising Strategist. Create an 8-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Nonprofit Fundraising details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Impact data\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":732,"title":"Objection Handling: “We Don’t Have the Budget Right Now”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Budget Cycle Sales Coach. Build a 3-step script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We Don’t Have the Budget Right Now”\"\n\nStarting brief:\nYou are a Budget Cycle Sales Coach. Build a 3-step script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We Don’t Have the Budget Right Now” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service packages\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":733,"title":"Product Launch Pitch for Media","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Tech Product PR Specialist. Build a 6-slide press pitch deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Product Launch Pitch for Media\"\n\nStarting brief:\nYou are a Tech Product PR Specialist. Build a 6-slide press pitch deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Product Launch Pitch for Media details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product specs\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":734,"title":"Objection Handling: “I Need to Think About It”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Sales Conversation Strategist. Draft a 5-step framework that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “I Need to Think About It”\"\n\nStarting brief:\nYou are a Sales Conversation Strategist. Draft a 5-step framework that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “I Need to Think About It” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":735,"title":"Internal Team Sales Training Deck","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Sales Enablement Coach. Create a 10-slide internal training deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Internal Team Sales Training Deck\"\n\nStarting brief:\nYou are a Sales Enablement Coach. Create a 10-slide internal training deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Internal Team Sales Training Deck details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product/service list\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":736,"title":"Pitch Deck for Government Contracts","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Advanced","explanation":"You are a GovTech Pitch Specialist. Build a 9-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Government Contracts\"\n\nStarting brief:\nYou are a GovTech Pitch Specialist. Build a 9-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Government Contracts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Certification details\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":737,"title":"Objection Handling: “We’re Happy With Current Results”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are an SEO Growth Consultant. Create a 4-step objection handling script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We’re Happy With Current Results”\"\n\nStarting brief:\nYou are an SEO Growth Consultant. Create a 4-step objection handling script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We’re Happy With Current Results” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current SEO report\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":738,"title":"Pitch Deck for Cross Selling to Existing Clients","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Cross-Sell Pitch Specialist. Build a 6-slide mini deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Cross Selling to Existing Clients\"\n\nStarting brief:\nYou are a Cross-Sell Pitch Specialist. Build a 6-slide mini deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Cross Selling to Existing Clients details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- Pitch Deck for Cross Selling to Existing Clients details\n- audience or stakeholder\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":739,"title":"Objection Handling: “We’ve Tried This Before and It Didn’t Work”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Program Repositioning Expert. Draft a 5-step objection handling script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We’ve Tried This Before and It Didn’t Work”\"\n\nStarting brief:\nYou are a Program Repositioning Expert. Draft a 5-step objection handling script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We’ve Tried This Before and It Didn’t Work” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Differentiators in your program\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":740,"title":"Pitch Deck for Selling to C Suite Executives","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Advanced","explanation":"You are a C-Suite Sales Strategist. Build a 10-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Selling to C Suite Executives\"\n\nStarting brief:\nYou are a C-Suite Sales Strategist. Build a 10-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Selling to C Suite Executives details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Risk reduction stats\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":741,"title":"Objection Handling: “I Need Approval From My Boss”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Champion Enablement Coach. Build a toolkit that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “I Need Approval From My Boss”\"\n\nStarting brief:\nYou are a Champion Enablement Coach. Build a toolkit that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “I Need Approval From My Boss” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product features\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":742,"title":"Pitch Deck for Selling at Trade Shows","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Trade Show Sales Expert. Create a 5-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Selling at Trade Shows\"\n\nStarting brief:\nYou are a Trade Show Sales Expert. Create a 5-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Selling at Trade Shows details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Product images/videos\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":743,"title":"Objection Handling: “We’re in Contract With Someone Else”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Future Positioning Sales Coach. Draft a 3-step script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We’re in Contract With Someone Else”\"\n\nStarting brief:\nYou are a Future Positioning Sales Coach. Draft a 3-step script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We’re in Contract With Someone Else” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Service advantages\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":744,"title":"Pitch Deck for Selling to International Clients","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Advanced","explanation":"You are an International Sales Strategist. Create an 8-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Selling to International Clients\"\n\nStarting brief:\nYou are an International Sales Strategist. Create an 8-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Selling to International Clients details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Project case studies\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":745,"title":"Objection Handling: “It’s Not a Priority Right Now”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Advanced","explanation":"You are a Urgency Reframing Expert. Build a 4-step script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “It’s Not a Priority Right Now”\"\n\nStarting brief:\nYou are a Urgency Reframing Expert. Build a 4-step script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “It’s Not a Priority Right Now” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Case studies\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":746,"title":"Pitch Deck for Upselling Existing Enterprise Clients","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are an Enterprise Upsell Strategist. Create a 7-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Upselling Existing Enterprise Clients\"\n\nStarting brief:\nYou are an Enterprise Upsell Strategist. Create a 7-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Upselling Existing Enterprise Clients details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Client usage report\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":747,"title":"Objection Handling: “We’ve Heard Bad Reviews About Your Industry”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Beginner","explanation":"You are a Reputation Rebuilding Specialist. Draft a 4-step objection script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We’ve Heard Bad Reviews About Your Industry”\"\n\nStarting brief:\nYou are a Reputation Rebuilding Specialist. Draft a 4-step objection script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We’ve Heard Bad Reviews About Your Industry” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Ethical practices list\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":748,"title":"Pitch Deck for Selling to Educational Institutions","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Advanced","explanation":"You are an EduTech Sales Specialist. Build a 9-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Selling to Educational Institutions\"\n\nStarting brief:\nYou are an EduTech Sales Specialist. Build a 9-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Selling to Educational Institutions details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Outcome data\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":749,"title":"Objection Handling: “We’re Too Busy to Implement This”","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Intermediate","explanation":"You are a Low-Effort Implementation Strategist. Create a 3-step script that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Objection Handling: “We’re Too Busy to Implement This”\"\n\nStarting brief:\nYou are a Low-Effort Implementation Strategist. Create a 3-step script that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Objection Handling: “We’re Too Busy to Implement This” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Setup process timeline\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":750,"title":"Pitch Deck for Selling to Non Tech Founders","category":"Sales & Marketing","source":"Marketing","module":"Sales pitch decks objection handling","difficulty":"Advanced","explanation":"You are a Non-Technical Founder Sales Expert. Create an 8-slide deck that: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a sales and marketing strategist who connects audience insight to clear action. Help me create a polished, workplace-ready output for this task:\n\"Pitch Deck for Selling to Non Tech Founders\"\n\nStarting brief:\nYou are a Non-Technical Founder Sales Expert. Create an 8-slide deck that:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a campaign, message, pitch, or analysis that can be tested and improved\n\nMy details:\n- Pitch Deck for Selling to Non Tech Founders details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Process outline\n- target persona\n- product or offer\n- channel\n- proof points\n- success metric\n- target audience\n- offer or message\n- brand tone\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Define the audience, pain point, promise, proof, and call to action.\n2. Create message options for different awareness levels or objections.\n3. Connect the output to a measurable next step.\n4. Add a simple test plan or improvement loop.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Core message\n- Channel-ready draft or campaign asset\n- Audience and objection notes\n- A/B test or variation ideas\n- Measurement checklist\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid exaggerated claims. Mark proof points, offers, prices, and compliance-sensitive wording for review.\n- Check claims, brand fit, compliance, audience relevance, and whether the call to action is specific.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"📣","color":"cat-indigo"},{"id":751,"title":"Morning Abundance Affirmations Inspired by Indian Spiritual Texts","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a spiritual content creator. Draft 15 short morning affirmations inspired by the Bhagavad Gita, Upanishads, and Indian spiritual thought. They should be positive, easy to repeat, and focused on gratitude, abundance, and self-worth. Copy-ready...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Morning Abundance Affirmations Inspired by Indian Spiritual Texts\"\n\nStarting brief:\nYou are a spiritual content creator. Draft 15 short morning affirmations inspired by the Bhagavad Gita, Upanishads, and Indian spiritual thought. They should be positive, easy to repeat, and focused on gratitude, abundance, and self-worth.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Morning Abundance Affirmations Inspired by Indian Spiritual Texts details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- User's preferred language (English/Tamil/mix)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":752,"title":"Visualization Script for Achieving Career Goals Using Sankalpa Principle","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a meditation guide. Write a detailed 10-minute guided visualization script based on the yogic principle of Sankalpa. Tailor it for a 28-year-old preparing for a major professional qualification exam, focusing on calm confidence, sharp focus, and...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization Script for Achieving Career Goals Using Sankalpa Principle\"\n\nStarting brief:\nYou are a meditation guide. Write a detailed 10-minute guided visualization script based on the yogic principle of Sankalpa. Tailor it for a 28-year-old preparing for a major professional qualification exam, focusing on calm confidence, sharp focus, and belief in success.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization Script for Achieving Career Goals Using Sankalpa Principle details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exam date\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":753,"title":"Healing Heartbreak Affirmations Using Bhakti Tradition","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a spiritual mentor. Create 12 short, compassionate affirmations inspired by the Bhakti tradition and stories of divine love, to help a young woman heal from heartbreak and rediscover trust in life. Copy-ready prompt with placeholders, task steps,...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Healing Heartbreak Affirmations Using Bhakti Tradition\"\n\nStarting brief:\nYou are a spiritual mentor. Create 12 short, compassionate affirmations inspired by the Bhakti tradition and stories of divine love, to help a young woman heal from heartbreak and rediscover trust in life.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Healing Heartbreak Affirmations Using Bhakti Tradition details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Religious/spiritual background\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":754,"title":"Visualization Exercise for Health Recovery with Ayurveda Imagery","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are an Ayurvedic wellness coach. Write a 15-minute guided visualization exercise using Ayurvedic imagery to help a 45-year-old man imagine restoring his body's balance, vitality, and energy. Copy-ready prompt with placeholders, task steps, output...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization Exercise for Health Recovery with Ayurveda Imagery\"\n\nStarting brief:\nYou are an Ayurvedic wellness coach. Write a 15-minute guided visualization exercise using Ayurvedic imagery to help a 45-year-old man imagine restoring his body's balance, vitality, and energy.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization Exercise for Health Recovery with Ayurveda Imagery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Dominant dosha imbalance (Vata\n- Pitta\n- or Kapha)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":755,"title":"Affirmations for Overcoming Self Doubt Using Gita s Karma Yoga Teachings","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a motivational coach. Write 10 daily affirmations inspired by Karma Yoga from the Bhagavad Gita to help a 35-year-old business owner overcome self-doubt and focus on consistent action. Copy-ready prompt with placeholders, task steps, output format,...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Overcoming Self Doubt Using Gita s Karma Yoga Teachings\"\n\nStarting brief:\nYou are a motivational coach. Write 10 daily affirmations inspired by Karma Yoga from the Bhagavad Gita to help a 35-year-old business owner overcome self-doubt and focus on consistent action.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Overcoming Self Doubt Using Gita s Karma Yoga Teachings details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of business\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":756,"title":"Affirmations for Students Before Exams Using Saraswati Vandana Themes","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are an educational wellness coach. Create 12 exam-day affirmations inspired by the themes of Goddess Saraswati that help students stay calm, focused, and confident during their exams. Copy-ready prompt with placeholders, task steps, output format, and...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Students Before Exams Using Saraswati Vandana Themes\"\n\nStarting brief:\nYou are an educational wellness coach. Create 12 exam-day affirmations inspired by the themes of Goddess Saraswati that help students stay calm, focused, and confident during their exams.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Students Before Exams Using Saraswati Vandana Themes details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Subject focus\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":757,"title":"Visualization for Attracting the Right Life Partner Using Indian Astrology Imager","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a spiritual coach. Create a 15-minute guided visualization for attracting a life partner, using Indian astrology imagery and compatibility principles. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Attracting the Right Life Partner Using Indian Astrology Imager\"\n\nStarting brief:\nYou are a spiritual coach. Create a 15-minute guided visualization for attracting a life partner, using Indian astrology imagery and compatibility principles.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Attracting the Right Life Partner Using Indian Astrology Imager details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Birth date\n- time\n- place\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":758,"title":"Affirmations for Financial Abundance Using Lakshmi Mantra Energy","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a wealth mindset coach. Write 15 affirmations for financial abundance inspired by Goddess Lakshmi, using a positive, grateful tone. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Financial Abundance Using Lakshmi Mantra Energy\"\n\nStarting brief:\nYou are a wealth mindset coach. Write 15 affirmations for financial abundance inspired by Goddess Lakshmi, using a positive, grateful tone.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Financial Abundance Using Lakshmi Mantra Energy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current financial goal\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":759,"title":"Visualization for Healing Family Relationships Using Ramayana s Values","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a meditation guide. Write a 12-minute guided visualization for healing family relationships using values and imagery from the Ramayana. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Healing Family Relationships Using Ramayana s Values\"\n\nStarting brief:\nYou are a meditation guide. Write a 12-minute guided visualization for healing family relationships using values and imagery from the Ramayana.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Healing Family Relationships Using Ramayana s Values details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Relationship to heal\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":760,"title":"Affirmations for Overcoming Career Stress Using Yogic Breathing","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a mindfulness trainer. Write 10 affirmations that can be silently repeated during yogic breathing (Anulom Vilom, Bhramari) to reduce stress and promote focus. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Overcoming Career Stress Using Yogic Breathing\"\n\nStarting brief:\nYou are a mindfulness trainer. Write 10 affirmations that can be silently repeated during yogic breathing (Anulom Vilom, Bhramari) to reduce stress and promote focus.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Overcoming Career Stress Using Yogic Breathing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Nature of work stress\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":761,"title":"Visualization for Attracting Dream Job Using Indian Temple Imagery","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a manifestation coach. Create a 10-minute dream job visualization using Indian temple rituals, light, and offering imagery. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Attracting Dream Job Using Indian Temple Imagery\"\n\nStarting brief:\nYou are a manifestation coach. Create a 10-minute dream job visualization using Indian temple rituals, light, and offering imagery.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Attracting Dream Job Using Indian Temple Imagery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Target company/role\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":762,"title":"Affirmations for Boosting Self Confidence Using Mahabharata Lessons","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a personal development coach. Write 12 affirmations for self-confidence inspired by key moments in the Mahabharata, especially Arjuna's transformation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Boosting Self Confidence Using Mahabharata Lessons\"\n\nStarting brief:\nYou are a personal development coach. Write 12 affirmations for self-confidence inspired by key moments in the Mahabharata, especially Arjuna's transformation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Boosting Self Confidence Using Mahabharata Lessons details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Field of work/study\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":763,"title":"Visualization for Peaceful Sleep Using Panchatatva Elements","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a sleep meditation coach. Write a 15-minute guided visualization using the five elements (earth, water, fire, air, space) to help someone fall asleep peacefully. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Peaceful Sleep Using Panchatatva Elements\"\n\nStarting brief:\nYou are a sleep meditation coach. Write a 15-minute guided visualization using the five elements (earth, water, fire, air, space) to help someone fall asleep peacefully.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Peaceful Sleep Using Panchatatva Elements details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Favourite natural element\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":764,"title":"Affirmations for Overcoming Fear of Public Speaking Using Vedic Chant Energy","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a confidence coach. Write 10 affirmations with the rhythm and energy of Vedic chants to help overcome fear of public speaking. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Overcoming Fear of Public Speaking Using Vedic Chant Energy\"\n\nStarting brief:\nYou are a confidence coach. Write 10 affirmations with the rhythm and energy of Vedic chants to help overcome fear of public speaking.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Overcoming Fear of Public Speaking Using Vedic Chant Energy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of presentations\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":765,"title":"Visualization for Weight Loss Motivation Using Yogic Body Awareness","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a wellness coach. Write a 12-minute guided visualization using yogic body awareness to encourage healthy eating, regular exercise, and self-compassion. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Weight Loss Motivation Using Yogic Body Awareness\"\n\nStarting brief:\nYou are a wellness coach. Write a 12-minute guided visualization using yogic body awareness to encourage healthy eating, regular exercise, and self-compassion.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Weight Loss Motivation Using Yogic Body Awareness details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current fitness routine\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":766,"title":"Affirmations for Self Worth Using Devi Durga Archetypes","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a spiritual self-worth coach. Write 12 affirmations for women to rebuild confidence and self-esteem inspired by Devi Durga's archetypes and qualities. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Self Worth Using Devi Durga Archetypes\"\n\nStarting brief:\nYou are a spiritual self-worth coach. Write 12 affirmations for women to rebuild confidence and self-esteem inspired by Devi Durga's archetypes and qualities.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Self Worth Using Devi Durga Archetypes details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of challenge faced\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":767,"title":"Visualization for Letting Go of Past Mistakes Using Ganga River Imagery","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a meditation teacher. Write a 15-minute guided visualization using the Ganga River's imagery to release guilt and welcome new opportunities. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Letting Go of Past Mistakes Using Ganga River Imagery\"\n\nStarting brief:\nYou are a meditation teacher. Write a 15-minute guided visualization using the Ganga River's imagery to release guilt and welcome new opportunities.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Letting Go of Past Mistakes Using Ganga River Imagery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Specific past events to let go\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":768,"title":"Affirmations for Resilience During Job Search Using Hanuman s Determination","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a career resilience coach. Write 10 affirmations for job seekers inspired by Hanuman's determination and strength. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Resilience During Job Search Using Hanuman s Determination\"\n\nStarting brief:\nYou are a career resilience coach. Write 10 affirmations for job seekers inspired by Hanuman's determination and strength.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Resilience During Job Search Using Hanuman s Determination details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of job sought\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":769,"title":"Visualization for Gratitude Practice Using Indian Festival Imagery","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Advanced","explanation":"You are a gratitude coach. Create a 12-minute guided visualization for daily gratitude practice using imagery from Indian festivals like Deepavali or Pongal. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Gratitude Practice Using Indian Festival Imagery\"\n\nStarting brief:\nYou are a gratitude coach. Create a 12-minute guided visualization for daily gratitude practice using imagery from Indian festivals like Deepavali or Pongal.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Gratitude Practice Using Indian Festival Imagery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Favourite festival\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":770,"title":"Affirmations for Daily Energy Boost Using Surya Namaskar Inspiration","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a wellness coach. Write 10 morning affirmations inspired by Surya Namaskar to boost daily energy and mental clarity. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Daily Energy Boost Using Surya Namaskar Inspiration\"\n\nStarting brief:\nYou are a wellness coach. Write 10 morning affirmations inspired by Surya Namaskar to boost daily energy and mental clarity.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Daily Energy Boost Using Surya Namaskar Inspiration details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current morning routine\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":771,"title":"Visualization for Overcoming Fear of Change Using Koi Fish River Symbolism","category":"Meetings","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a life transition coach. Write a 15-minute guided visualization using koi fish and flowing river symbolism to inspire courage during major life changes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Overcoming Fear of Change Using Koi Fish River Symbolism\"\n\nStarting brief:\nYou are a life transition coach. Write a 15-minute guided visualization using koi fish and flowing river symbolism to inspire courage during major life changes.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Visualization for Overcoming Fear of Change Using Koi Fish River Symbolism details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of change happening\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":772,"title":"Affirmations for Healthy Boundaries Using Indian Proverb Wisdom","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a self-care coach. Write 12 affirmations for healthy boundaries inspired by Indian proverbs and folk wisdom. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Healthy Boundaries Using Indian Proverb Wisdom\"\n\nStarting brief:\nYou are a self-care coach. Write 12 affirmations for healthy boundaries inspired by Indian proverbs and folk wisdom.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Healthy Boundaries Using Indian Proverb Wisdom details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Common boundary challenges\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":773,"title":"Visualization for Emotional Healing After Breakup Using Lotus Bloom Imagery","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a meditation guide. Write a 12-minute guided visualization using lotus bloom imagery to help heal emotional wounds after a breakup. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Emotional Healing After Breakup Using Lotus Bloom Imagery\"\n\nStarting brief:\nYou are a meditation guide. Write a 12-minute guided visualization using lotus bloom imagery to help heal emotional wounds after a breakup.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Emotional Healing After Breakup Using Lotus Bloom Imagery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Relationship duration\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":774,"title":"Affirmations for Weight Management Motivation Using Ayurveda Dosha Balance","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a wellness and Ayurveda coach. Write 10 affirmations for weight management inspired by Ayurvedic dosha balance principles. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Affirmations for Weight Management Motivation Using Ayurveda Dosha Balance\"\n\nStarting brief:\nYou are a wellness and Ayurveda coach. Write 10 affirmations for weight management inspired by Ayurvedic dosha balance principles.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Affirmations for Weight Management Motivation Using Ayurveda Dosha Balance details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Dosha type (Vata / Pitta / Kapha)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":775,"title":"Visualization for Career Clarity Using Himalayan Sunrise Imagery","category":"Productivity","source":"Personal Growth","module":"Affirmations visualisation exercises","difficulty":"Beginner","explanation":"You are a career clarity coach. Write a 15-minute guided visualization using Himalayan sunrise imagery to help professionals find direction in their careers. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Visualization for Career Clarity Using Himalayan Sunrise Imagery\"\n\nStarting brief:\nYou are a career clarity coach. Write a 15-minute guided visualization using Himalayan sunrise imagery to help professionals find direction in their careers.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Visualization for Career Clarity Using Himalayan Sunrise Imagery details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current job role\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":776,"title":"Prompt 1 – Morning Gratitude Meditation for Busy Professionals","category":"Meetings","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a mindfulness coach specializing in workplace well-being. Write a 7-minute guided meditation script for busy Singaporean professionals that helps them start their day with gratitude. Copy-ready prompt with placeholders, task steps, output format,...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 1 – Morning Gratitude Meditation for Busy Professionals\"\n\nStarting brief:\nYou are a mindfulness coach specializing in workplace well-being. Write a 7-minute guided meditation script for busy Singaporean professionals that helps them start their day with gratitude.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 1 – Morning Gratitude Meditation for Busy Professionals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration preference (in minutes)\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":777,"title":"Prompt 2 – Sleep Induction Meditation for Overthinkers","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Advanced","explanation":"You are a certified sleep therapist and meditation guide. Create a 10-minute sleep induction meditation for people who overthink at night. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 2 – Sleep Induction Meditation for Overthinkers\"\n\nStarting brief:\nYou are a certified sleep therapist and meditation guide. Create a 10-minute sleep induction meditation for people who overthink at night.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 2 – Sleep Induction Meditation for Overthinkers details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age group of the listener\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":778,"title":"Prompt 3 – Guided Meditation for Exam Stress Relief","category":"Meetings","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a mental wellness mentor for students. Write a 5-minute guided meditation script that helps reduce exam anxiety and improves focus. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 3 – Guided Meditation for Exam Stress Relief\"\n\nStarting brief:\nYou are a mental wellness mentor for students. Write a 5-minute guided meditation script that helps reduce exam anxiety and improves focus.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 3 – Guided Meditation for Exam Stress Relief details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exam type (PSLE, O-Level, A-Level\n- university finals\n- etc.)\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":779,"title":"Prompt 4 – Full Moon Release Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a spiritual life coach with knowledge of Asian cultural practices found in Singapore. Write a 12-minute guided meditation for emotional release during the full moon. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 4 – Full Moon Release Meditation\"\n\nStarting brief:\nYou are a spiritual life coach with knowledge of Asian cultural practices found in Singapore. Write a 12-minute guided meditation for emotional release during the full moon.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 4 – Full Moon Release Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Emotional theme (letting go of anger\n- sadness\n- guilt\n- etc.)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":780,"title":"Prompt 5 – Body Scan Meditation for Corporate Employees","category":"Meetings","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a workplace wellness trainer. Develop a 15-minute guided body scan meditation for corporate employees. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 5 – Body Scan Meditation for Corporate Employees\"\n\nStarting brief:\nYou are a workplace wellness trainer. Develop a 15-minute guided body scan meditation for corporate employees.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 5 – Body Scan Meditation for Corporate Employees details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration (10–20 minutes)\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":781,"title":"Prompt 6 – Inner Child Healing Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a trauma-informed mindfulness facilitator. Write a 15-minute guided meditation for inner child healing. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 6 – Inner Child Healing Meditation\"\n\nStarting brief:\nYou are a trauma-informed mindfulness facilitator. Write a 15-minute guided meditation for inner child healing.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 6 – Inner Child Healing Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age to focus on\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":782,"title":"Prompt 7 – Chakra Balancing Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a meditation teacher trained in energy healing. Create a 20-minute guided meditation for balancing the seven chakras. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 7 – Chakra Balancing Meditation\"\n\nStarting brief:\nYou are a meditation teacher trained in energy healing. Create a 20-minute guided meditation for balancing the seven chakras.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 7 – Chakra Balancing Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration preference\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":783,"title":"Prompt 8 – Grounding Meditation for Anxiety","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a mental health mindfulness coach. Create a 10-minute guided grounding meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 8 – Grounding Meditation for Anxiety\"\n\nStarting brief:\nYou are a mental health mindfulness coach. Create a 10-minute guided grounding meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 8 – Grounding Meditation for Anxiety details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Preferred natural imagery\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":784,"title":"Prompt 9 – Heart Centered Loving Kindness Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a compassion-focused meditation facilitator. Write a 12-minute guided loving-kindness meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 9 – Heart Centered Loving Kindness Meditation\"\n\nStarting brief:\nYou are a compassion-focused meditation facilitator. Write a 12-minute guided loving-kindness meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 9 – Heart Centered Loving Kindness Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Groups to focus compassion on\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":785,"title":"Prompt 10 – Meditation for Manifestation and Goal Alignment","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Intermediate","explanation":"You are a manifestation coach blending modern mindset work with yogic spiritual philosophy. Write a 15-minute guided meditation for manifestation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 10 – Meditation for Manifestation and Goal Alignment\"\n\nStarting brief:\nYou are a manifestation coach blending modern mindset work with yogic spiritual philosophy. Write a 15-minute guided meditation for manifestation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 10 – Meditation for Manifestation and Goal Alignment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of goal (career\n- health\n- relationships)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":786,"title":"Prompt 11 – Morning Gratitude Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a mindfulness teacher blending modern gratitude practice with Asian traditions found in Singapore. Write an 8-minute morning guided meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 11 – Morning Gratitude Meditation\"\n\nStarting brief:\nYou are a mindfulness teacher blending modern gratitude practice with Asian traditions found in Singapore. Write an 8-minute morning guided meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 11 – Morning Gratitude Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration preference\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":787,"title":"Prompt 12 – Sleep Inducing Deep Relaxation Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a relaxation coach specializing in sleep hygiene. Create a 20-minute guided meditation for sleep. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 12 – Sleep Inducing Deep Relaxation Meditation\"\n\nStarting brief:\nYou are a relaxation coach specializing in sleep hygiene. Create a 20-minute guided meditation for sleep.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 12 – Sleep Inducing Deep Relaxation Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":788,"title":"Prompt 13 – Meditation for Emotional Release and Forgiveness","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are an emotional healing facilitator. Write a 15-minute guided forgiveness meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 13 – Meditation for Emotional Release and Forgiveness\"\n\nStarting brief:\nYou are an emotional healing facilitator. Write a 15-minute guided forgiveness meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 13 – Meditation for Emotional Release and Forgiveness details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Relationship context (family\n- work\n- self)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":789,"title":"Prompt 14 – Mindful Eating Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a wellness coach integrating mindfulness into daily routines. Write a 10-minute mindful eating meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 14 – Mindful Eating Meditation\"\n\nStarting brief:\nYou are a wellness coach integrating mindfulness into daily routines. Write a 10-minute mindful eating meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 14 – Mindful Eating Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Meal type (breakfast\n- lunch\n- dinner)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":790,"title":"Prompt 15 – Meditation for Resilience During Challenges","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a resilience coach. Create a 12-minute guided meditation for overcoming challenges. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 15 – Meditation for Resilience During Challenges\"\n\nStarting brief:\nYou are a resilience coach. Create a 12-minute guided meditation for overcoming challenges.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 15 – Meditation for Resilience During Challenges details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of challenge (career\n- health\n- relationships)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":791,"title":"Prompt 16 – Meditation for Letting Go of Overthinking","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a meditation coach focusing on mental clarity. Write a 15-minute guided meditation for letting go of overthinking. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 16 – Meditation for Letting Go of Overthinking\"\n\nStarting brief:\nYou are a meditation coach focusing on mental clarity. Write a 15-minute guided meditation for letting go of overthinking.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 16 – Meditation for Letting Go of Overthinking details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration preference\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":792,"title":"Prompt 17 – Chakra Balancing Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a yoga teacher creating a 20-minute guided chakra-balancing meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 17 – Chakra Balancing Meditation\"\n\nStarting brief:\nYou are a yoga teacher creating a 20-minute guided chakra-balancing meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 17 – Chakra Balancing Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Level of explanation (beginner/advanced)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":793,"title":"Prompt 18 – Self Love & Inner Confidence Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a life coach creating a 12-minute guided self-love meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 18 – Self Love & Inner Confidence Meditation\"\n\nStarting brief:\nYou are a life coach creating a 12-minute guided self-love meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 18 – Self Love & Inner Confidence Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":794,"title":"Prompt 19 – Stress Relief in Traffic Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a mindfulness trainer. Write a 5-minute guided meditation for stress relief during traffic jams or crowded commutes. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 19 – Stress Relief in Traffic Meditation\"\n\nStarting brief:\nYou are a mindfulness trainer. Write a 5-minute guided meditation for stress relief during traffic jams or crowded commutes.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 19 – Stress Relief in Traffic Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":795,"title":"Prompt 20 – Meditation for Exam Anxiety","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are an academic wellness coach. Write a 10-minute guided meditation for reducing exam stress. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 20 – Meditation for Exam Anxiety\"\n\nStarting brief:\nYou are an academic wellness coach. Write a 10-minute guided meditation for reducing exam stress.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 20 – Meditation for Exam Anxiety details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exam type\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":796,"title":"Prompt 21 – Morning Energy Boost Meditation","category":"Meetings","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a wellness coach. Create an 8-minute guided meditation for boosting morning energy. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 21 – Morning Energy Boost Meditation\"\n\nStarting brief:\nYou are a wellness coach. Create an 8-minute guided meditation for boosting morning energy.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 21 – Morning Energy Boost Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Breathwork inclusion (yes/no)\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":797,"title":"Prompt 22 – Mindfulness for Workplace Focus","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a corporate wellness facilitator. Write a 7-minute mindfulness meditation for workplace focus. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 22 – Mindfulness for Workplace Focus\"\n\nStarting brief:\nYou are a corporate wellness facilitator. Write a 7-minute mindfulness meditation for workplace focus.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 22 – Mindfulness for Workplace Focus details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":798,"title":"Prompt 23 – Guided Meditation for Grief Healing","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Intermediate","explanation":"You are a grief counselor. Write a 15-minute guided meditation for processing grief. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 23 – Guided Meditation for Grief Healing\"\n\nStarting brief:\nYou are a grief counselor. Write a 15-minute guided meditation for processing grief.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 23 – Guided Meditation for Grief Healing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Relationship to the loss\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":799,"title":"Prompt 24 – Meditation for Creative Inspiration","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a creativity coach. Write a 12-minute guided meditation for unlocking creative potential. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 24 – Meditation for Creative Inspiration\"\n\nStarting brief:\nYou are a creativity coach. Write a 12-minute guided meditation for unlocking creative potential.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 24 – Meditation for Creative Inspiration details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Creative field\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":800,"title":"Prompt 25 – Evening Reflection & Release Meditation","category":"Productivity","source":"Personal Growth","module":"Guided meditation scripts","difficulty":"Beginner","explanation":"You are a mindfulness trainer. Write a 10-minute guided evening reflection meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 25 – Evening Reflection & Release Meditation\"\n\nStarting brief:\nYou are a mindfulness trainer. Write a 10-minute guided evening reflection meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 25 – Evening Reflection & Release Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":801,"title":"Manifesting Career Growth through Sankalpa Practice","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Spiritual Coach specializing in yogic manifestation practices. Design a 6-week sankalpa-based manifestation routine for a 27-year-old software developer based in Singapore who wants career growth. Include morning affirmations, visualization...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Career Growth through Sankalpa Practice\"\n\nStarting brief:\nYou are a Spiritual Coach specializing in yogic manifestation practices. Design a 6-week sankalpa-based manifestation routine for a 27-year-old software developer based in Singapore who wants career growth. Include morning affirmations, visualization meditations, action steps, and gratitude practices. Integrate teachings from Bhagavad Gita and yoga philosophy. Suggest ways to measure signs of alignment and progress.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Career Growth through Sankalpa Practice details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current job role & skills\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":802,"title":"Financial Abundance using Lakshmi Sadhana","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Intermediate","explanation":"You are a Wealth Manifestation Mentor blending Vedic abundance practices with business coaching. Create a 3-month Lakshmi Sadhana plan for a Singapore-based boutique owner to attract financial stability and growth. Include morning rituals, chanting...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Financial Abundance using Lakshmi Sadhana\"\n\nStarting brief:\nYou are a Wealth Manifestation Mentor blending Vedic abundance practices with business coaching. Create a 3-month Lakshmi Sadhana plan for a Singapore-based boutique owner to attract financial stability and growth. Include morning rituals, chanting schedules, mindful money habits, and actionable business steps. Recommend ways to track both financial and energetic shifts.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Financial Abundance using Lakshmi Sadhana details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current monthly revenue\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":803,"title":"Relationship Manifestation using Bhakti Yoga","category":"Meetings","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Relationship Manifestation Coach with expertise in Bhakti Yoga. Create a 40-day daily routine for a 29-year-old marketing professional based in Singapore to attract a committed partner. Include heart-opening meditations, devotional chanting, acts...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Relationship Manifestation using Bhakti Yoga\"\n\nStarting brief:\nYou are a Relationship Manifestation Coach with expertise in Bhakti Yoga. Create a 40-day daily routine for a 29-year-old marketing professional based in Singapore to attract a committed partner. Include heart-opening meditations, devotional chanting, acts of kindness, and self-love rituals. Suggest practical steps for meeting like-minded people while staying energetically aligned.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Relationship Manifestation using Bhakti Yoga details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Desired partner qualities\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":804,"title":"Manifesting Health Goals through Ayurveda Visualization","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Health Manifestation Specialist blending Ayurveda with Law of Attraction principles. Create a 30-day plan for a 25-year-old fashion student to improve digestion, boost energy, and develop healthy habits. Include daily affirmations, meal...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Health Goals through Ayurveda Visualization\"\n\nStarting brief:\nYou are a Health Manifestation Specialist blending Ayurveda with Law of Attraction principles. Create a 30-day plan for a 25-year-old fashion student to improve digestion, boost energy, and develop healthy habits. Include daily affirmations, meal recommendations based on dosha, visualization exercises, and small lifestyle tweaks.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Health Goals through Ayurveda Visualization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current health issues\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":805,"title":"Career Change Manifestation using Karma Yoga","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Life Purpose Coach integrating Karma Yoga principles. Create a 12-month manifestation plan for a 32-year-old banker in Singapore who wants to move into environmental policy. Include goal clarity exercises, networking strategies, skill-building...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Career Change Manifestation using Karma Yoga\"\n\nStarting brief:\nYou are a Life Purpose Coach integrating Karma Yoga principles. Create a 12-month manifestation plan for a 32-year-old banker in Singapore who wants to move into environmental policy. Include goal clarity exercises, networking strategies, skill-building steps, and daily gratitude/karma practices to attract aligned opportunities.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Career Change Manifestation using Karma Yoga details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current career & skills\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":806,"title":"Confidence Manifestation through Solar Plexus Chakra Work","category":"Meetings","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Chakra & Manifestation Coach. Create a 21-day Solar Plexus healing and manifestation program for a 26-year-old content creator in Singapore. Include breathwork, affirmations, guided meditations, posture improvement, and daily action challenges...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Confidence Manifestation through Solar Plexus Chakra Work\"\n\nStarting brief:\nYou are a Chakra & Manifestation Coach. Create a 21-day Solar Plexus healing and manifestation program for a 26-year-old content creator in Singapore. Include breathwork, affirmations, guided meditations, posture improvement, and daily action challenges for building self-belief.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Confidence Manifestation through Solar Plexus Chakra Work details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current confidence challenges\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":807,"title":"Manifesting Peaceful Living through Minimalism Aparigraha","category":"Meetings","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Mindfulness Mentor specializing in yogic living. Create a 60-day minimalism and Aparigraha-based manifestation program for a 28-year-old in Singapore. Include decluttering rituals, gratitude journaling, mindful spending practices, and...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Peaceful Living through Minimalism Aparigraha\"\n\nStarting brief:\nYou are a Mindfulness Mentor specializing in yogic living. Create a 60-day minimalism and Aparigraha-based manifestation program for a 28-year-old in Singapore. Include decluttering rituals, gratitude journaling, mindful spending practices, and visualization exercises for a simpler, happier lifestyle.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Manifesting Peaceful Living through Minimalism Aparigraha details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current living situation\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":808,"title":"Manifesting Study Success using Mantra Meditation","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are an Academic Performance Coach using Indian spiritual practices. Create a mantra meditation routine for a 23-year-old university student in Singapore to improve focus and reduce stress. Recommend specific mantras, meditation timings, visualization...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Study Success using Mantra Meditation\"\n\nStarting brief:\nYou are an Academic Performance Coach using Indian spiritual practices. Create a mantra meditation routine for a 23-year-old university student in Singapore to improve focus and reduce stress. Recommend specific mantras, meditation timings, visualization for exam success, and tracking methods for study efficiency.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Study Success using Mantra Meditation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exam date & schedule\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":809,"title":"Manifesting Public Speaking Confidence using Vedic Breathing","category":"Meetings","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Public Speaking Coach integrating Vedic breathing techniques. Create a 2-month manifestation program for a 31-year-old manager to overcome stage fright. Include pranayama exercises, visualization, positive affirmations, and mock practice...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Public Speaking Confidence using Vedic Breathing\"\n\nStarting brief:\nYou are a Public Speaking Coach integrating Vedic breathing techniques. Create a 2-month manifestation program for a 31-year-old manager to overcome stage fright. Include pranayama exercises, visualization, positive affirmations, and mock practice sessions.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Manifesting Public Speaking Confidence using Vedic Breathing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Type of presentation\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":810,"title":"Manifesting Entrepreneurial Success using Navagraha Energy Alignment","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Business & Spiritual Alignment Coach. Create a 90-day manifestation plan for a 29-year-old startup founder using Navagraha energy alignment. Suggest personalized rituals, affirmations, action steps, and mindset shifts based on planetary...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Entrepreneurial Success using Navagraha Energy Alignment\"\n\nStarting brief:\nYou are a Business & Spiritual Alignment Coach. Create a 90-day manifestation plan for a 29-year-old startup founder using Navagraha energy alignment. Suggest personalized rituals, affirmations, action steps, and mindset shifts based on planetary influences.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Entrepreneurial Success using Navagraha Energy Alignment details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Birth details for astrology\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":811,"title":"Manifesting Peaceful Relationships through Nonviolent Communication Ahimsa","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Relationship Energy Coach blending Ahimsa with Nonviolent Communication. Create a 30-day manifestation plan for a 33-year-old HR professional in Singapore to attract harmony in her relationships. Include daily reflection exercises, communication...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Peaceful Relationships through Nonviolent Communication Ahimsa\"\n\nStarting brief:\nYou are a Relationship Energy Coach blending Ahimsa with Nonviolent Communication. Create a 30-day manifestation plan for a 33-year-old HR professional in Singapore to attract harmony in her relationships. Include daily reflection exercises, communication scripts, and intentional gratitude practices.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Peaceful Relationships through Nonviolent Communication Ahimsa details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Common conflict triggers\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":812,"title":"Manifesting Overseas Job Offers using Spiritual Travel Visualization","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Career Manifestation Coach using Indian visualization techniques. Create a 90-day plan for a 28-year-old architect in Singapore to manifest an overseas job. Include guided imagery scripts, application schedules, affirmations, and rituals aligned...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Overseas Job Offers using Spiritual Travel Visualization\"\n\nStarting brief:\nYou are a Career Manifestation Coach using Indian visualization techniques. Create a 90-day plan for a 28-year-old architect in Singapore to manifest an overseas job. Include guided imagery scripts, application schedules, affirmations, and rituals aligned with the energy of travel and opportunity.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Overseas Job Offers using Spiritual Travel Visualization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Target countries\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":813,"title":"Manifesting Self Discipline through Gita Teachings","category":"Meetings","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Personal Growth Mentor using Bhagavad Gita wisdom. Create a 45-day manifestation program for a 25-year-old law student to develop discipline in studies. Include daily reading assignments, reflection prompts, meditation, and measurable milestones....","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Self Discipline through Gita Teachings\"\n\nStarting brief:\nYou are a Personal Growth Mentor using Bhagavad Gita wisdom. Create a 45-day manifestation program for a 25-year-old law student to develop discipline in studies. Include daily reading assignments, reflection prompts, meditation, and measurable milestones.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Manifesting Self Discipline through Gita Teachings details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Academic schedule\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":814,"title":"Manifesting a Successful Side Business with Saraswati Lakshmi Energy Balance","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Creative Business Manifestation Coach blending Indian goddess archetypes. Create a 6-month plan for a 30-year-old engineer in Singapore to launch a profitable digital art side business. Include creative exercises, wealth attraction rituals, and...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting a Successful Side Business with Saraswati Lakshmi Energy Balance\"\n\nStarting brief:\nYou are a Creative Business Manifestation Coach blending Indian goddess archetypes. Create a 6-month plan for a 30-year-old engineer in Singapore to launch a profitable digital art side business. Include creative exercises, wealth attraction rituals, and marketing actions.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting a Successful Side Business with Saraswati Lakshmi Energy Balance details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current creative skills\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":815,"title":"Manifesting Marriage Proposals through Auspicious Timing Intention Setting","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Intermediate","explanation":"You are a Spiritual Matchmaking Coach. Create a marriage manifestation plan for a 29-year-old woman in Singapore using muhurta, intention-setting, and practical matchmaking actions. Include affirmations, family involvement tips, and ways to attract...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Marriage Proposals through Auspicious Timing Intention Setting\"\n\nStarting brief:\nYou are a Spiritual Matchmaking Coach. Create a marriage manifestation plan for a 29-year-old woman in Singapore using muhurta, intention-setting, and practical matchmaking actions. Include affirmations, family involvement tips, and ways to attract proposals aligned with her values.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Marriage Proposals through Auspicious Timing Intention Setting details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Desired partner traits\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":816,"title":"Manifesting Inner Peace through Daily Ganga Arati Visualization","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Mindfulness Guide specializing in Indian sacred rituals. Create a 30-day Ganga Aarti-inspired manifestation plan for a corporate professional to attract peace and emotional balance. Include visualization scripts, sound meditation, and gratitude...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Inner Peace through Daily Ganga Arati Visualization\"\n\nStarting brief:\nYou are a Mindfulness Guide specializing in Indian sacred rituals. Create a 30-day Ganga Aarti-inspired manifestation plan for a corporate professional to attract peace and emotional balance. Include visualization scripts, sound meditation, and gratitude journaling.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Inner Peace through Daily Ganga Arati Visualization details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Daily free time\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":817,"title":"Manifesting Dream Home through Vastu Energy Clearing","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Vastu & Manifestation Consultant. Create a 6-month manifestation roadmap for a 27-year-old freelancer to attract her dream home. Include intention-setting rituals, Vastu adjustments in her current living space, and financial preparation steps....","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Dream Home through Vastu Energy Clearing\"\n\nStarting brief:\nYou are a Vastu & Manifestation Consultant. Create a 6-month manifestation roadmap for a 27-year-old freelancer to attract her dream home. Include intention-setting rituals, Vastu adjustments in her current living space, and financial preparation steps.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Dream Home through Vastu Energy Clearing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Desired location & budget\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":818,"title":"Manifesting Career Awards through Gratitude Public Recognition Energy","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Career Recognition Coach using manifestation principles. Create a 24-month plan for a chef to attract industry awards. Include gratitude journaling, public relations actions, community involvement, and self-affirmations. Copy-ready prompt with...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Career Awards through Gratitude Public Recognition Energy\"\n\nStarting brief:\nYou are a Career Recognition Coach using manifestation principles. Create a 24-month plan for a chef to attract industry awards. Include gratitude journaling, public relations actions, community involvement, and self-affirmations.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Career Awards through Gratitude Public Recognition Energy details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current achievements\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":819,"title":"Manifesting Freedom from Debt through Energetic Clearing Money Discipline","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Money Mindset Coach using Indian spiritual wealth practices. Create a 12-month plan to help a 28-year-old teacher in Singapore clear debt. Include energy-clearing rituals, mantras, budget discipline strategies, and manifestation exercises....","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Freedom from Debt through Energetic Clearing Money Discipline\"\n\nStarting brief:\nYou are a Money Mindset Coach using Indian spiritual wealth practices. Create a 12-month plan to help a 28-year-old teacher in Singapore clear debt. Include energy-clearing rituals, mantras, budget discipline strategies, and manifestation exercises.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Freedom from Debt through Energetic Clearing Money Discipline details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Total debt amount\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":820,"title":"Manifesting Better Health through Panchakarma Positive Imaging","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Health Manifestation Guide integrating Ayurveda and visualization. Create a 90-day plan for a 32-year-old with chronic pain, including Panchakarma preparation, daily positive imaging, and gentle movement practices. Copy-ready prompt with...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Better Health through Panchakarma Positive Imaging\"\n\nStarting brief:\nYou are a Health Manifestation Guide integrating Ayurveda and visualization. Create a 90-day plan for a 32-year-old with chronic pain, including Panchakarma preparation, daily positive imaging, and gentle movement practices.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Better Health through Panchakarma Positive Imaging details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Medical restrictions\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":821,"title":"Manifesting Academic Success through Saraswati Vandana Study Flow Rituals","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Intermediate","explanation":"You are an Academic Success Coach integrating Indian spiritual rituals. Create a 100-day manifestation plan for a 22-year-old engineering student in Singapore to achieve top exam results. Include Saraswati Vandana chanting schedules, morning focus...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Academic Success through Saraswati Vandana Study Flow Rituals\"\n\nStarting brief:\nYou are an Academic Success Coach integrating Indian spiritual rituals. Create a 100-day manifestation plan for a 22-year-old engineering student in Singapore to achieve top exam results. Include Saraswati Vandana chanting schedules, morning focus meditations, and smart study planning.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Academic Success through Saraswati Vandana Study Flow Rituals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Exam dates\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":822,"title":"Manifesting Public Speaking Confidence through Hanuman Chalisa Energy Activation","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Intermediate","explanation":"You are a Confidence Coach specializing in Indian spiritual practices. Create a 30-day manifestation plan for a 27-year-old marketing professional to deliver a confident stage speech, using Hanuman Chalisa chanting, power-posture training, and speech...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Public Speaking Confidence through Hanuman Chalisa Energy Activation\"\n\nStarting brief:\nYou are a Confidence Coach specializing in Indian spiritual practices. Create a 30-day manifestation plan for a 27-year-old marketing professional to deliver a confident stage speech, using Hanuman Chalisa chanting, power-posture training, and speech visualization.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Public Speaking Confidence through Hanuman Chalisa Energy Activation details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Date of event\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":823,"title":"Manifesting a Fitness Transformation through Surya Namaskar Affirmations","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Holistic Health Coach integrating yoga and manifestation. Create a 90-day plan for a 31-year-old IT consultant to lose weight and boost energy through Surya Namaskar, affirmations, and mindful eating practices. Copy-ready prompt with...","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting a Fitness Transformation through Surya Namaskar Affirmations\"\n\nStarting brief:\nYou are a Holistic Health Coach integrating yoga and manifestation. Create a 90-day plan for a 31-year-old IT consultant to lose weight and boost energy through Surya Namaskar, affirmations, and mindful eating practices.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting a Fitness Transformation through Surya Namaskar Affirmations details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Current fitness level\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":824,"title":"Manifesting Startup Funding through Lakshmi Energy Activation Networking Rituals","category":"Meetings","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Intermediate","explanation":"You are a Business Abundance Coach blending finance strategy with Lakshmi energy practices. Create a 60-day plan for a 29-year-old founder to attract startup funding, including wealth rituals, pitch preparation, and intentional investor networking....","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Startup Funding through Lakshmi Energy Activation Networking Rituals\"\n\nStarting brief:\nYou are a Business Abundance Coach blending finance strategy with Lakshmi energy practices. Create a 60-day plan for a 29-year-old founder to attract startup funding, including wealth rituals, pitch preparation, and intentional investor networking.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Manifesting Startup Funding through Lakshmi Energy Activation Networking Rituals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Funding target\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":825,"title":"Manifesting Artistic Recognition through Raga Meditation Creative Flow States","category":"Productivity","source":"Personal Growth","module":"Manifestation Goal Setting Using Indian Spiritual Principles","difficulty":"Beginner","explanation":"You are a Creative Arts Manifestation Mentor integrating Indian classical music traditions. Create a 6-month plan for a 26-year-old singer to manifest regional recognition, using Raga meditation, performance visualization, and gratitude-based networking....","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Manifesting Artistic Recognition through Raga Meditation Creative Flow States\"\n\nStarting brief:\nYou are a Creative Arts Manifestation Mentor integrating Indian classical music traditions. Create a 6-month plan for a 26-year-old singer to manifest regional recognition, using Raga meditation, performance visualization, and gratitude-based networking.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Manifesting Artistic Recognition through Raga Meditation Creative Flow States details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Genre focus\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":826,"title":"Prompt 1 – Instagram Carousel on “Daily Mindfulness Habits”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a content strategist for a spiritual coach. Write a 7-slide Instagram carousel post titled 'Daily Mindfulness Habits for a Calmer Life'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 1 – Instagram Carousel on “Daily Mindfulness Habits”\"\n\nStarting brief:\nYou are a content strategist for a spiritual coach. Write a 7-slide Instagram carousel post titled 'Daily Mindfulness Habits for a Calmer Life'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 1 – Instagram Carousel on “Daily Mindfulness Habits” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Audience type\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":827,"title":"Prompt 2 – Reel Script on “How to Start Meditation When You’re Restless”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a social media manager for a spiritual coach. Write a 30-second reel script titled 'How to Start Meditation When You're Restless'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 2 – Reel Script on “How to Start Meditation When You’re Restless”\"\n\nStarting brief:\nYou are a social media manager for a spiritual coach. Write a 30-second reel script titled 'How to Start Meditation When You're Restless'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 2 – Reel Script on “How to Start Meditation When You’re Restless” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Platform (Instagram/YouTube Shorts)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":828,"title":"Prompt 3 – Facebook Live Outline on “Healing Through Forgiveness”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Intermediate","explanation":"You are a content writer for a spiritual coach. Create a 20-minute Facebook Live outline titled 'Healing Through Forgiveness'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 3 – Facebook Live Outline on “Healing Through Forgiveness”\"\n\nStarting brief:\nYou are a content writer for a spiritual coach. Create a 20-minute Facebook Live outline titled 'Healing Through Forgiveness'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 3 – Facebook Live Outline on “Healing Through Forgiveness” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":829,"title":"Prompt 4 – YouTube Video Script on “Law of Attraction for Beginners”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a video content writer for a spiritual coach. Write a 7-minute script titled 'Law of Attraction for Beginners'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 4 – YouTube Video Script on “Law of Attraction for Beginners”\"\n\nStarting brief:\nYou are a video content writer for a spiritual coach. Write a 7-minute script titled 'Law of Attraction for Beginners'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 4 – YouTube Video Script on “Law of Attraction for Beginners” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Level of detail\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":830,"title":"Prompt 5 – LinkedIn Article on “Mindfulness for Leadership”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a content strategist for a spiritual coach. Write a 1,000-word LinkedIn article titled 'Mindfulness for Leadership: The Secret to Calm, Effective Decisions'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 5 – LinkedIn Article on “Mindfulness for Leadership”\"\n\nStarting brief:\nYou are a content strategist for a spiritual coach. Write a 1,000-word LinkedIn article titled 'Mindfulness for Leadership: The Secret to Calm, Effective Decisions'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 5 – LinkedIn Article on “Mindfulness for Leadership” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Target leadership level\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":831,"title":"Prompt 6 – Instagram Story Series: “7 Days to Self Love”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a content creator for a spiritual coach. Design a 7-day Instagram Story challenge called '7 Days to Self-Love'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 6 – Instagram Story Series: “7 Days to Self Love”\"\n\nStarting brief:\nYou are a content creator for a spiritual coach. Design a 7-day Instagram Story challenge called '7 Days to Self-Love'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 6 – Instagram Story Series: “7 Days to Self Love” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Audience demographics\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":832,"title":"Prompt 7 – Twitter/X Thread on “5 Myths About Meditation”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a content strategist for a spiritual coach. Write a 7-tweet thread titled '5 Myths About Meditation — Busted'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 7 – Twitter/X Thread on “5 Myths About Meditation”\"\n\nStarting brief:\nYou are a content strategist for a spiritual coach. Write a 7-tweet thread titled '5 Myths About Meditation — Busted'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 7 – Twitter/X Thread on “5 Myths About Meditation” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of myths\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":833,"title":"Prompt 8 – Podcast Episode Plan: “Manifestation for Students”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a podcast scriptwriter for a spiritual coach. Create a 20-minute episode plan titled 'Manifestation for Students'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 8 – Podcast Episode Plan: “Manifestation for Students”\"\n\nStarting brief:\nYou are a podcast scriptwriter for a spiritual coach. Create a 20-minute episode plan titled 'Manifestation for Students'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 8 – Podcast Episode Plan: “Manifestation for Students” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Student age range\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":834,"title":"Prompt 9 – Instagram Reel: “Morning Ritual for a Positive Day”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a social media strategist for a spiritual coach. Create a 45-second reel titled 'Morning Ritual for a Positive Day'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 9 – Instagram Reel: “Morning Ritual for a Positive Day”\"\n\nStarting brief:\nYou are a social media strategist for a spiritual coach. Create a 45-second reel titled 'Morning Ritual for a Positive Day'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 9 – Instagram Reel: “Morning Ritual for a Positive Day” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Ritual type (yoga\n- meditation\n- journaling)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":835,"title":"Prompt 10 – WhatsApp Broadcast Script: “Daily Gratitude Practice”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a community manager for a spiritual coach. Create a 30-day WhatsApp gratitude series. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 10 – WhatsApp Broadcast Script: “Daily Gratitude Practice”\"\n\nStarting brief:\nYou are a community manager for a spiritual coach. Create a 30-day WhatsApp gratitude series.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 10 – WhatsApp Broadcast Script: “Daily Gratitude Practice” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Duration of series\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":836,"title":"Prompt 11 – Facebook Group Live Q&A: “Healing Through Forgiveness”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are an event planner for a spiritual coach. Create a 45-minute Facebook Live Q&A plan on the theme 'Healing Through Forgiveness'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 11 – Facebook Group Live Q&A: “Healing Through Forgiveness”\"\n\nStarting brief:\nYou are an event planner for a spiritual coach. Create a 45-minute Facebook Live Q&A plan on the theme 'Healing Through Forgiveness'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 11 – Facebook Group Live Q&A: “Healing Through Forgiveness” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Audience demographics\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":837,"title":"Prompt 12 – YouTube Shorts: “One Minute Mindfulness”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a video scriptwriter for a spiritual coach. Create a 1-minute YouTube Short titled 'One-Minute Mindfulness'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 12 – YouTube Shorts: “One Minute Mindfulness”\"\n\nStarting brief:\nYou are a video scriptwriter for a spiritual coach. Create a 1-minute YouTube Short titled 'One-Minute Mindfulness'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 12 – YouTube Shorts: “One Minute Mindfulness” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Scenario type (office, MRT commute\n- home)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":838,"title":"Prompt 13 – Instagram Carousel Post: “Chakra Healing Basics”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a content designer for a spiritual coach. Create a 7-slide Instagram carousel on 'Chakra Healing Basics'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 13 – Instagram Carousel Post: “Chakra Healing Basics”\"\n\nStarting brief:\nYou are a content designer for a spiritual coach. Create a 7-slide Instagram carousel on 'Chakra Healing Basics'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 13 – Instagram Carousel Post: “Chakra Healing Basics” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Preferred color palette\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":839,"title":"Prompt 14 – LinkedIn Article: “Mindfulness in Corporate Life”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a corporate wellness content writer. Draft a 1,000-word LinkedIn article titled 'Mindfulness in Corporate Life'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 14 – LinkedIn Article: “Mindfulness in Corporate Life”\"\n\nStarting brief:\nYou are a corporate wellness content writer. Draft a 1,000-word LinkedIn article titled 'Mindfulness in Corporate Life'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 14 – LinkedIn Article: “Mindfulness in Corporate Life” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry type\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":840,"title":"Prompt 15 – Instagram Live Collaboration: “Yoga & Affirmations”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a live content planner. Create a 30-minute IG Live outline for a spiritual coach and a yoga instructor on 'Yoga & Affirmations'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 15 – Instagram Live Collaboration: “Yoga & Affirmations”\"\n\nStarting brief:\nYou are a live content planner. Create a 30-minute IG Live outline for a spiritual coach and a yoga instructor on 'Yoga & Affirmations'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 15 – Instagram Live Collaboration: “Yoga & Affirmations” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Yoga style\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":841,"title":"Prompt 16 – Twitter Thread: “Daily Gratitude Practice”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a social media strategist. Draft a 10-tweet thread on the theme 'Daily Gratitude Practice'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 16 – Twitter Thread: “Daily Gratitude Practice”\"\n\nStarting brief:\nYou are a social media strategist. Draft a 10-tweet thread on the theme 'Daily Gratitude Practice'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 16 – Twitter Thread: “Daily Gratitude Practice” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Target audience profile\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":842,"title":"Prompt 17 – Pinterest Infographic: “Morning Rituals for Peace”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a visual content creator. Create a Pinterest infographic titled '5 Morning Rituals for Peace'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 17 – Pinterest Infographic: “Morning Rituals for Peace”\"\n\nStarting brief:\nYou are a visual content creator. Create a Pinterest infographic titled '5 Morning Rituals for Peace'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 17 – Pinterest Infographic: “Morning Rituals for Peace” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Rituals to feature\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":843,"title":"Prompt 18 – Instagram Story Series: “7 Days of Self Love”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Intermediate","explanation":"You are a challenge campaign designer. Develop a 7-day Instagram Story challenge titled '7 Days of Self-Love'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 18 – Instagram Story Series: “7 Days of Self Love”\"\n\nStarting brief:\nYou are a challenge campaign designer. Develop a 7-day Instagram Story challenge titled '7 Days of Self-Love'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 18 – Instagram Story Series: “7 Days of Self Love” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Activities per day\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":844,"title":"Prompt 19 – Facebook Ad Copy: “Free 5 Minute Meditation”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are an ad copywriter. Create a Facebook ad for a free 5-minute meditation. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 19 – Facebook Ad Copy: “Free 5 Minute Meditation”\"\n\nStarting brief:\nYou are an ad copywriter. Create a Facebook ad for a free 5-minute meditation.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 19 – Facebook Ad Copy: “Free 5 Minute Meditation” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Meditation focus\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":845,"title":"Prompt 20 – Instagram Reel: “Before and After Mindfulness”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a video scriptwriter. Create a 30-second Reel script showing a day before mindfulness and after mindfulness. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 20 – Instagram Reel: “Before and After Mindfulness”\"\n\nStarting brief:\nYou are a video scriptwriter. Create a 30-second Reel script showing a day before mindfulness and after mindfulness.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 20 – Instagram Reel: “Before and After Mindfulness” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Scenarios (workplace\n- home)\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":846,"title":"Prompt 21 – LinkedIn Carousel: “Spiritual Leadership in Business”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a B2B content creator. Create an 8-slide carousel on 'Spiritual Leadership in Business'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 21 – LinkedIn Carousel: “Spiritual Leadership in Business”\"\n\nStarting brief:\nYou are a B2B content creator. Create an 8-slide carousel on 'Spiritual Leadership in Business'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 21 – LinkedIn Carousel: “Spiritual Leadership in Business” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry focus\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":847,"title":"Prompt 22 – WhatsApp Broadcast: “Daily Mindfulness Tip”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a community engagement manager. Write 7 daily WhatsApp messages with short mindfulness tips. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 22 – WhatsApp Broadcast: “Daily Mindfulness Tip”\"\n\nStarting brief:\nYou are a community engagement manager. Write 7 daily WhatsApp messages with short mindfulness tips.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 22 – WhatsApp Broadcast: “Daily Mindfulness Tip” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Tip themes\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":848,"title":"Prompt 23 – Blog Post: “How Meditation Changed My Life”","category":"Meetings","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a ghostwriter for a spiritual coach. Write a blog post titled 'How Meditation Changed My Life'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Prompt 23 – Blog Post: “How Meditation Changed My Life”\"\n\nStarting brief:\nYou are a ghostwriter for a spiritual coach. Write a blog post titled 'How Meditation Changed My Life'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Prompt 23 – Blog Post: “How Meditation Changed My Life” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Personal anecdotes\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":849,"title":"Prompt 24 – Instagram Quote Post: “Inner Peace is Power”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a graphic content planner. Design an Instagram quote post with the text 'Inner Peace is Power'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 24 – Instagram Quote Post: “Inner Peace is Power”\"\n\nStarting brief:\nYou are a graphic content planner. Design an Instagram quote post with the text 'Inner Peace is Power'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 24 – Instagram Quote Post: “Inner Peace is Power” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Font style\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":850,"title":"Prompt 25 – Podcast Episode Outline: “Mindfulness for Parents”","category":"Productivity","source":"Personal Growth","module":"Social media content for spiritual coaches","difficulty":"Beginner","explanation":"You are a podcast content producer. Outline a 20-minute episode on 'Mindfulness for Parents'. Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as a practical productivity coach who turns goals into small repeatable actions. Help me create a polished, workplace-ready output for this task:\n\"Prompt 25 – Podcast Episode Outline: “Mindfulness for Parents”\"\n\nStarting brief:\nYou are a podcast content producer. Outline a 20-minute episode on 'Mindfulness for Parents'.\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\ncreate a simple plan, checklist, habit, or reflection tool that can be used immediately\n\nMy details:\n- Prompt 25 – Podcast Episode Outline: “Mindfulness for Parents” details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Parenting challenges to focus on\n- goal\n- available time\n- constraints\n- current blockers\n- preferred routine\n- current situation\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Start with the desired outcome and the smallest useful next action.\n2. Prioritize tasks by impact, effort, urgency, and dependency.\n3. Make the plan realistic for a busy employee.\n4. Include a review loop so the employee can adjust after trying it.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Quick-start plan\n- Prioritized checklist\n- Daily or weekly routine\n- Common blockers and fixes\n- Reflection or review prompt\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Avoid vague advice. Keep actions specific, time-bounded, and easy to try.\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"⚡","color":"cat-yellow"},{"id":851,"title":"Weekend Mindfulness Retreat for Corporate Professionals","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are an experienced retreat planner specializing in corporate wellness programs. Design a detailed weekend retreat agenda for Singapore corporate professionals focused on mindfulness and stress relief. Include: Copy-ready prompt with placeholders, task...","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Weekend Mindfulness Retreat for Corporate Professionals\"\n\nStarting brief:\nYou are an experienced retreat planner specializing in corporate wellness programs. Design a detailed weekend retreat agenda for Singapore corporate professionals focused on mindfulness and stress relief. Include:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Weekend Mindfulness Retreat for Corporate Professionals details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":852,"title":"Women s Self Love Empowerment Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a women's empowerment retreat facilitator. Create a 3-day agenda for a Singapore audience that includes: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Women s Self Love Empowerment Retreat\"\n\nStarting brief:\nYou are a women's empowerment retreat facilitator. Create a 3-day agenda for a Singapore audience that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Women s Self Love Empowerment Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age range of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":853,"title":"Spiritual Awakening Inner Peace Workshop","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a spiritual workshop designer. Create a 1-day agenda that includes: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Spiritual Awakening Inner Peace Workshop\"\n\nStarting brief:\nYou are a spiritual workshop designer. Create a 1-day agenda that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Spiritual Awakening Inner Peace Workshop details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Group size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":854,"title":"Mindful Parenting Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a parenting and mindfulness expert. Design a 2-day retreat plan including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Mindful Parenting Retreat\"\n\nStarting brief:\nYou are a parenting and mindfulness expert. Design a 2-day retreat plan including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Mindful Parenting Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age range of children attending\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":855,"title":"Stress Management Retreat for Students Preparing for Exams","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a youth wellness retreat planner. Create a 2-day agenda for exam aspirants that includes: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Stress Management Retreat for Students Preparing for Exams\"\n\nStarting brief:\nYou are a youth wellness retreat planner. Create a 2-day agenda for exam aspirants that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Stress Management Retreat for Students Preparing for Exams details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age group of students\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":856,"title":"Healing Through Nature Forest Therapy Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Advanced","explanation":"You are an eco-spiritual retreat designer. Plan a 3-day forest therapy retreat in or near Singapore, including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Healing Through Nature Forest Therapy Retreat\"\n\nStarting brief:\nYou are an eco-spiritual retreat designer. Plan a 3-day forest therapy retreat in or near Singapore, including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Healing Through Nature Forest Therapy Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Participant fitness levels\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":857,"title":"Yoga Ayurveda Wellness Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Advanced","explanation":"You are a wellness retreat planner. Design a 5-day agenda for a Singapore-region Yoga & Ayurveda retreat (Sentosa, Bintan, or similar venue), including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Yoga Ayurveda Wellness Retreat\"\n\nStarting brief:\nYou are a wellness retreat planner. Design a 5-day agenda for a Singapore-region Yoga & Ayurveda retreat (Sentosa, Bintan, or similar venue), including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Yoga Ayurveda Wellness Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":858,"title":"Men s Emotional Healing Brotherhood Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a facilitator of men's emotional wellness programs. Create a 2-day agenda for a Singapore audience that includes: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Men s Emotional Healing Brotherhood Retreat\"\n\nStarting brief:\nYou are a facilitator of men's emotional wellness programs. Create a 2-day agenda for a Singapore audience that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Men s Emotional Healing Brotherhood Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age range of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":859,"title":"Silent Meditation Retreat Vipassana inspired","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a meditation retreat planner. Create a detailed 4-day silent retreat agenda for beginners, including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Silent Meditation Retreat Vipassana inspired\"\n\nStarting brief:\nYou are a meditation retreat planner. Create a detailed 4-day silent retreat agenda for beginners, including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Silent Meditation Retreat Vipassana inspired details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":860,"title":"Creative Manifestation Vision Board Workshop","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a manifestation and creativity coach. Create a 1-day workshop plan that includes: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Creative Manifestation Vision Board Workshop\"\n\nStarting brief:\nYou are a manifestation and creativity coach. Create a 1-day workshop plan that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Creative Manifestation Vision Board Workshop details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Group size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":861,"title":"Women s Sacred Circle Inner Healing Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a women's wellness retreat planner. Create a 3-day agenda including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Women s Sacred Circle Inner Healing Retreat\"\n\nStarting brief:\nYou are a women's wellness retreat planner. Create a 3-day agenda including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Women s Sacred Circle Inner Healing Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Group size and age range\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":862,"title":"Corporate Mindfulness Stress Release Workshop","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a corporate wellness trainer. Create a 1-day workshop agenda including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Corporate Mindfulness Stress Release Workshop\"\n\nStarting brief:\nYou are a corporate wellness trainer. Create a 1-day workshop agenda including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Corporate Mindfulness Stress Release Workshop details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Employee demographics\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":863,"title":"Bhakti Yoga Kirtan Immersion","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a Bhakti yoga facilitator. Create a 2-day retreat plan that includes: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Bhakti Yoga Kirtan Immersion\"\n\nStarting brief:\nYou are a Bhakti yoga facilitator. Create a 2-day retreat plan that includes:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Bhakti Yoga Kirtan Immersion details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Music and instrument availability\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":864,"title":"Mindful Parenting Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a conscious parenting coach. Design a 2-day retreat including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Mindful Parenting Retreat\"\n\nStarting brief:\nYou are a conscious parenting coach. Design a 2-day retreat including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Mindful Parenting Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of families attending\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":865,"title":"Sound Healing Chakra Balancing Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Advanced","explanation":"You are a sound healer designing a retreat. Create a 3-day schedule including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Sound Healing Chakra Balancing Retreat\"\n\nStarting brief:\nYou are a sound healer designing a retreat. Create a 3-day schedule including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Sound Healing Chakra Balancing Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":866,"title":"Ayurveda Seasonal Wellness Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are an Ayurvedic wellness retreat planner. Create a 4-day schedule including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Ayurveda Seasonal Wellness Retreat\"\n\nStarting brief:\nYou are an Ayurvedic wellness retreat planner. Create a 4-day schedule including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Ayurveda Seasonal Wellness Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Participant dosha assessment results\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":867,"title":"Mindfulness for Educators Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a mindfulness coach for educators. Design a 2-day retreat including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Mindfulness for Educators Retreat\"\n\nStarting brief:\nYou are a mindfulness coach for educators. Design a 2-day retreat including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Mindfulness for Educators Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Teaching experience levels\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":868,"title":"Digital Detox Nature Immersion","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a digital detox retreat planner. Create a 3-day program including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Digital Detox Nature Immersion\"\n\nStarting brief:\nYou are a digital detox retreat planner. Create a 3-day program including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Digital Detox Nature Immersion details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Number of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":869,"title":"Grief Healing Emotional Resilience Workshop","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Intermediate","explanation":"You are a grief healing facilitator. Create a 1-day workshop plan including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Grief Healing Emotional Resilience Workshop\"\n\nStarting brief:\nYou are a grief healing facilitator. Create a 1-day workshop plan including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Grief Healing Emotional Resilience Workshop details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age group of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":870,"title":"Sacred Masculinity Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a men's personal growth coach. Create a 2-day retreat schedule including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Sacred Masculinity Retreat\"\n\nStarting brief:\nYou are a men's personal growth coach. Create a 2-day retreat schedule including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Sacred Masculinity Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Participant age range\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":871,"title":"Women s Empowerment Self Love Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a women's wellness coach. Create a 3-day empowerment retreat plan including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Women s Empowerment Self Love Retreat\"\n\nStarting brief:\nYou are a women's wellness coach. Create a 3-day empowerment retreat plan including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Women s Empowerment Self Love Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age range of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":872,"title":"Stress Relief Through Sound Healing","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Advanced","explanation":"You are a sound healing facilitator. Create a 1-day workshop including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Stress Relief Through Sound Healing\"\n\nStarting brief:\nYou are a sound healing facilitator. Create a 1-day workshop including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Stress Relief Through Sound Healing details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Group size\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":873,"title":"Yoga Mindful Leadership Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a corporate mindfulness coach. Create a 2-day retreat plan including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Yoga Mindful Leadership Retreat\"\n\nStarting brief:\nYou are a corporate mindfulness coach. Create a 2-day retreat plan including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Yoga Mindful Leadership Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Industry background of leaders\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":874,"title":"Couples Connection Communication Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Beginner","explanation":"You are a relationship coach. Create a 2-day couples' retreat including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Couples Connection Communication Retreat\"\n\nStarting brief:\nYou are a relationship coach. Create a 2-day couples' retreat including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Couples Connection Communication Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Relationship stage of couples\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"},{"id":875,"title":"Inner Child Healing Retreat","category":"Meetings","source":"Personal Growth","module":"Workshop retreat agendas","difficulty":"Intermediate","explanation":"You are a trauma-informed mindfulness coach. Create a 2-day inner child healing retreat including: Copy-ready prompt with placeholders, task steps, output format, and review rules.","prompt":"Act as an expert meeting facilitator and follow-up owner. Help me create a polished, workplace-ready output for this task:\n\"Inner Child Healing Retreat\"\n\nStarting brief:\nYou are a trauma-informed mindfulness coach. Create a 2-day inner child healing retreat including:\n\nBusiness context:\nUse the context I provide below. Do not guess missing facts.\n\nDesired outcome:\nturn scattered discussion or planning needs into a clear meeting asset\n\nMy details:\n- Inner Child Healing Retreat details: [paste the real situation, notes, data, or draft here]\n- Audience: [who will read or use the output]\n- Goal: [what should happen after this output is used]\n- Constraints: [deadline, policy, tone, format, system, budget, or approval rules]\n- Source material: [file notes, meeting notes, spreadsheet summary, CRM notes, or links if available]\n\nUse or ask me to confirm these inputs if needed:\n- Age range of participants\n- meeting purpose\n- attendees or roles\n- time limit\n- decisions needed\n- follow-up format\n- goal\n- current situation\n- constraints\n- preferred style\n- time available\n- company policy or approved wording if relevant\n- examples of preferred style or past output if available\n\nInstructions:\n1. Clarify the meeting objective, audience, timing, and decision points.\n2. Separate agenda items, discussion prompts, decisions, risks, and follow-up actions.\n3. Assign suggested owners and due dates where the employee has provided enough context.\n4. Include a concise version for busy readers and a detailed version for the organizer.\n5. Use the starting brief as the intent, but improve it with clearer structure, stronger reasoning, and practical business detail.\n6. Write for a non-technical employee unless the user asks for an expert-level version.\n7. Use concrete examples, tables, checklists, or templates where they make the output easier to use.\n8. Keep sensitive details anonymized. Replace private names, client data, account numbers, credentials, and confidential figures with placeholders.\n\nIf important information is missing, ask up to 5 focused clarification questions first. If there is enough information to proceed, continue and mark any assumptions as [Assumption].\n\nReturn the output in this format:\n- Meeting objective\n- Agenda or recap table with time, topic, owner, and expected outcome\n- Decision log\n- Action items with owner, due date, and dependency\n- Follow-up message ready to send\n\nQuality rules:\n- Be specific enough that the employee can use the result immediately after review.\n- Use simple language, short headings, and clear bullets or tables.\n- Separate confirmed facts from assumptions and recommendations.\n- Include practical next steps, owners, timing, or review gates when relevant.\n- Offer a shorter version when the output is likely to be pasted into email, chat, CRM, Teams, or a document.\n\nSafety and accuracy rules:\n- Do not invent attendance, decisions, or commitments. Mark unknown owners or dates as [confirm].\n- Keep advice grounded, realistic, non-clinical, and easy to try today.\n- Check facts, numbers, dates, names, and policy-sensitive claims before sharing.\n- Do not include confidential, personal, client, financial, or system-access data unless the approved internal AI tool allows it.\n\nBefore you answer, check:\n- Did you answer the exact task?\n- Did you use the provided context instead of inventing details?\n- Is the output easy for a beginner to copy, edit, and use?\n- Are risks, missing information, and review needs clearly marked?","icon":"🗓️","color":"cat-blue"}]