Your AI Action Plan

Create a 10-slide presentation on [TOPIC] for [AUDIENCE - e.g. "potential B2B clients"].
Slide structure: agenda, problem, solution, 3 key benefits, case study, data slide, pricing/next steps, CTA.
Tone: [professional / conversational / bold].

I need to create a presentation for [AUDIENCE] about [TOPIC].
My goal is to [GOAL - e.g. "convince the client to start a pilot project"].
Write a slide-by-slide script: title + 3 bullet points per slide.
Keep each bullet under 12 words. Total: 8-10 slides.
Start with the most important point, not context.

Step 1 - Research brief (Perplexity):
"Find current, cited evidence for [TOPIC] relevant to [AUDIENCE]. Return 5 facts, 3 risks, and 3 credible examples."

Step 2 - Narrative outline (Claude):
"Turn this research into an 8-slide persuasive deck. For each slide include: title, core message, one supporting fact, and speaker note."

Step 3 - Paste the outline into Gamma and generate the draft deck.

Step 1 - Brief to structure (Claude):
"I'm preparing a [TYPE] presentation for [AUDIENCE].
Context: [2-3 sentences about the situation].
Goal: [what decision or action you want from the audience].
Constraints: [length, tone, things to avoid].
Create a presentation outline with: goal per slide, key message, supporting data point."

Step 2 - Paste outline into Gamma.app -> generate draft.
Step 3 - Export to Canva -> apply brand colors, fonts, logo.

Turn these rough process notes into a simple SOP. Include: purpose, when to use it, required inputs, step-by-step workflow, owner, tools, quality checks, and common mistakes.

Notes:
[PASTE]

Create a reusable checklist for [PROCESS]. Include sections for intake, execution, quality check, handoff, escalation, and completion evidence. Format it so I can paste it into Notion.

Convert this process explanation into: 1. SOP, 2. quick checklist, 3. training note for a new person, 4. edge cases, 5. questions to confirm with the process owner.

Transcript or notes:
[PASTE]

Design a procedure-library template for [TEAM]. Include fields for owner, last reviewed, inputs, steps, tools, examples, risks, escalation path, related templates, and update log. Add rules for when a procedure must be reviewed.

Write a weekly [TEAM / CLIENT / PROJECT] report.
Period: [DATE RANGE]
Metrics: [PASTE METRICS]
Highlights: [WHAT WENT WELL]
Risks or blockers: [WHAT NEEDS ATTENTION]
Next actions: [3-5 BULLETS]
Audience: [MANAGER / CLIENT / TEAM]. Keep it factual, concise, and easy to scan.

Analyze this report data before drafting the summary.
Data: [PASTE TABLE OR METRICS]
Return: 1. Top 5 changes, 2. likely explanations, 3. questions to verify, 4. what should be highlighted, 5. what should not be overclaimed.

Turn this exported data into a decision memo.
Audience: [WHO WILL READ IT]
Data: [PASTE CSV OR TABLE]
Return: executive summary, key changes, likely causes, recommended action, risks, and a short appendix explaining assumptions.

Create a reusable monthly review template for [ROLE / TEAM]. It should include: required inputs, KPI table, variance analysis, stakeholder narrative, recommended actions, risks, and a quality checklist before sending.

Write a [TYPE - cold outreach / follow-up / proposal / status update] email.
From: [YOUR ROLE] at [COMPANY]
To: [RECIPIENT ROLE] at [THEIR COMPANY]
Context: [1-2 sentences of background]
Goal: [what you want them to do]
Tone: [professional / friendly / direct]
Length: [short = 3 sentences / medium = 1 short paragraph / full = structured email]

Write a weekly marketing performance report.
Period: [DATE RANGE]
Metrics to include: [list your KPIs]
Highlights: [what went well]
Issues: [what underperformed and brief reason]
Next week priorities: [3 bullet points]
Audience: [manager / team / client]
Tone: factual, no fluff. Use bullet points for metrics, short paragraphs for narrative.

Turn these rough notes into a clear [EMAIL / STATUS UPDATE / REPORT].
Audience: [WHO WILL READ IT]
Purpose: [DECISION, UPDATE, REQUEST, OR ESCALATION]
Raw notes:
[PASTE NOTES]

Return:
1. Suggested subject line
2. Short summary
3. Main message in my tone: [DIRECT / WARM / EXECUTIVE]
4. Action items with owners and dates
5. Risks or open questions

I'll share 3 examples of emails I've written. After reading them, identify:
1. My typical sentence length and structure
2. Words or phrases I use often
3. My tone (formal / casual / direct / warm)
4. Things I never say

