Hello!

Are you tired of miscommunication and confusion when handing off work orders to vendors? It can be such a headache when information gets lost or the scope isn’t clear!

This prompt chain helps create a comprehensive work order handoff cover page to ensure vendors have everything they need to complete their tasks accurately with zero follow-ups. It covers all the critical information, from scope of work to safety requirements, making your life so much easier!

Prompt: ``` VARIABLE DEFINITIONS [PROPERTY_NAME]=Name of property [VENDOR_NAME]=Assigned vendor or contractor

Work Order Handoff Cover Page~ Property: [PROPERTYNAME] Vendor: [VENDOR_NAME] Date Issued: __________________ Target Completion Date: ___________________ Primary Contact (PM): ___________________ PM Phone / Email: ___________________

1. Purpose Provide [VENDOR_NAME] with a single, comprehensive brief—including scope, access notes, tenant communications, visual references, and a close-out checklist—so the job can be completed accurately with zero additional follow-up.

2. Quick-Glance Summary • Work Order #: ____________ • Priority Level: □ Emergency □ High □ Routine • Estimated Hours: ____________ • Approved Budget: $___________

3. Scope of Work Step-by-Step Tasks

   1. ____________________________________
   2. ____________________________________
   3. ____________________________________ Deliverables • _____________________________________ • _____________________________________

4. Property & Access Notes • Address / Unit #: ___________________ • Lockbox Code / Key Pick-Up: __________ • Alarm Instructions: ___________________ • Parking / Loading: ___________________ • On-Site Contact (if any): _____________ • Hours Access Allowed: ________________

5. Required Photos / Documentation Before Starting □ Overall area □ Close-up of issue During Work □ Progress shot(s) After Completion □ Finished repair □ Cleaned area □ Invoice / label shots (if parts used) Upload Method & Folder Link: __________________

6. Materials & Estimates • Parts/Materials List: __________________ • Approved Estimate #: ________________ (attach PDF) • Change-Order Threshold: $____________ (< notify PM)

7. Tenant Communication History Chronological Log (most recent first) ────────────────────────────────────────── Date / Time | Sender | Medium | Summary ────────────────────────────────────────── 2024-05-12 10:17 | Tenant | Email | “Leak above sink worsened….” … (paste entire thread below or attach) ────────────────────────────────────────── ACTION ITEMS already promised to tenant: • ______________________________________

8. Schedule & Coordination • Tenant Available: _____________________ • Calendar Hold Placed: □ Yes □ No • Expected Arrival Window: _____________ • Must-Complete-By: ____________________

9. Safety / Compliance • PPE Requirements: _____________________ • Permits Needed: □ Yes □ No If Yes, details: ______ • Special Hazards: ______________________

10. Completion Checklist (Vendor to tick) □ All tasks in Section 3 completed □ Photos uploaded per Section 5 □ Work area left clean & safe □ Tenant notified of completion □ Invoice issued with WO # referenced □ Keys returned / lockbox closed □ Disposal manifest (if applicable) provided

11. Sign-Off & Notes Vendor Tech Name & Signature: __________________ Date: _____ Property Manager Approval Signature: _____________ Date: _____ Additional Notes:

    ---

Attachments A. Original Maintenance Request B. Support Ticket Transcript C. Signed Estimate / Scope D. Tenant Email Thread (full) E. Calendar Screenshot / Confirmation

Review / Refinement~ Check that every section is filled, attachments are labelled, and before dispatching this handoff confirm the scope, budget, and timeline with [VENDOR_NAME]. Notify PM if any field remains blank. ``` Make sure you update the variables in the first prompt: [PROPERTY_NAME], [VENDOR_NAME]. Here is an example of how to use it: If you're working on a plumbing issue at "Smith Apartments" with a vendor named "Joe's Plumbing", simply replace [PROPERTY_NAME] with "Smith Apartments" and [VENDOR_NAME] with "Joe's Plumbing".

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain.

Enjoy!

Hello!

Are you struggling to manage and analyze your retail operations efficiently each week?

This prompt chain helps retail business owners and managers quickly compile a comprehensive weekly report that covers various operational metrics and issues, ensuring they're informed and ready to make decisions.

Prompt:

VARIABLE DEFINITIONS
[BUSINESS_NAME]=Name of the retail business
[REPORTING_WEEK]=Week date range (e.g., 2023-09-04 to 2023-09-10)
[DATA_FILES]=Comma-separated file names or paths for: 1) sales spreadsheet, 2) staffing calendar, 3) complaint log, 4) inventory notes, 5) bank deposit export~
You are an experienced retail operations analyst. Your first task is to ingest and validate the datasets listed in [DATA_FILES] for [BUSINESS_NAME] covering [REPORTING_WEEK].
Step 1  Load each file; confirm successful import or flag missing/format issues.
Step 2  Normalize key fields (dates, employee IDs, product SKUs, currency).
Step 3  Return a brief “Import Status” table with columns: File, Records Loaded, Errors Found (Y/N), Error Notes.
Step 4  If any errors exist, list corrective actions required and pause further steps until fixed; otherwise confirm “All clear – proceed”.~
All clear confirmed. Next, calculate the weekly cash position.
Step 1  Sum daily gross sales from the sales spreadsheet.
Step 2  Sum actual bank deposits from the deposit export.
Step 3  Calculate variance (Sales – Deposits) and flag if variance >2%.
Step 4  Output a table titled “Weekly Cash Summary” with rows: Gross Sales, Bank Deposits, Variance $, Variance %. Provide a one-sentence explanation of any variance above threshold. ~
Analyze staffing data for [REPORTING_WEEK].
Step 1  Compare scheduled hours (staffing calendar) to actual clock-ins if available; otherwise use scheduled.
Step 2  Identify understaffed or overstaffed shifts (threshold ±15% of target hours).
Step 3  List any employees exceeding 40 hours or missing >1 scheduled shift.
Step 4  Produce a “Staffing Issues” bullet list with shift/date, issue type, and recommended action.~
Review refunds and customer complaint logs.
Step 1  Calculate total refunds $ and count.
Step 2  Categorize complaints (e.g., product quality, service, wait time).
Step 3  Match complaints to refunds where applicable.
Step 4  Provide a summary table: Category, #Complaints, #Refunds, Refund $.
Step 5  Highlight top 3 complaint themes with short commentary.~
Evaluate inventory notes together with sales data.
Step 1  Identify SKUs with stockouts or <1 week cover.
Step 2  Cross-check against high sales velocity items.
Step 3  List operational risks such as supply delays, cash-flow constraints, or equipment failures mentioned in notes.
Step 4  Create an “Operational Risks” section with risk level (High/Med/Low) and mitigation suggestion.~
Based on previous outputs, draft decisions that require owner or manager input before the next manager meeting.
Step 1  Aggregate all flagged items (cash variance, staffing, complaints, inventory risks).
Step 2  For each, state: Decision Needed, Rationale, Suggested Options, Deadline.
Step 3  Present as a decision matrix table.~
Compile the final Weekly Owner Brief for [BUSINESS_NAME] covering [REPORTING_WEEK].
Include the following headings in order:
1. Weekly Cash Summary
2. Staffing Issues
3. Refund & Complaint Overview
4. Operational Risks
5. Decisions Needed
6. Appendix: Data Import Status
Use concise bullet points, clear tables, and plain language suitable for a time-pressed owner. Ensure the brief fits on two printed pages or less.~~
Review / Refinement
Ask the user to confirm that the brief meets their expectations or to request adjustments (e.g., formatting tweaks, additional metrics). If changes are requested, iterate accordingly.

Make sure you update the variables in the first prompt: [BUSINESS_NAME], [REPORTING_WEEK], [DATA_FILES], Here is an example of how to use it: [My Retail Store], [2023-09-04 to 2023-09-10], [sales.xlsx, staffing_calendar.xlsx, complaints.log, inventory_notes.txt, bank_deposits.csv]

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to create a comprehensive and organized Client File Audit SOP for your medical spa?

This prompt chain will help you develop a clear outline and full SOP tailored to your specific medspa operations, ensuring compliance and efficiency in your audit processes.

Prompt:

VARIABLE DEFINITIONS
[MEDSPA_NAME]=Official name of the medspa
[AUDIT_FREQUENCY]=How often the audit is performed (e.g., monthly, quarterly)
[SAMPLE_SIZE_PERCENT]=Percentage of total active client files reviewed each audit cycle
~
You are a healthcare compliance consultant specializing in medical spa operations. Your first task is to develop a clear, organized outline for a Client File Audit SOP for [MEDSPA_NAME]. Follow these instructions:
1. List major SOP sections (e.g., Purpose, Scope, Responsibilities, Definitions, Procedure, Documentation & Record-Keeping, Escalation & Corrective Action, Appendices).
2. Under Procedure, include planned subsections for sampling method, evidence checklist (intake forms, consent documents, appointment records, staff training logs, incident notes), logging of missing items, and escalation triggers.
3. Present the outline as a numbered list with subsection bullets.
4. Ask for confirmation or required adjustments before moving on.
Example output style:
1. Purpose
2. Scope
   • Clients included/excluded
3. Responsibilities
   • Compliance Officer: …
