Scheduling Recurring Tasks and Measuring Results — Automations that run on a schedule. Honest ROI tracking.

Check my Jira board and create a Monday morning briefing. For each issue assigned to me or updated since last Friday: list key, summary, status, priority. Group into URGENT, IN PROGRESS, UPCOMING, COMPLETED. Save as monday-briefing-[date].md.

Check the chargeback cases file. Create a deadline alert: OVERDUE (past deadline), URGENT (0-2 days), THIS WEEK (3-7 days). Include case ID, merchant, amount, days remaining. Save as chargeback-deadlines-[date].md.

Read screening-alerts-export.csv from my workspace (this week's exported alerts). Create a compliance briefing: (1) alerts by category (sanctions, PEP, adverse media) with counts, (2) merchants approaching periodic review deadlines in the next 30 days, (3) any ESCALATE-level items from last week still unresolved, (4) a 3-line summary of this week's risk landscape. Save as compliance-weekly-[date].md.

Query Jira: issues completed this week, still in progress, blocked, and new. Show counts and lists. Format as stakeholder update for Slack/email. Save as sprint-summary-[date].md.

Read the helpdesk export CSV from the past 30 days. Identify: (1) merchants whose ticket volume increased significantly vs the previous period — early warning signs, (2) merchants whose ticket volume dropped to zero — possible churn risk or happy customer, (3) the top 3 emerging issue types that weren't in the top 10 last month — new problems brewing, (4) merchants with zero tickets for 6+ months who suddenly filed 3+ — something changed. Create a 1-page trend report as a Word document with recommended actions for each finding.

I have an export of our wiki pages (title, last updated date, author, page views). Analyse the list and identify: (1) pages not updated in over 6 months — likely stale, (2) pages with very similar titles that might be duplicates, (3) pages with zero views in the last 90 days — probably forgotten, (4) pages by authors who have left the company — may need a new owner. Create an Excel workbook: Sheet 1 — full audit with a recommended action per page (keep, update, archive, merge, delete), Sheet 2 — priority cleanup list (top 20 pages to fix first). Save as wiki-audit.xlsx.

I'm pasting my calendar for this week (or exporting it as CSV). Analyse it and tell me: (1) total hours in meetings vs total working hours — what percentage of my week is meetings? (2) back-to-back meetings with no break — flag these, (3) longest block of uninterrupted focus time available, (4) meetings that could potentially be async (status updates, FYI-only topics), (5) suggested reschedule plan to protect at least 2 hours of focused work per day. Format as a 1-page "Calendar Health Check" document.

[Paste or attach your calendar export]

Read merchant-activity-export.csv from my workspace (this week's transaction and support data per merchant). Create a merchant health report with:

(1) **Volume changes** — merchants whose transaction volume changed by more than 20% vs. the previous period (up or down). Flag direction and magnitude.
(2) **Gone quiet** — merchants with zero transactions in the last 7 days who were previously active. Possible churn risk.
(3) **Support spikes** — merchants who filed 3+ support tickets this week when their average is 0-1. Something may have broken.
(4) **New and thriving** — merchants onboarded in the last 30 days who are already transacting above average. Good news worth knowing.

Save as merchant-health-[date].md. Keep it scannable — one section per category, sorted by severity.

I'm pasting my team's standup notes and Slack highlights from this week. Create a "Weekly Wins" report with:

(1) **Shipped** — things that went live or got completed this week.
(2) **Unblocked** — issues that were stuck and are now moving again.
(3) **Key numbers** — any metrics mentioned (tickets resolved, deals closed, cases processed) — pull them into a summary table.
(4) **Shout-outs** — anyone mentioned positively by name for going above and beyond.
(5) **Next week** — carry-over items and upcoming deadlines.

Format as a clean document I can paste into Slack or email to my skip-level. Keep it under 1 page.

[Paste this week's standup notes and highlights]

I'm pasting a process document / policy / runbook that my team needs to know. Create a training quiz with:

(1) 10 multiple-choice questions that test understanding (not just recall — include scenario-based questions).
(2) For each question: the correct answer and a brief explanation of WHY it's correct.
(3) 3 "what would you do?" scenario questions where the person has to apply the knowledge to a realistic situation.
(4) An answer key at the end.

Make the questions tricky enough that someone who just skimmed the document would get some wrong. The goal is learning, not easy passes.

[Paste the document here]

Here's my context for next quarter's goal-setting:
- Last quarter's results: [what we achieved, what we missed, key metrics]
- Company/department priorities for next quarter: [themes, focus areas, strategic bets]
- My team's capacity: [team size, any hiring/departures, major projects already committed]

Draft 3-5 quarterly goals (OKRs or equivalent) that: (1) connect to the company priorities, (2) are specific and measurable (not "improve quality" — what metric, by how much?), (3) are realistic given the team's capacity, (4) include one stretch goal that's ambitious but not impossible. For each goal, suggest 2-3 key results that would prove it's been achieved.

Read the following files from my workspace: [list your weekly exports — e.g., jira-export.csv, tickets-resolved.csv, team-updates.txt].

Create a weekly status report with: (1) **Highlights** — top 3-5 things accomplished this week, (2) **Metrics** — key numbers in a summary table (tickets resolved, cases closed, deals progressed — whatever applies), (3) **Blockers** — anything stuck and what's needed to unblock, (4) **Next week** — top priorities for the coming week, (5) **Risks** — anything the reader should know about.

Format for Slack (scannable, with bold headers). Keep it under 20 lines — if someone can't read it in 60 seconds, it's too long. Save as weekly-status-[date].md.