[PASTE EMAIL 1]
[PASTE EMAIL 2]
[PASTE EMAIL 3]

Now write a [TYPE] email using my style. Here's the context: [CONTEXT]

Analyze this data for trends, outliers, and practical next steps. Return: 1. top 5 findings, 2. possible explanations, 3. questions to verify, 4. recommended next actions. Do not assume causes without evidence.

Data:
[PASTE]

In this workbook, analyze [TABLE/RANGE] and answer: What changed most, what looks unusual, which rows need attention, and what chart or pivot would best explain the result?

Use these spreadsheet findings to write a decision memo. Include: headline insight, supporting numbers, likely drivers, caveats, recommended action, and what data should be checked next.

Findings:
[PASTE]

Create a recurring analysis checklist for [DATA TYPE]. Include: required inputs, cleaning checks, metrics to calculate, outlier rules, interpretation questions, caveats, and the final memo format.

Create a lesson plan for [GRADE/SUBJECT].
Standard or objective: [PASTE]
Student context: [PASTE]
Return: learning objective, hook, direct instruction, guided practice, independent practice, checks for understanding, differentiation options, and exit ticket.

Create a standards-aligned lesson plan for [TOPIC]. Include objective, vocabulary, activity sequence, materials, formative checks, extension, support, and homework. Mark where teacher judgment is required.

Create a complete lesson packet for [TOPIC]. Return: lesson plan, teacher notes, student handout, slide outline, vocabulary support, exit ticket, answer key, and misconceptions to watch for.

Design a reusable unit planning system for [SUBJECT/GRADE]. Include: standards map, unit essential question, lesson sequence, formative checks, differentiation plan, materials list, assessment plan, and teacher reflection fields.

Differentiate this text for [GRADE/SUBJECT].
Text: [PASTE]
Return: original-level summary, easier version, extension version, vocabulary support, comprehension questions, and teacher notes about what changed.

Create differentiated supports for [LESSON TOPIC]. Student needs: [GENERAL NEEDS, NO NAMES]. Return: hooks, scaffolded questions, challenge prompts, group options, and checks for understanding.

Create differentiated materials for this objective.
Objective: [PASTE]
Return: core task, scaffolded version, extension version, vocabulary support, teacher grouping notes, and risks if students are over- or under-supported.

Create a differentiation pattern library for [SUBJECT/GRADE]. Include: reading supports, language supports, challenge tasks, misconceptions, formative checks, grouping patterns, and privacy-safe student need descriptors.

Create a rubric for this assignment.
Assignment: [PASTE]
Learning objective: [PASTE]
Return: criteria, 4 performance levels, student-friendly language, common errors, and teacher review notes.

Create an exit ticket for [LESSON OBJECTIVE]. Include 3 questions, answer key, likely misconceptions, and how I should group responses for the next lesson.

Create an assessment packet for [OBJECTIVE]. Return: rubric, student checklist, practice set, answer key, common misconceptions, and teacher calibration notes.

Create an assessment design checklist for [SUBJECT/GRADE]. Include: objective alignment, question type, reading load, accessibility supports, answer key, misconception mapping, grading notes, and student feedback plan.

Draft student feedback from these teacher notes.
Rubric evidence: [PASTE, NO STUDENT NAMES]
Tone: supportive and specific.
Return: strength, next step, one concrete suggestion, and a version for family communication. Do not assign a grade.

Create a feedback sentence bank for [ASSIGNMENT TYPE]. Include: strengths, next steps, revision prompts, encouragement, and family-friendly explanations. Keep language specific and nonjudgmental.

Create feedback and a revision task.
Rubric evidence: [PASTE]
Objective: [PASTE]
Return: feedback paragraph, revision instruction, mini-example, and teacher note about what to check next.

Create AI feedback guardrails for teachers. Include: no student names, allowed evidence, prohibited data, final teacher review, tone rules, grade-decision boundaries, and family communication rules.

Draft a parent/guardian progress update.
Teacher notes: [PASTE, NO NAMES]
Return: progress summary, specific evidence, next step, how family can help, and a sensitive-language check. Do not diagnose or label the student.

Draft a family update in [LANGUAGE].
Context: [PASTE]
Return: plain-language message, English back-translation, terms to verify, and questions for school translation support.

Create a family communication packet.
Evidence: [PASTE, NO NAMES]
Return: family update, conference agenda, student strengths, support plan, questions for family, and privacy review checklist.

Create a family communication template library. Include: positive update, progress concern, missing work, conference invitation, follow-up note, multilingual review steps, privacy rules, and tone checklist.