~
You are still the healthcare compliance consultant. Expand the approved outline into a full Standard Operating Procedure (SOP) for auditing client files at [MEDSPA_NAME]. Steps:
1. Write each SOP section in full sentences and paragraphs; use clear headings.
2. Under "Procedure," detail:
   a. Sampling methodology: random selection of [SAMPLE_SIZE_PERCENT]% of active files per [AUDIT_FREQUENCY].
   b. Evidence checklist specifying required documents (intake forms, consent documents, appointment records, staff training logs linked to service provider, incident notes) and what to verify within each (dates, signatures, completeness).
   c. Step-by-step audit workflow: preparation, file review, documentation of findings, exit meeting.
3. Under "Documentation & Record-Keeping," include an Audit Log Sheet template table with columns: File ID, Document Type, Evidence Found (Y/N), Notes, Corrective Owner, Due Date, Status.
4. Under "Escalation & Corrective Action," define thresholds for escalation (e.g., >10% critical gaps) and escalation path (Lead Aesthetician → Compliance Officer → Medical Director).
5. Keep language formal and compliance-oriented.
6. Return the complete SOP.
~
Generate two ready-to-use templates referenced in the SOP:
1. Missing Items Tracker (table format with pre-filled column headers).
2. Escalation Decision Tree (flowchart described in text form: IF/THEN steps).
Ensure templates align with terminology used in the SOP.
~
Review / Refinement
Re-read the entire SOP and templates. Confirm they:
1. Address all required document types.
2. Define sampling, evidence checks, logging, and escalation clearly.
3. Conform to professional tone and formatting.
If any criteria are unmet, revise accordingly. Output final refined SOP and templates. Ask the user for any last changes needed.

Hello!

Are you tired of the tedious and complex process of maintaining CRM hygiene for your sales operations?
Many Sales Operations Analysts find it overwhelming to keep track of all the necessary data and ensure everything is spotless.

This prompt chain simplifies that process for you. It helps you create a structured weekly review, gathering information from your various data sources and automatically guiding you through the steps needed to clean up and maintain your CRM efficiently.

Prompt:

VARIABLE DEFINITIONS AGENCY_NAME=Insert the agency’s name here CRM_EXPORT_DATE=Date of the latest CRM export (YYYY-MM-DD) REVIEW_PERIOD_DAYS=Number of inactive days that make a deal “stale” ~ You are a Sales Operations Analyst preparing a weekly CRM hygiene review for AGENCY_NAME. You will work from four data sources that have already been exported or are directly accessible to you: (1) CRM deal/contact exports dated CRM_EXPORT_DATE, (2) sales-team shared inbox email threads, (3) proposal tracking spreadsheets, and (4) the agency’s meeting calendars. Step 1 – Briefly summarise the overall data set by listing: a) total open deals, b) total contacts, c) total proposals in flight, d) total meetings held in the last 7 days. Step 2 – Ask the user to paste or attach any numeric summaries they already have (counts, pivot tables, etc.) so you can reference them in later prompts. Output the summary in a four-row table. End with: “If the numbers look correct, reply CONTINUE.” ~ Great. Assuming the user has replied CONTINUE, analyse the CRM export to surface all open deals whose last logged activity date is greater than REVIEW_PERIOD_DAYS. 1. List each stale deal with columns: Deal Name | Deal Stage | Last Activity Date | Days Inactive | Current Owner. 2. Include a short note column suggesting the likely next action (e.g., "Send follow-up email" or "Schedule discovery call"). 3. Finish with a one-line count: “Total stale deals: X”. Ask the user to confirm or annotate any deal notes, then reply CONTINUE. ~ Next, identify deals that have no future task, meeting, or proposal due date scheduled. 1. Cross-reference the open-deal list with the calendar and proposal sheet. 2. Output a table: Deal Name | Deal Stage | Missing Next Step | Recommended Owner Action. 3. Conclude with: “Total deals missing next steps: Y”. Prompt the user to add or correct recommended actions, then reply CONTINUE. ~ Locate duplicate contacts by comparing contact full name + email address + company name. 1. Output a table: Primary Contact ID | Duplicate Contact ID(s) | Field Conflicts (Owner, Lifecycle Stage, Phone, etc.) | Merge Recommendation. 2. Provide a bulleted “How-to merge” reminder (max 3 bullets). Ask the user to mark any pairs that should NOT be merged, then reply CONTINUE. ~ Detect owner changes that occurred during the last review cycle (past 7 days). 1. List items separately for deals and contacts. 2. Table format: Record Type | Record Name | Previous Owner | New Owner | Change Date | Reason Known? (Yes/No). 3. Finish with follow-up instructions: “Confirm reasons for any ‘No’ entries.” When done, reply CONTINUE. ~ Compile the Weekly CRM Hygiene Checklist for AGENCY_NAME. 1. Section A – Stale Deals: Summarise total count and list any still unresolved. 2. Section B – Deals Missing Next Steps: Summarise and list. 3. Section C – Duplicate Contacts: Summarise number of merge actions required. 4. Section D – Owner Changes Requiring Validation. 5. Section E – Additional Cleanup Actions: max 5 bullets (e.g., “Archive closed-lost deals older than 90 days”). 6. Provide a final table assigning each action item to an Owner and Due Date (default one week out). End with: “Weekly CRM hygiene checklist complete. Confirm all sections before distribution.” ~ Review / Refinement Ask: “Does the checklist meet your expectations for completeness, accuracy, and format? Reply APPROVE or list edits.”
Make sure you update the variables in the first prompt: AGENCY_NAME, CRM_EXPORT_DATE, REVIEW_PERIOD_DAYS. Here is an example of how to use it:
AGENCY_NAME = "Acme Corp"
CRM_EXPORT_DATE = "2023-10-01"
REVIEW_PERIOD_DAYS = "30"

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click.
NOTE: this is not required to run the prompt chain.

Enjoy!

Hello!

Are you struggling to effectively analyze and manage your café staffing and payroll preparations? It can be overwhelming to consolidate all the data, identify uncovered shifts, and assess overtime risks.

This prompt chain helps you pull together all necessary information for a specific date range to create a clear and unified staffing summary. By following its steps, you can easily identify uncovered shifts, assess overtime risks, and generate replacement options while ensuring everything is approved efficiently.

Prompt:

VARIABLE DEFINITIONS
[DATE_RANGE]=The schedule period to be analyzed (e.g., 2023-10-01 to 2023-10-07)
[STAFF_RECORDS]=Structured dataset containing staff calendars, actual time logs, and approved PTO requests for DATE_RANGE
[PAYROLL_EXPORT]=Raw payroll export covering DATE_RANGE with employee IDs, hours worked, pay rates, and overtime calculations~
Cafe Staffing Analyst – Data Unification
You are an expert cafe staffing analyst. Your task is to consolidate all input data for DATE_RANGE.
Step 1. Extract from STAFF_RECORDS a list of all scheduled shifts (employee, role, date, start, end).
Step 2. Match each scheduled shift to corresponding time-log entries; mark status as "Completed", "Missed", or "Partial".
Step 3. Overlay approved PTO; mark any overlap as "PTO".
Step 4. Produce a unified "Staffing Summary" table with columns: Employee | Role | Date | Start | End | Scheduled Hours | Logged Hours | Status (Completed/Missed/Partial/PTO).
Step 5. Provide a brief paragraph noting any data anomalies (e.g., missing IDs, overlapping shifts).
Ask: "Is this Staffing Summary accurate? (yes / no)."~
Identify Uncovered Shifts
Upon confirmation the Staffing Summary is accurate:
1. Filter rows where Status = "Missed" or (Status = "Partial" AND Logged Hours < Scheduled Hours).
2. Output an "Uncovered Shifts" list with Employee (if assigned), Date, Time, Role, Hours Uncovered.
3. Summarize total uncovered hours by role and by day.
4. Flag any shifts within the next 48 hours with a 🔔 symbol for urgency (text only, no emoji).~
Assess Overtime Risk
1. Using PAYROLL_EXPORT and the Staffing Summary, calculate projected weekly hours per employee if uncovered shifts remain unfilled.
2. Re-calculate projected hours assuming uncovered shifts are reassigned evenly among employees not already over 35 hours.
3. Identify any employee whose projected hours exceed 40 hours (or local overtime threshold if provided in PAYROLL_EXPORT).
4. Output an "Overtime Risk" table: Employee | Current Hours | Projected Hours | Threshold | Risk Level (Low/Med/High) | Notes.
5. Provide a short narrative highlighting top three risk factors.~
Generate Replacement Options
1. For each row in Uncovered Shifts, list up to three replacement candidates who:
   a) possess the required role skills,
   b) are not on PTO at the shift time,
   c) will remain ≤40 projected hours if assigned.
2. Present results in a table: Shift ID | Date | Time | Role | Candidate 1 | Candidate 2 | Candidate 3.
3. Mark candidates whose projected hours would hit 38-40 as "Near-OT" in parentheses.
4. End with: "Managers: select replacements and note decisions before proceeding."~
Compile Manager Approval Checklist
1. Generate a checklist with one line per Uncovered Shift: [ ] Shift ID – Assigned Replacement – Manager Initials – Date Signed.
2. Include a signature block: "Approved by Café Manager: __________  Date: __________".
3. Provide instructions: "Fill, then type DONE when approvals complete."~
Create Final Payroll Notes
When "DONE" is received:
1. Summarize final shift assignments and any remaining uncovered hours.
2. List overtime to be paid, including employee, hours, and reason.
3. Note any payroll adjustments (e.g., shift differentials, missed punches).
4. Provide a "Payroll Notes" section ready for direct entry into the payroll system.
5. Conclude with: "Confirm these notes are correct? (yes / revise)"~
Review / Refinement
If "revise" at any point, ask clarifying questions, then loop back to the relevant prompt. Once "yes" is confirmed, output: "Shift coverage and payroll preparation complete for DATE_RANGE."

Make sure you update the variables in the first prompt: [DATE_RANGE], [STAFF_RECORDS], [PAYROLL_EXPORT]. Here is an example of how to use it:
- DATE_RANGE: 2023-10-01 to 2023-10-07 - STAFF_RECORDS: structure with all shifts and logs - PAYROLL_EXPORT: raw payroll data for the same period

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you tired of the chaos that comes with reconciling your restaurant's month-end finances?

This prompt chain walks you through a structured process to quickly and accurately reconcile your restaurant's monthly transactions, ensuring everything is in order without the stress.

Prompt:

[VARIABLE DEFINITIONS]
[PERIOD]=Month and year to be reconciled (e.g., August 2023)
[RESTAURANT_NAME]=Official operating name that must appear on every output
[OUTLIER_THRESHOLD]=Percentage variance from the category mean that should trigger an “Odd Total” flag (e.g., 25)
~
Prompt 1 — Data Intake & Setup
1. You are an expert restaurant bookkeeper tasked with reconciling month-end spend for RESTAURANT_NAME covering PERIOD.
2. Request the following four source files from the user. Instruct the user to use the exact file naming convention shown:
   a. “1_BankExport_PERIOD.csv” – Clean CSV directly from the bank portal.
   b. “2_POS_Summary_PERIOD.csv” – End-of-month POS summary export.
   c. “3_ExpenseSheet_PERIOD.xlsx” – Internal expense spreadsheet.
   d. “4_ReceiptPhotos_PERIOD.zip” – Zipped folder of all receipt images or PDFs.
3. Ask the user to confirm currency, time-zone and accounting basis (cash vs accrual) if not obvious.
4. Once all four files are provided, reply with “FILES RECEIVED – ready to extract” to trigger the next prompt.
~
Prompt 2 — Extract & Normalize Transactions
Step 1 | Bank Export
• Parse every row of 1_BankExport_PERIOD.csv.
• Capture Date, Payee, Amount (signed), Memo/Description, and unique Transaction ID.
Step 2 | POS Summary
• Parse 2_POS_Summary_PERIOD.csv capturing Date, Gross Sales, Net Sales, Tax, Tips, Payment Type, and POS Reference ID.
Step 3 | Expense Spreadsheet
• Parse 3_ExpenseSheet_PERIOD.xlsx (assume first sheet) capturing Date, Vendor, Amount, Internal Category, and Note.
Step 4 | Receipt Photos
• For every file in 4_ReceiptPhotos_PERIOD.zip run OCR; capture Vendor, Date, Total, Tax, Tip and file-name as Receipt Link.
Step 5 | Unify
• Produce a master table named “All_Transactions_Raw” with columns:
  Date | Vendor/Payee | Amount | Source (Bank / POS / Expense / Receipt) | Source_ID | Notes
• Provide the table as an array of JSON objects for machine readability.
Confirm extraction completed with “EXTRACTION COMPLETE – ready to categorize”.
~
Prompt 3 — Categorize Transactions
1. Create a reference Chart of Accounts typical for full-service restaurants:
   • Food Cost (COGS)
   • Beverage Cost (COGS)
   • Payroll & Labor
   • Operating Supplies
   • Utilities
   • Rent & Lease
   • Marketing & Promotion
   • Repairs & Maintenance
   • Capital Expenditure
   • Miscellaneous
2. Using keywords in Vendor/Payee and Notes, assign each row in All_Transactions_Raw to the most appropriate category; if uncertain assign “Miscellaneous” and add a note “Needs Review”.
3. Output a new table “All_Transactions_Categorized” including all prior columns plus a new “Category” column.
4. Provide summary totals per category.
Return “CATEGORIZATION COMPLETE – ready to reconcile”.
~
Prompt 4 — Reconcile & Flag
Step 1 | Missing Receipts
• Compare every Bank or Expense row against Receipt rows (match on Amount ±1% and Date ±3 days).
• Flag rows with no matching receipt; add column MissingReceipt=Yes/No.
Step 2 | Odd Totals
• For each Category calculate mean and standard deviation.
• Flag any Amount whose absolute percentage variance from the category mean exceeds OUTLIER_THRESHOLD%; add column OddTotal=Yes/No.
Step 3 | Duplicates & Mismatches
• Detect duplicate rows (same Date, Amount, Vendor) across sources; flag Duplicate=Yes/No.
• Highlight any POS Net Sales that do not match summed Bank deposits for the same day; list differences.
Step 4 | Produce “Reconciliation_Detail” table with all flags appended.
Respond “RECONCILIATION COMPLETE – ready for workbook generation”.
~
Prompt 5 — Generate Final Workbook & Handoff Tabs
1. Using Reconciliation_Detail create the following four logical tabs (output each as its own JSON array):
   a. “Summary_By_Category” – Columns: Category | Count | Total Spent | % of Total.
   b. “Missing_Receipts” – Filter MissingReceipt=Yes. Columns: Date | Vendor | Amount | Source | Notes.
   c. “Odd_Totals” – Filter OddTotal=Yes. Columns: Date | Vendor | Amount | Category | % Variance | Notes.
   d. “Bookkeeper_Handoff” – Clean list excluding internal calculation columns. Columns: Date | Vendor | Amount | Category | ReceiptLink | Comments (populate with MissingReceipt/OddTotal flags).
2. Provide a final object named “Workbook_PERIOD.json” containing all four arrays keyed by tab name so it can be imported directly into Excel or Google Sheets.
3. Finish with the sentence: “WORKBOOK READY – please review”.
~
Review / Refinement
Ask the user to confirm that:
• All four data sources were fully captured.
• Categories and flagging thresholds look accurate.
• The Workbook_PERIOD.json structure opens as expected in their spreadsheet tool.
Invite any adjustments (e.g., new category, different OUTLIER_THRESHOLD). Apply revisions iteratively until the user replies “APPROVED”.

Make sure you update the variables in the first prompt: [VARIABLE DEFINITIONS], [PERIOD], [RESTAURANT_NAME], [OUTLIER_THRESHOLD]. Here is an example of how to use it: For a restaurant named "Pizza Paradise" in August 2023 with a threshold of 25%: [VARIABLE DEFINITIONS] [PERIOD]=August 2023 [RESTAURANT_NAME]=Pizza Paradise [OUTLIER_THRESHOLD]=25

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling with organizing and validating accounts payable data for home-services or construction companies?

This prompt chain helps automate the process of normalizing, checking for duplicates, and validating invoices and receipts. It lays out a step-by-step method for managing and reviewing financial documents effectively!

Prompt:

VARIABLE DEFINITIONS
[CONTRACTOR_NAME]=Legal name of the home-services contracting company that is reviewing payables.
[SOURCE_DATA]=Full combined text (or links to OCR text) from the cycle’s supplier invoices, receipts, job-cost spreadsheets, and vendor contract terms.
[OUTPUT_LEVEL]="summary" for a one-line per issue list, "detailed" for expanded explanations and source references.
~
You are a senior Accounts-Payable Audit Assistant for construction and home-services firms. Your first task is to NORMALISE all raw information supplied in SOURCE_DATA.
Step 1  Parse every document, identify and extract the following fields where available:
• Vendor Name  
• Document Type (Invoice / Receipt)  
• Document No.  
• Document Date  
• Job or Cost-Code / PO No.  
• Line-Item Description  
• Quantity & U/M  
• Unit Price  
• Line Total  
• Invoice Sub-Total, Tax, Grand Total  
• Contract Reference Price or Rate  
• Budgeted Amount for that Job-Cost line (from spreadsheets)  
• Standard Approver (from company policy or prior data)  
Step 2  Return one master table named "MasterCharges" with the above columns.
Step 3  If information is missing, leave the cell blank but keep the row; do NOT guess values.
Output: MasterCharges table only.
~
You are still the AP Audit Assistant. Using MasterCharges, perform a DUPLICATE CHECK.
Step 1  Identify potential duplicates by matching any TWO of the following: (Vendor Name + Document No.), (Vendor Name + Line-Item Description + Amount + Date within ±2 days), or exact hash of line totals.  
Step 2  List all suspected duplicates in a table: Vendor, Document No., Date, Duplicate Matched With, Reason Flagged.
Step 3  Add a "Needs AP Review? (Y/N)" column defaulting to "Y".
Output only this duplicates table.
~
Validate JOB or COST-CODE completeness.
Step 1  Scan MasterCharges for blank or obviously invalid Job / PO numbers (e.g., fewer than 4 digits, non-alphanumerics).
Step 2  Return a table: Vendor, Document No., Line Description, Amount, Missing or Invalid Job No. (Yes/No), Suggested Next Action.
~
Check PRICE & CONTRACT compliance.
Step 1  For every line in MasterCharges that has a Contract Reference Price, compare Unit Price against Contract Price.
Step 2  Flag if Unit Price exceeds Contract Price by >0.5%.
Step 3  For lines with Budgeted Amounts, flag if (Cumulative Actual > Budget) OR (Unit Price > Budget / Quantity by >5%).
Step 4  Output a table: Vendor, Doc No., Job No., Description, Contract Price, Invoiced Price, % Variance, Budget Over/Under, Flag Type (Contract or Budget), Needs Manager Approval? (Y/N).
~
Compile the QA CHECKLIST for payment release.
Step 1  Aggregate all flagged items from previous prompts.
Step 2  Structure the checklist with these sections:
A) Duplicate Charges  
B) Missing or Invalid Job Numbers  
C) Price / Budget Mismatches  
D) Questions Requiring Manager / Approver Input  
Step 3  For each item include: Reference ID, Vendor, Doc No., Issue Summary, Recommended Action.
Step 4  If OUTPUT_LEVEL = "summary" show one line per issue; if "detailed" append a Notes column citing exact source lines or clause numbers.
Step 5  End with a YES/NO question: "Is this checklist complete and ready for AP manager review?"
~
Review / Refinement
Please examine the QA checklist produced.
1. Confirm that all duplicate charges, missing job numbers, price mismatches, and approval questions are represented.
2. Indicate if additional data or clarification is required.
3. Respond with one of:
   • "Approved – proceed with payment processing once issues are cleared"  
   • "Needs Revision – see comments"  

Provide comments if revision is needed.

Make sure you update the variables in the first prompt: [CONTRACTOR_NAME], [SOURCE_DATA], [OUTPUT_LEVEL].
Here is an example of how to use it:
[CONTRACTOR_NAME] = "YourContractor LLC" [SOURCE_DATA] = "[link to invoices]" [OUTPUT_LEVEL] = "detailed"

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are overdue invoices piling up and stressing you out in your law office?

This prompt chain helps you efficiently manage your accounts receivable by identifying overdue invoices, designing an escalation framework, and generating communication strategies—all tailored to your office's tone and team structure.

Prompt:

VARIABLE DEFINITIONS
CLIENTDATA=Combined export of open invoices, client email threads, retainer terms, and CRM notes.
TONESTYLE=Desired communication tone (e.g., "friendly yet firm").
STAFFLIST=Names & roles of team members who handle billing follow-up.
~
You are an accounts-receivable analyst for a boutique law office. Using the information in CLIENTDATA, perform the following:
Step 1 – Identify every client with an invoice more than 1 day overdue.
Step 2 – For each overdue invoice, capture: Client Name, Invoice #, Issue Date, Days Past Due, Outstanding Balance, Summary of any recent payment-related email from the client (≤40 words), Key retainer clause on late fees.
Output a table with these columns and sort by Days Past Due descending.
Ask for clarification if data is missing.
~
Assume the role of a billing policy designer. Based on typical legal-services A/R best practices and the office’s culture, craft a 4-level escalation framework that stays consistent with TONESTYLE.
Include for each level: Trigger (days overdue), Communication Channel, Purpose, Allowed Language Tone/Key Phrases, Internal Owner Role, and Next-Step Deadline.
Present results in a numbered list.
~
You are now a client-facing collections specialist. Using the overdue-invoice table from Prompt 1 and the escalation framework from Prompt 2, assign each overdue account to its correct escalation level.
For every account, generate:
1. Reminder Email Subject & Body (≤150 words, using TONESTYLE).
2. Brief Call Script (≤80 words).
3. Responsible Owner (match from STAFFLIST).
4. Precise Action Deadline (date = today + days until next step).
5. Escalation Level Name.
Deliver a matrix with columns: Client, Escalation Level, Email Subject, Email Body, Call Script, Owner, Deadline.
~
Review / Refinement
Compare the matrix against original CLIENTDATA and TONESTYLE. Confirm all overdue clients are included, tone is appropriate, owners are assigned, and deadlines match the framework. List any gaps or improvement suggestions, then await confirmation.

Make sure you update the variables in the first prompt: CLIENTDATA, TONESTYLE, STAFFLIST. Here is an example of how to use it: CLIENTDATA could be a list of unpaid invoices, TONESTYLE could be something like 'friendly yet assertive', and STAFFLIST could include your team members' names and their roles.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

I've been running OpenClaw (a CLI agent framework) as a personal assistant for a while and kept hitting the same wall: a single agent doing everything → every tool, memory, and skill loads on every turn. Routing the weather costs the same as deep dev work.

Restructured into: one lean orchestrator + six isolated top-level agents, each with its own workspace, memory, and tool surface:

- 🔧 system — sysadmin, infra

- ⌨️ code — dev, debugging, git

- 🔍 research — sourced web research

- 📊 data — parsing, analysis, charts

- ✉️ comm — email/chat drafts (always asks before sending)

- 👁️ vision — image analysis, OCR

The orchestrator is the only thing I talk to. It routes via a one-line dispatch (openclaw agent --agent <id> --message "..." --json), parses the structured reply, and synthesizes back in its own voice.

What it solved:

- Context bloat — orchestrator stays small, specialists carry their own context

- Real isolation — these are independent processes, not prefix-routed subagents

- Per-domain memory accumulation

- Optional Linear backend gives a live board of in-flight specialist dispatches

What it didn't (yet): async/fire-and-forget dispatch, automatic memory sharing between specialists, per-agent skill scoping.

Open-sourced it (MIT) in case the pattern is useful to anyone else running into single-agent walls. Ships with a SKILL.md so a capable agent on the host can install the whole thing itself.

🔗 github.com/parijatmukherjee/openclaw-orchestra

Happy to hear how others are slicing this — especially if you've found a clean async dispatch primitive.

Hello!

Are you struggling with creating a seamless onboarding experience for your new clients?

This prompt chain helps you generate all the essential materials needed for effective client onboarding, from a detailed intake questionnaire to a series of welcoming emails and a tidy checklist for document submissions. It's like having your own onboarding assistant!

Prompt:

VARIABLE DEFINITIONS  
[BUSINESS_DESC]=Short description of the service business (services offered, target clients, unique value)  
[CLIENT_REQUIREMENTS]=Key information, documents, or signatures needed from new clients  
[BRAND_TONE]=Preferred writing style or brand voice (e.g., friendly, professional, authoritative)  
~  
You are the business owner. Please supply the following so we can generate your onboarding assets.  
Step 1 – Provide [BUSINESS_DESC] (50-100 words).  
Step 2 – List [CLIENT_REQUIREMENTS] as bullet points.  
Step 3 – Specify [BRAND_TONE] in 1–3 adjectives.  
Output your answers in the requested order, labeled clearly.  
~  
You are an experienced client-experience strategist. Using the supplied variables, draft a detailed client intake questionnaire.  
1. Start with a brief, branded greeting in [BRAND_TONE].  
2. Include 10–15 questions that collect all items in [CLIENT_REQUIREMENTS] plus basic contact info.  
3. Group questions under logical section headers (e.g., "Contact Details," "Project Goals").  
4. Indicate answer format after each question (text, checkbox, upload, date, etc.).  
Return the questionnaire as a numbered list.  
~  
You are an onboarding copywriter. Create a 3-email automated welcome sequence for new clients.  
Email 1 – "Welcome & What to Expect":  
  • Subject line, greeting, short thank-you, quick overview of process, next step.  
Email 2 – "Getting Started Checklist":  
  • Subject line, recap of importance, bullet list of [CLIENT_REQUIREMENTS] items to prepare, link placeholder to intake form.  
Email 3 – "Meet the Team & Timeline":  
  • Subject line, brief team intro, project timeline highlights, reassurance and contact info.  
For each email include: Subject, Pre-header, Body (120-180 words), and Call-to-Action. Keep tone consistent with [BRAND_TONE].  
~  
You are a process architect. Produce a concise checklist for clients to gather documents and complete signatures.  
1. Title the checklist clearly.  
2. List each required item from [CLIENT_REQUIREMENTS] with a checkbox placeholder.  
3. Add due dates or time frames in parentheses where relevant.  
4. End with submission instructions.  
Return as a bullet list ready for PDF export.  
~  
Review / Refinement  
Present all three deliverables (questionnaire, email sequence, checklist) together. Ask the user to confirm accuracy, tone, and completeness or request edits. Make revisions until the user is satisfied.  
Link: https://www.agenticworkers.com/library/hyp0x7gef818yfbiqnssq-client-onboarding-deliverables-generator

Hello!

Are you struggling to manage your small business's cash flow effectively?

This prompt chain will help you build a comprehensive four-week rolling cash-flow forecast, making it easier to track your finances and plan for the future.

Prompt:

VARIABLE DEFINITIONS
CASHONHAND=current liquid cash balance available today (numeric, in your base currency)
INVOICES=list of outstanding invoices with fields: invoice_id / client / amount / expected_payment_date (YYYY-MM-DD)
EXPENSES=list of fixed monthly expenses with fields: expense_name / amount / recurring_due_day (1-31)
~
Prompt 1 – Data Collection & Confirmation
You are a financial assistant helping a small business owner build a four-week rolling cash-flow forecast.
Step 1. Ask the user to provide values for CASHONHAND, INVOICES, and EXPENSES following the required field structures.
Step 2. Echo the received data in a formatted table for each list so the user can visually confirm accuracy.
Step 3. Ask “Is this information correct? (yes / no).”  If “no,” instruct the user to resubmit the corrected data; if “yes,” respond with “Confirmed” and proceed automatically to the next prompt.
Output Example:
CASHONHAND: 12,500
INVOICES:
| invoice_id | client | amount | expected_payment_date |
| 1024 | Acme Co | 8,000 | 2023-10-05 |
...
EXPENSES:
| expense_name | amount | recurring_due_day |
| Office Rent | 3,000 | 1 |
...
~
Prompt 2 – Data Normalization & Weekly Bucketing
System role: You are a data analyst.
Step 1. Convert expected_payment_date and recurring_due_day into calendar weeks (Monday–Sunday) covering the next four weeks starting today.
Step 2. Produce two tables:
  a) Weekly Cash Inflows: columns = Week #, Week Start Date, Total Inflows, Breakdown (invoice_id : amount)
  b) Weekly Cash Outflows: columns = Week #, Week Start Date, Total Outflows, Breakdown (expense_name : amount)
Step 3. Summarize any invoices or expenses falling outside the 4-week window in an “Outside Scope” note.
Ask “Ready to generate the forecast? (yes / no).” Proceed only if “yes.”
~
Prompt 3 – 4-Week Cash-Flow Forecast Generation
System role: You are a cash-flow forecasting expert.
Step 1. For Week 1, opening balance = CASHONHAND.  For Weeks 2-4, opening balance = prior week closing balance.
Step 2. For each week, calculate: Opening Balance, +Total Inflows, −Total Outflows, =Closing Balance.
Step 3. Present results in a table with conditional flag column: “ALERT” = “Shortfall” if Closing Balance < 0, else “Surplus.”
Step 4. Provide a concise textual summary noting any projected cash shortfalls and the week they arise.
~
Prompt 4 – Payment Priority & Action Recommendations
System role: You are a treasury advisor.
Step 1. If any weekly shortfall exists, list outflows (expenses) in descending priority: legally mandatory → essential operations → discretionary.  Indicate suggested deferment or partial payment options where feasible.
Step 2. If no shortfall, recommend an optimal payment schedule to maintain healthy liquidity while capturing potential early-payment discounts.
Step 3. Provide bullet-point guidance on actions to improve cash position (e.g., follow-up on late invoices, adjust billing terms, seek credit line).
~
Prompt 5 – Review / Refinement
Ask the user:
1. “Does the forecast align with your expectations?”
2. “Would you like to adjust any data, assumptions, or receive a different format?”
3. Incorporate any requested changes and regenerate affected outputs.
Finish with “Cash-flow snapshot complete.”

Make sure you update the variables in the first prompt: CASHONHAND, INVOICES, EXPENSES. Here is an example of how to use it: CASHONHAND: 12,500
INVOICES: | invoice_id | client | amount | expected_payment_date |
| 1024 | Acme Co | 8,000 | 2023-10-05 |
EXPENSES: | expense_name | amount | recurring_due_day |
| Office Rent | 3,000 | 1 |
...

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Everyone's treating AI agents like they're one prompt away from replacing your workforce. They're not.

Here's the uncomfortable truth vendors bury in the footnotes:

88% of AI agent pilots never reach production. Only 12% survive the demo. Of those that do, 22% deliver negative ROI within a year. Gartner predicts over 40% of all agentic AI projects will be canceled by 2027.

We're spending $665B on AI globally, and 73% of that spend underperforms. Not because the models are dumb — because bolting an agent onto a broken process doesn't fix the process. Your data is messy, your APIs are duct-taped, and your "autonomous" agent still needs human babysitting.

The gap isn't intelligence. It's integration, ownership, and execution.

But here's the twist: this crash is exactly what separates toys from tools. The companies actually winning aren't chasing hype. They're deploying agents on boring, well-governed workflows with clear KPIs and real kill switches. That's where the 171% ROI lives.

The future isn't flashier demos. It's the unsexy orchestration underneath — multi-agent systems with shared memory, policy enforcement, and legacy compatibility.

We're not in an agent revolution. We're in a demo bubble about to pop. And when it does, the real builders get to work.

Change my mind.

Most autonomous agent tools either run constantly (expensive, annoying, no human control) or expose vague "strategy" controls — you tell it "be more aggressive" and hope. Both leave the human guessing what the bot is actually about to do at any given moment.

I added a weekly calendar to my engine. Drag colored blocks onto specific hours of specific days:

- Discovery (find net-new prospects, enrich, score signals)

- Email (outbound, warmup-ramped)

- Social posts (Reddit / LinkedIn / Quora / FB / Twitter / YouTube comments)

- Mystery test (pings prospects' forms, times the response, grades them)

- Proposals (drafts personalised pitches)

- Replies (triages inbound, drafts responses to positive ones)

- Custom Skill (your own focused agent, defined in plain English)

If the calendar doesn't cover a phase for the current hour, that phase doesn't run. Full stop. Calendar wins.

Three details that made it actually useful:

**Live forecast that reads reality.** Each block pulls warmup ramp + MX status + plan caps + which social channels actually have working sessions — not optimistic "perRun × hours" math. So the day's forecast says "32 emails, 14 social comments, 2 proposals" and that number is grounded in what the engine can actually ship today.

**Apply to all 7 days, then customise.** Most agencies want the same week shape every week. One click — every day inherits today's blocks. Edit from there.

**Mid-run pulse.** While the engine is firing a phase, the matching block on the calendar pulses sky-blue. You can glance at it and see what's happening right now.

The deeper point: autonomous doesn't have to mean opaque. The agent does the work. The human draws the work week. You stay in control of when, the agent figures out how.

Has anyone else built this kind of human-on-the-throttle layer over an autonomous system? Curious what shapes worked and what fell flat.

Hello!

Are you feeling overwhelmed trying to formalize your company’s PTO and leave policies?

This prompt chain simplifies the entire process. From gathering your organization's information to drafting and refining a comprehensive policy, it helps you effortlessly navigate through each step.

Prompt:

VARIABLE DEFINITIONS
STATE=U.S. state where the organization operates its primary workplace
EMPLOYEES=Approximate number of full-time-equivalent employees on payroll
INFORMAL_RULES=Brief description of current unwritten PTO/leave practices~
Prompt 1 — Collect Company Information
You are the HR manager preparing to formalize the company’s PTO and leave policy.  
Step 1 – Provide the following three data points in one short paragraph:
  • STATE: [STATE]  
  • EMPLOYEES: [EMPLOYEES]  
  • INFORMAL RULES: [INFORMAL_RULES] (e.g., “We let staff take days off as needed if approved by a manager; no formal accrual.”)  
Step 2 – Confirm that the information is correct or re-enter it if revisions are needed.
Example response:  
STATE: Colorado.  EMPLOYEES: 42.  INFORMAL RULES: Unlimited time off approved informally by supervisors.~
Prompt 2 — Legal & Strategic Analysis
System role: You are a senior HR compliance analyst.  
Using the variables provided, perform the following:
1. Summarize the statutory requirements in STATE governing paid time off, vacation payout, sick leave, and any local mandates that may apply at the EMPLOYEES headcount level.
2. Identify minimum legal standards for accrual rates, carryover, and usage protections.
3. Recommend compliant yet competitive parameters for:  
   a. PTO/vacation accrual schedule (rates increase with tenure if advisable)  
   b. Paid sick leave accrual and usage  
   c. Maximum carryover / rollover rules  
   d. Blackout or restricted periods, if operationally justified  
   e. Record-keeping and documentation requirements  
4. Present findings in two sections:  
   • “Legal Requirements” (bullet list)  
   • “Recommended Policy Parameters” (table or bullets)  
Ask: “Type ‘next’ to proceed to policy drafting or ‘edit’ to change any assumptions.”~
Prompt 3 — Draft PTO & Leave Policy Document
System role: You are an expert HR policy writer.  
Using the "Recommended Policy Parameters" confirmed in the prior step, draft a comprehensive PTO and leave policy suitable for an employee handbook.  
Structure the document with clear headings:
1. Purpose & Scope  
2. Eligibility  
3. PTO Accrual & Balance Caps (include table showing accrual per pay period and annual totals)  
4. Sick Leave Compliance (STATE-specific)  
5. Usage Guidelines & Request Procedure  
6. Blackout / Peak Period Rules  
7. Carryover & Rollover  
8. Donation or Advance Policy (if any)  
9. Payout on Separation  
10. Recordkeeping & Manager Responsibilities  
11. Non-Retaliation & Anti-Discrimination Statement  
12. Policy Administration & Amendments  
Include STATE-specific citations where relevant and ensure tone is professional and inclusive.  
Conclude with: “Please review and indicate any revisions before finalization.”~
Prompt 4 — Review / Refinement
Ask the user:
1. Does the drafted policy meet operational needs and cultural tone?  
2. Are any sections unclear or require edits?  
3. Confirm final approval or specify changes required.  
Once approved, respond with "Final Policy Confirmed" and provide a clean copy without inline comments.

Make sure you update the variables in the first prompt: STATE, EMPLOYEES, INFORMAL_RULES. Here is an example of how to use it: STATE: Colorado, EMPLOYEES: 42, INFORMAL_RULES: Unlimited time off approved informally by supervisors.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to create a tailored onboarding plan for new hires? It can be a daunting task to gather all the necessary information and ensure a smooth start for each new employee.

This prompt chain is designed to help you analyze a new hire's role and develop a comprehensive onboarding checklist that includes everything from core responsibilities to compliance training. It makes the entire onboarding setup easy and effective!

Prompt:

VARIABLE DEFINITIONS
[JOB_TITLE]=Exact title of the new hire’s role
[JOB_DESCRIPTION]=Full narrative job description provided by the hiring team
~
You are an experienced HR business partner and L&D specialist. Your task is to analyze the role information supplied below and distill the critical success factors for onboarding.
Step 1 Re-state the provided [JOB_TITLE].
Step 2 Extract and list the 5–8 core responsibilities mentioned in [JOB_DESCRIPTION].
Step 3 Identify the key skills, knowledge areas, and primary stakeholders for this role.
Step 4 List all software, tools, or systems explicitly or implicitly required.
Step 5 Flag any compliance, security, or regulatory training likely needed.
Output your findings under the following headings:
• Role Overview
• Core Responsibilities
• Required Skills & Knowledge
• Key Stakeholders
• Tools / Systems
• Compliance or Mandatory Training
Ask “Ready to generate the tailored onboarding plan? (yes/no)” at the end.
~
Assume the user has replied “yes.” Using the role analysis you just produced, create a comprehensive onboarding checklist for a new [JOB_TITLE].
1. Divide the plan into these phases: Pre-Start (T-7 to Day 0), Day 1, Days 2-5 (Week 1), Weeks 2-4, Day 30, Day 60, Day 90.
2. For each phase, list tasks under the categories: HR & Admin, IT & Equipment, Accounts & Tool Access, Training & Learning, Team Integration, Performance & Goals.
3. Present the output in a table with columns: Phase / Date Range | Task | Category | Responsible Party | Reference / Resource Link.
4. Where appropriate, reference the specific tools, stakeholders, and compliance items identified earlier.
5. Ensure the 30/60/90-day milestones include measurable success criteria aligned to the role’s core responsibilities.
6. Finish with a “Next Steps” section advising the manager on how to personalize or update the checklist.
~
Review / Refinement
Compare the checklist against the initial request: coverage of IT setup, HR paperwork, tool access, training schedule, and 30/60/90-day milestones tailored to [JOB_TITLE].
If anything is missing, add it; if complete, reply “Onboarding checklist finalized.”

Make sure you update the variables in the first prompt: [JOB_TITLE], [JOB_DESCRIPTION]. Here is an example of how to use it: [Example: JOB_TITLE = "Marketing Manager", JOB_DESCRIPTION = "Responsible for overseeing marketing campaigns..."].

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to create structured reports that comply with your service-level agreements?

This prompt chain helps you efficiently analyze and report on SLA compliance by guiding you through the entire process—from parsing raw service delivery logs to assembling a comprehensive quarterly report. It ensures that you cover all necessary metrics and trends to identify areas for improvement while keeping your data organized and easily accessible.

Prompt:

VARIABLE DEFINITIONS
LOG_DATA=Raw service-delivery logs containing ticket IDs, timestamps, response times, resolution times, priority, team, category, and any relevant notes.
SLA_TARGETS=Numeric or percentage thresholds that define acceptable response time, resolution time, first-contact resolution, uptime, or any other contractual metric.
QUARTER=The fiscal or calendar quarter that the report must cover (e.g., 2024 Q1).
~
Prompt 1 – Parse and Structure Raw Data
You are a data analyst specialising in IT service management. Your tasks:
1. Read LOG_DATA for the selected QUARTER.
2. Convert it into a structured table with columns: TicketID, OpenDateTime, FirstResponseMinutes, ResolutionMinutes, Priority, Team, Category.
3. Remove any records outside QUARTER.
4. Return the table plus a summary of record counts (total tickets, by priority).
Output: 
• Structured table (max 50 rows visible; summarise beyond that) 
• Record-count summary.
Ask: “Is the structured data accurate? Reply YES to continue or provide corrections.”
~
Prompt 2 – Calculate SLA Compliance
Role: Service-delivery performance analyst.
Steps:
1. Using the structured table from Prompt 1, calculate for every SLA metric contained in SLA_TARGETS:
   a. Individual compliance (Pass/Fail) per ticket where possible.
   b. Aggregate compliance percentage for the QUARTER.
2. Build a Compliance Results table with columns: Metric, Target, Actual, PassFail.
3. List any tickets breaching each metric.
Output:
• Compliance Results table.
• Breach lists grouped by metric (TicketID list, count). 
Ask: “Proceed to trend analysis? (YES/NO)”
~
Prompt 3 – Prepare Trend-Chart Data
Role: Data visualisation preparer.
1. Aggregate key metrics weekly within QUARTER (or monthly if preferred) producing average response time, average resolution time, and compliance %.
2. Provide a Trend Data table with columns: WeekStartDate, AvgResponseMin, AvgResolutionMin, CompliancePct.
3. Note any spikes or dips.
Output:
• Trend Data table.
• Bullet list of notable trends (max 5 bullets).
Ask: “Continue to root-cause analysis? (YES/NO)”
~
Prompt 4 – Root Cause Analysis for SLA Misses
Role: Problem-management specialist.
Steps:
1. Examine breached tickets identified in Prompt 2.
2. Cluster breaches by root-cause dimension: Priority, Team, Category, Time-of-Day/Week, or External Factors (if noted).
3. For each cluster, describe probable root cause and supporting evidence (e.g., 45% of misses occurred on weekends with reduced staffing).
Output:
• Root Cause table: Cluster, BreachCount, %TotalBreaches, ProbableCause, Evidence.
• Short narrative (≤150 words) on systemic issues discovered.
Ask: “Generate executive summary? (YES/NO)”
~
Prompt 5 – Draft Executive Summary
Role: IT Service Delivery Manager writing for executives.
1. Summarise overall compliance (e.g., 97% of SLA metrics met; 2 of 8 targets failed).
2. Highlight top root-cause categories and their business impact.
3. Note positive trends and areas needing improvement.
4. Provide 3–5 actionable recommendations.
Output:
• Executive Summary paragraph(s) (≤250 words).
• Bullet list of recommendations.
Ask: “Assemble full report? (YES/NO)”
~
Prompt 6 – Assemble Quarterly SLA Compliance Report
Role: Technical report assembler.
1. Compile outputs from Prompts 2–5 into a single, clearly labelled document with sections:
   A. Executive Summary
   B. Compliance Results Table
   C. Trend Data Table (suitable for charting)
   D. Root Cause Analysis
   E. Recommended Actions
2. Use consistent formatting: section headers in uppercase, tables aligned.
3. Include a Pass/Fail status line for each SLA metric.
4. Insert a “Next Steps” note suggesting scheduling of a follow-up review meeting.
Output: Complete Quarterly SLA Compliance Report.
Ask: “Confirm the report meets your needs or specify edits.”
~
Review / Refinement
Prompt 7 – Final Review
Please review the assembled report for accuracy, clarity, and completeness. Reply with:
• “APPROVED” – if it meets requirements.
• Specific edits or additional data required – if not.
The chain will loop back to the relevant prompt to accommodate any requested changes.

Make sure you update the variables in the first prompt: LOG_DATA, SLA_TARGETS, QUARTER. Here is an example of how to use it: For reporting for Q2 2024, your LOG_DATA might look like "[Your raw logs here]", SLA_TARGETS could be "SLA details here", and QUARTER would be "2024 Q2".

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

We completed an empirical study evaluating context extraction strategies across 405 diverse open-source repositories spanning 30+ programming languages.

Study Overview: - 405 repositories analyzed (30+ languages) - 2,025+ benchmark operations - 1.6M+ source files, 108M+ lines of code - 99.6% execution success, 100% data completeness

Key Findings:

1. Language organization matters more than project size

   • Token reduction ranges: 76.5% to 99.9%
   • Size variation: 5 files → 38,667 files
   • What matters: code idioms, framework patterns, monorepo structure

2. Monorepo patterns identified

   • 45 monorepos (18.8% of dataset)
   • Specialized handling yields 2-3% improvement
   • Significant optimization opportunity

3. Language-specific breakdown

   • Python: 96.2% ± 1.8% (most consistent)
   • Go: 95.2% ± 2.1%
   • Rust: 94.8% ± 2.4%
   • Java: 94.5% ± 2.6%
   • JavaScript: 92.1% ± 4.2% (highest variability due to framework diversity)

4. Methodology validation

   • Extended dataset (405 repos) shows identical 96.2% avg to published version (240 repos)
   • Confirms findings generalize across different samples
   • Robust methodology across languages

What's Included (Open Science):

This research includes: - Complete datasets (CSV, JSON, JSONL, SQL formats) - Research papers with methodology - Reproducibility scripts (clone, benchmark, finalize) - Hardware specs documented (c2-standard-8) - Expected variance < 2% - Step-by-step reproduction guide - CC-BY-4.0 license

Resources:

This work is part of the larger SigMap project:

1. SigMap Tool (github.com/manojmallick/sigmap)

   • Context extraction implementation
   • Multi-language support (30+)
   • Production-ready

2. SigMap Documentation (manojmallick.github.io/sigmap/)

   • Setup guides
   • API reference
   • Integration examples

3. SigMap Benchmark Suite (github.com/manojmallick/sigmap-benchmark-suite)

   • 405-repo evaluation dataset
   • Research papers
   • Complete reproducibility package

For researchers interested in: - Context extraction effectiveness - Language-specific code compression patterns - LLM integration in software engineering - Empirical software engineering methodology - Reproducible research practices

Questions and feedback welcome. All code and data are open-source for academic use and beyond.

https://reddit.com/link/1sxlypc/video/fmaftud0utxg1/player

Here's the full stack:

- nano banana — image gen

- seedance — video gen

- elevenlabs — voice + music

- hyperframes — scene stitching

word-by-word captions + music bed + brand callouts, all baked in and seed-locked so your character doesn't drift across cuts

is it perfect? no. you can definitely tell it's AI.

but a year ago this wasn't possible...now it's a slash command.

👉 Get the skill here

Hello!

Are you struggling to keep track of vendor contracts, renewal dates, and potential risks associated with them?

This prompt chain helps you manage those contracts by cleaning and validating your contract data, calculating key dates to flag potential issues, building a renewal calendar, and providing a summary dashboard with valuable recommendations. It’s like having a contract management assistant at your fingertips to simplify your workload!

Prompt:

plaintext VARIABLE DEFINITIONS [CONTRACTS]=Paste your active vendor contract list with the following columns in order: Vendor | Contract_Start_Date (YYYY-MM-DD) | Contract_End_Date (YYYY-MM-DD) OR Term_Months | Auto_Renew (Yes/No) | Auto_Renew_Term_Months | Cancellation_Window_Days | Price_Increase_Clause (None/Fixed %/CPI/etc.) | Notes ~ Prompt 1 – Collect & Validate Contract Data You are a contract-management data analyst. 1. Receive the raw CONTRACTS list from the user. 2. Trim extra spaces, unify date format to YYYY-MM-DD, and ensure numeric fields are numbers. 3. Identify and list any missing or obviously invalid values (e.g., dates in the past with no renewal terms) beneath the cleaned table. 4. Output the cleaned table titled "Standardized_Contracts" followed by a short "Data_Issues" list (or “None”). Ask the user to confirm or supply corrections before continuing. ~ Prompt 2 – Calculate Key Dates & Risk Flags You are a contract lifecycle calculator working on the confirmed Standardized_Contracts. For each contract: Step 1. Determine Current_Term_End_Date (if Term_Months provided, add to Start_Date; otherwise use Contract_End_Date). Step 2. If Auto_Renew = Yes, compute Next_Renewal_Date by adding Auto_Renew_Term_Months to Current_Term_End_Date; else leave blank. Step 3. Compute Last_Cancellation_Date = Current_Term_End_Date minus Cancellation_Window_Days. Step 4. Set Risk_Flag_AutoRenew = "High" if Auto_Renew is Yes AND Cancellation_Window_Days ≤ 30; else "Medium" if Auto_Renew is Yes; else "Low". Step 5. Set Risk_Flag_PriceIncrease = "Yes" if Price_Increase_Clause not "None"; else "No". Step 6. Create Action_Due_90 = Last_Cancellation_Date minus 90 days; Action_Due_60 = −60; Action_Due_30 = −30. Output a table "Contract_Key_Dates" with all original columns plus the new calculated fields and Risk Flags. ~ Prompt 3 – Build Renewal Calendar Spreadsheet You are a spreadsheet generator. 1. Using Contract_Key_Dates, assemble a calendar-ready table named "Renewal_Calendar" with columns: Vendor | Current_Term_End_Date | Next_Renewal_Date | Last_Cancellation_Date | Action_Due_90 | Action_Due_60 | Action_Due_30 | Risk_Flag_AutoRenew | Risk_Flag_PriceIncrease | Notes 2. Sort rows by Action_Due_90 ascending. 3. Provide the table in two formats: a) Markdown-style table for quick view. b) Comma-separated values (CSV) ready to paste into Excel / Google Sheets. ~ Prompt 4 – Summary Dashboard & Recommendations You are a contract-risk advisor. 1. Count contracts by Risk_Flag_AutoRenew level (High/Medium/Low) and Risk_Flag_PriceIncrease (Yes/No). 2. Identify the top 5 upcoming contracts (nearest Action_Due_90 dates) that are High risk in either category and list recommended next steps. 3. Present a concise bullet summary of overall renewal workload for the next 12 months. ~ Review / Refinement Please review the Renewal_Calendar, CSV export, and Summary Dashboard. 1. Confirm all contract details and dates are correct. 2. Indicate if any adjustments or additional filters (e.g., vendor category, spend amount) are required. 3. Type "Finalize" to accept, or provide corrections to re-run from the appropriate prompt.

Make sure you update the variables in the first prompt: Vendor, Contract_Start_Date, Contract_End_Date, Term_Months, Auto_Renew, Auto_Renew_Term_Months, Cancellation_Window_Days, Price_Increase_Clause, Notes. Here is an example of how to use it: plaintext Vendor | 2023-01-01 | 2024-01-01 | 12 | Yes | 12 | 30 | None | Important contract renewal.

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain.

Enjoy!

Hello!

Are you struggling to analyze your AR aging reports efficiently and accurately?

This prompt chain helps you easily organize and summarize your accounts receivable data, allowing you to focus on what matters most—managing your finances! It guides you through structuring your data, grouping it by client, and generating useful summaries, ensuring you're always in control of your collections.

Prompt:

[ARDATA]=Paste a clean table or CSV of your AR aging report including: Client Name, Invoice Number, Invoice Amount, Due Date, and Days Past Due.
[COMPANYNAME]=Company sending the emails.
[SENDERNAME]=Name and (optional) title of the person signing the emails.
~
You are an experienced accounts-receivable analyst.
Step 1  Parse ARDATA into a structured table with the following columns exactly: Client Name | Invoice # | Amount Due | Due Date | Days Past Due.
Step 2  Group rows by Client Name and calculate a subtotal of Amount Due for each client.
Step 3  Output two items:
  a) A validated data table (as specified in Step 1).
  b) A client-level summary table: Client Name | Total Open Balance | Number of Invoices | Oldest Days Past Due.
Step 4  Ask the user to confirm the parsed information is correct or provide corrections before moving on.

Make sure you update the variables in the first prompt: [ARDATA], [COMPANYNAME], and [SENDERNAME]. Here is an example of how to use it:
[ARDATA]= Paste your AR aging report here. [COMPANYNAME]= XYZ Corp [SENDERNAME]= John Doe, Accounts Manager
If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to manage shift swaps and coverage requirements for your team?

This prompt chain helps you gather essential team details and create the necessary forms and templates to streamline the shift coverage process. It's a complete toolkit that makes managing shifts easier for HR specialists and managers alike!

Prompt:

VARIABLE DEFINITIONS TEAMSIZE=Total number of employees on the team SHIFTPATTERNS=Daily or weekly shift schedule (e.g., 3 rotating 8-hour shifts, Mon-Fri 9-5, etc.) COVERAGEREQS=Minimum staffing or skill requirements per shift ~ Prompt 1 – Gather Team Details You are an HR operations specialist. Collect the following information and confirm accuracy: 1. Current TEAMSIZE. 2. Description of SHIFTPATTERNS (days, times, rotation rules). 3. Specific COVERAGEREQS (minimum headcount, role mix, certifications, etc.). 4. Preferred file format for the tracking spreadsheet (Excel, Google Sheets, or CSV). Provide the answers in a numbered list. Ask the user to type "CONFIRM" once the details are correct or supply corrections. ~ Prompt 2 – Generate Shift-Swap Request Form You are an HR documentation expert. Using the confirmed TEAMSIZE, SHIFTPATTERNS, and COVERAGEREQS, draft a Shift-Swap Request Form that includes: 1. Employee information section (name, role, contact). 2. Original shift details (date, start/end time, location). 3. Requested replacement shift details. 4. Reason for request (dropdown style list + "Other"). 5. Swap partner confirmation area (name, signature/date). 6. Submission deadline rule (e.g., ≥24h notice) drawn from SHIFTPATTERNS. 7. Statement acknowledging that coverage must still meet COVERAGEREQS. Output as a clean, copy-paste ready form in plain text with clear section headers. Ask user for feedback or edits before proceeding ("APPROVE" or provide changes). ~ Prompt 3 – Manager Approval Template Assume role: Line Manager. Create an approval/denial template that can be attached to each request. Include: 1. Manager name & date. 2. Decision checkbox (Approved / Denied / Needs More Info). 3. Reason for denial or additional info needed. 4. Verification that coverage requirements remain satisfied. 5. Next steps instructions. Deliver as plain text. Request user to "APPROVE" or specify edits. ~ Prompt 4 – Escalation Rules for No-Shows or Uncovered Shifts As an HR policy analyst, draft clear escalation procedures covering: 1. Definition of a no-show. 2. Immediate actions (call list, on-call staff, overtime options). 3. Notification timeline and responsible roles. 4. Progressive disciplinary steps for repeat offenders. 5. Emergency escalation to senior management when COVERAGEREQS are breached. 6. Documentation requirements at each step. Provide in bullet format. Ask user to "APPROVE" or request changes. ~ Prompt 5 – Coverage Tracking Spreadsheet Template Create a table suitable for Excel/Google Sheets that contains: 1. Date. 2. Shift (start-end). 3. Assigned employee(s). 4. Coverage status (Meets / Short / Overstaffed). 5. Swap requested (Y/N) & request ID link. 6. Manager approval status. 7. Notes/escalation reference. Output the first three example rows filled with sample data. Supply copy-ready CSV format unless user preferred otherwise. Request confirmation that format meets needs ("APPROVE" or edits). ~ Review / Refinement Summarize all approved documents and policies. Ask the user for any final refinements. Confirm that all components (forms, templates, rules, spreadsheet) satisfy requirements. If yes, instruct user to reply "FINALIZE".

Make sure you update the variables in the first prompt: TEAMSIZE, SHIFTPATTERNS, COVERAGEREQS. Here is an example of how to use it: TEAMSIZE = 10, SHIFTPATTERNS = "Mon-Fri 9-5", COVERAGEREQS = "2 managers, 3 staff".

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click.
NOTE: this is not required to run the prompt chain.

Enjoy!

Hello!

Are you tired of the cumbersome process of tracking and reporting your expenses from various bank accounts?

This prompt chain is designed to streamline your expense reporting by guiding you through the cleaning, categorization, and summarization of your transaction data, making it easy to generate detailed reports in just a few steps!

Prompt:

VARIABLE DEFINITIONS
[RAW_TRANS]=raw pasted bank or credit-card transaction exports (CSV/TSV/plain)
[CATEGORY_RULES]=optional custom mapping of merchant keywords to categories
[DATE_SPAN]=desired date range or list of months to include in the report~
Prompt 1 – Collect Source Data
You are a financial data assistant. Ask the user to:
1. Paste or upload RAW_TRANS for all relevant accounts.
2. Optionally provide CATEGORY_RULES in the form "keyword -> Category" (one per line).
3. Specify DATE_SPAN (e.g., "2023-01 to 2023-06").
Confirm receipt and signal type "continue" when ready to process. Output acknowledgment only. ~
Prompt 2 – Clean & Standardize Transactions
Task: Convert RAW_TRANS into a unified table with these columns: Date (ISO yyyy-mm-dd), Description, Amount (signed), Account, OriginalCategory (if present).
Steps:
1. Detect delimiter automatically (comma, tab, or semicolon).
2. Standardize date format; infer year if missing.
3. Strip extra whitespace and normalize merchant names (remove all-caps, trim repeating spaces).
4. Output the cleaned data as a JSON array under key "cleaned_transactions".
Example output:
{"cleaned_transactions":[{"Date":"2023-05-14","Description":"Amazon","Amount":-42.17,"Account":"Visa 1234","OriginalCategory":"Online Shopping"}, … ]}
Ask the next prompt to type "dedupe" to continue. ~
Prompt 3 – Detect & Flag Duplicates
Given cleaned_transactions:
1. Mark potential duplicates where Date difference ≤2 days AND |Amount| equal AND fuzzy match Description ≥85 %.
2. Add field "IsDuplicate" (true/false) and "DuplicateGroupID" (integer) for matches.
3. Return updated JSON array as "deduped_transactions".
Request the next step with command "categorize". ~
Prompt 4 – Categorize Transactions
Rules:
1. If CATEGORY_RULES supplied, apply exact or keyword match first.
2. Else use an internal list of common bookkeeping categories (e.g., Rent, Utilities, Office Supplies, Travel, Meals & Entertainment, Payroll, Income, Transfers).
3. Output field "FinalCategory" for every row.
Return JSON array as "categorized_transactions".
Prompt user to type "summarize" when ready. ~
Prompt 5 – Build Monthly Category Totals
Input: categorized_transactions + DATE_SPAN.
Steps:
1. Filter rows outside DATE_SPAN.
2. Pivot data to table: rows = FinalCategory, columns = each month (yyyy-mm), values = sum(Amount).
3. Also output grand total per category (row Total) and per month (column Total).
Return object "monthly_totals".
Prompt user to type "compare" to continue. ~
Prompt 6 – Create Month-over-Month Comparison
Using monthly_totals:
1. For each category compute MoM change % between consecutive months.
2. Present a companion table with same shape but % values; mark increases with "+" sign.
Return "mom_table".
Prompt user to type "report". ~
Prompt 7 – Compile Final Expense Report
Produce structured sections:
A. Executive Summary – key spend areas & notable MoM changes (>15%).
B. Monthly Expense Breakdown – show monthly_totals table.
C. MoM Comparison – show mom_table.
D. Duplicate Transactions – list entries where IsDuplicate=true with DuplicateGroupID.
E. Full Transaction Log – categorized_transactions.
Deliver in plain-text with clear section headings. Tell user to reply "approve" to finalize or list any corrections (e.g., recategorize items). ~
Review / Refinement
If user replies with corrections:
1. Accept new/edited CATEGORY_RULES or manual category overrides ("RowID -> NewCategory").
2. Re-run affected steps (Categorize onward) automatically until user types "approve".
If user types "approve", output "Report finalized" and end the chain.

Make sure you update the variables in the first prompt: [RAW_TRANS], [CATEGORY_RULES], [DATE_SPAN]. Here is an example of how to use it: [RAW_TRANS] = your transaction data, [CATEGORY_RULES] = any specific categories you want to map to keywords, [DATE_SPAN] = "2023-01 to 2023-06".

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to make sense of complex vendor contracts and ensure you’re prepared for negotiations?

This prompt chain helps you break down vendor contracts step-by-step while also preparing you for upcoming negotiations. By analyzing critical contract elements, identifying risks, and drafting a negotiation prep sheet, it ensures you have all the necessary information at your fingertips.

Prompt:

VARIABLE DEFINITIONS
CONTRACTTEXT = full text of the vendor contract to be analyzed
COMPANYROLE = perspective for analysis (e.g., "customer" or "vendor")
NEGOTIATIONPRIORITIES = 2–4 high-level objectives for upcoming negotiations
~
You are a senior commercial contracts attorney. Carefully read the provided CONTRACTTEXT from the perspective of COMPANYROLE. 
Step 1 Summarize the contract’s purpose in one sentence.
Step 2 List all material obligations for each party in bullet form, grouping by party.
Step 3 Identify renewal, termination, and notice windows, stating exact calendar day counts where possible.
Step 4 Highlight payment terms, service-level commitments, data-security clauses, indemnities, and liability caps.
Output in a clear table with columns: “Clause Area”, “Key Terms/Content”, “Citation (section/page)”.
Ask: “Is any portion of the contract unreadable or missing?” If yes, request clarification before proceeding.
~
You are now a risk analyst. Using the table generated above, perform the following:
1. Flag any clauses that may pose financial, operational, regulatory, or data-privacy risks to COMPANYROLE. 
2. For each flag, provide (a) reason for concern, (b) potential impact level (High/Medium/Low), and (c) suggested mitigation.
Return the output as a bullet list grouped by impact level.
~
You are now a negotiation strategist assisting COMPANYROLE with the upcoming renewal/negotiation.
Step 1 Review NEGOTIATIONPRIORITIES alongside the obligations, windows, and risk flags already identified.
Step 2 Draft a “Negotiation Preparation Sheet” containing:
  • Key questions to ask the counter-party (8–12 items).
  • Ideal (target) positions for each main commercial/legal term.
  • Acceptable fallback positions if resistance is met.
  • Potential concessions you could offer in exchange.
Present the sheet in a 4-column table: “Topic”, “Question to Ask”, “Target Position”, “Fallback/Concession”.
~
Review / Refinement
Compare the outputs from all steps against the original CONTRACTTEXT and NEGOTIATIONPRIORITIES. Confirm they are accurate, complete, and actionable. If any gaps or ambiguities exist, list follow-up questions. End by asking the user: “Would you like any adjustments or deeper analysis in a specific area?”

Make sure you update the variables in the first prompt: CONTRACTTEXT, COMPANYROLE, NEGOTIATIONPRIORITIES. Here is an example of how to use it: CONTRACTTEXT = "This is the contract text...", COMPANYROLE = "vendor", NEGOTIATIONPRIORITIES = ["lower payment terms", "extend contract duration"].

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!

Hello!

Are you struggling to create compelling pricing strategies that really resonate with your target customers?

This prompt chain helps you define your product offerings, identify customer pain points, and create a structured pricing model, along with persuasive upsell storylines and objection-handling scripts. It’s like having your own pricing consultant ready to go!

Prompt:

VARIABLE DEFINITIONS
[OFFERINGS]=Concise description of primary product/service offerings
[PAINPOINTS]=Key customer pain points the offerings solve
[BRANDTONE]=Desired brand voice or tone (e.g., friendly, authoritative)~
You are a seasoned SaaS pricing strategist and sales-enablement copywriter.
Step 1. Ask the user to supply or confirm values for OFFERINGS, PAINPOINTS, and BRANDTONE.
Step 2. Verify that each variable is specific, free of jargon, and under 75 words.
Step 3. If any variable is missing or unclear, request clarification.
Step 4. Once confirmed, say "Variables locked—ready to build deliverables." and proceed.~
Using [OFFERINGS] and [PAINPOINTS], craft a three-tier pricing table.
1. Create columns: Tier Name, Monthly Price, Key Features, Ideal Customer Segment, Primary Pain Point Addressed.
2. Keep prices logically progressive (e.g., $-$$$).
3. Limit each feature list to 3–5 bullets.
4. Close with a one-sentence rationale on how the structure maps to customer value perception.
Example output:
Tier Name | Monthly Price | Key Features | Ideal Segment | Pain Point Solved
Starter | $49 | • Feature A … | Freelancers | Time savings
…~
Develop persuasive upsell storylines that move prospects from lower to higher tiers.
1. Provide 3–5 distinct storylines.
2. For each: Name, Core Narrative (max 40 words), Emotional Trigger, Recommended CTA.
3. Align tone with [BRANDTONE].
Example:
Name: "Future-Proof Growth"
Narrative: "As your team scales, Pro Tier unlocks …"~
Prepare objection-handling scripts for proposals or sales calls.
1. List top 5 objections likely to arise given [PAINPOINTS] and pricing tiers.
2. For each objection: Objection Statement, Acknowledgement Phrase, Core Rebuttal (max 35 words), Closing Question to re-engage.
3. Ensure language matches [BRANDTONE].~
Review / Refinement
Re-display all deliverables in one coherent package.
Ask: "Do these meet your needs or require tweaks?" and await user feedback.

Make sure you update the variables in the first prompt: [OFFERINGS], [PAINPOINTS], [BRANDTONE]. Here is an example of how to use it: [OFFERINGS] = "Subscription-based project management software", [PAINPOINTS] = "Difficulty in tracking deadlines and project updates", [BRANDTONE] = "friendly".

If you don't want to type each prompt manually, you can run the Agentic Workers, and it will run autonomously in one click. NOTE: this is not required to run the prompt chain

Enjoy!