The APEXPrompt Library.

Act as an operations analyst for a [ROLE] at a [TYPE OF BUSINESS].
Below is my calendar and task list for a typical week.

[PASTE CALENDAR AND TASKS]

1. Group the work into 8 to 12 recurring tasks.
2. For each task, estimate hours per week and how repeatable it is (high, medium, low).
3. Sort each task into a bucket: A (AI drafts), B (AI assists, I decide), C (owner only).
4. Return a table, then name the three tasks where AI would free the most time.

Ask me questions first if anything is unclear.

I run [BUSINESS] and I am responsible for [AREA].
List the decisions I likely make every week, month and quarter. For each one, show:
- what information I need to make it well
- where that information lives today
- how AI could prepare it for me
- the bucket: A, B or C

Then ask me five questions to correct your list before you finalize it.

Interview me to write my GOAL for an AI coaching engagement.
Ask one question at a time and wait for my answer. Cover:
- what I want to be able to do with AI in three months
- which part of my work it should change first
- how I will know it worked

After no more than eight questions, draft my GOAL in two or three sentences, in my words, with one result we can observe at the end.

Here are the AI tools and subscriptions my business pays for:
[LIST TOOLS AND PLANS]

For each one, tell me:
- what it is best at
- which of my tasks it fits: [PASTE TASK LIST FROM PROMPT 01]
- what data it should not see under our current setup

Then point out overlap, gaps and any tool we may not need. Flag anything you are unsure of instead of guessing.

You are a prompt engineer working for a business owner. I will give you a rough request.

Rough request: [WHAT I WANT]

Ask me up to five questions about audience, purpose, format and limits. Then write a reusable prompt that:
- states the role and the task
- lists the context the AI needs
- marks every variable in [BRACKETS]
- describes what good output looks like

Return only the finished prompt.

Read the material below and brief me as my chief of staff.

[PASTE DOCUMENT]

Give me:
1. The decision or action being asked of me, in one sentence
2. The three facts that matter most, each with where it appears
3. Risks and open questions
4. What happens if I do nothing

Keep it under 200 words. Quote the source for any number.

Here are three messages I wrote that sound like me:
[PASTE 3 SAMPLES]

Describe my writing style in five bullet points. Then draft a [TYPE OF MESSAGE] to [RECIPIENT] about [TOPIC].
The main point is: [MAIN POINT]

Match my length and tone. Do not add claims or promises I did not give you.

I am about to decide: [DECISION]
My reasoning: [WHY]

Act as a skeptical board member.
1. Make the strongest case against it.
2. Run a pre-mortem: it is a year from now and this failed. List the three most likely reasons.
3. Name what I would need to see to be confident.

Do not soften the critique. Do not make the decision for me.

Here are the notes from a meeting on [DATE] with [ATTENDEES]:
[PASTE NOTES OR TRANSCRIPT]

Return:
- decisions made
- action items as a table: task, owner, due date
- open questions, with who should answer each one

Only list what is in the notes. Mark anything you inferred with (inferred).

Below is how [PERSON] does [PROCESS], in their words:
[PASTE DESCRIPTION OR TRANSCRIPT]

Write a step-by-step checklist a new team member could follow. For each step, add the tool used, a common mistake and how to tell it was done right.
Flag any step that needs a judgment call so a person signs it off.

Build a single-file HTML page that works offline in a browser. No external libraries, no network calls, and no data leaves the page.

It should: [WHAT IT DOES]
Inputs: [FIELDS]
Output: [RESULT]

Keep the design clean and printable. Explain in three sentences how to open and use it.

You are working on behalf of [BUSINESS] as a [ROLE].
Goal: [OUTCOME]
You may use: [TOOLS OR CONNECTORS]

Plan first, and show me the plan before you act.
Stop and ask me before you:
- send anything to a client or vendor
- spend money or change a subscription
- touch [SENSITIVE DATA]

When finished, report what you did, what you did not do and anything I should check.

I want my team of [NUMBER AND ROLES] to start using AI for [TASK].

Design a 30-minute session: a short why, a live example using our own work, one exercise per person and a five-question check for understanding.
Include the rules they must follow about data and review. Write it so I can teach it myself.

Here is how I handled [TASK] before: [TIME, STEPS, QUALITY]
Here is how I handle it now with AI: [TIME, STEPS, QUALITY]

Compare the two in a table: time, steps, quality and risk.
Then tell me what is still manual that could move to Bucket A or B, and what should stay with me.
Use only the numbers I gave you.

Help me write a progress note in three parts:
1. Where I started: [BASELINE NOTES]
2. Where I said I wanted to be: [MY GOAL]
3. Where I am now: [WHAT CHANGED]

Ask me for examples wherever my answers are vague. Keep it factual and under 250 words. Do not add results I did not describe.

Based on this progress note:
[PASTE NOTE]

Draft a 90-day plan with three priorities. For each one: the outcome, the first step this week, who owns it and how I will know it is working.
Keep the whole plan on one page. End with three questions that test what I may have missed.

Here is how my team uses AI today: [TOOLS, TASKS, PEOPLE]
Review it against these rules: [OUR AI RULES, OR "NONE YET"]

List what is working, where data may be at risk and where decisions may be going to AI that should stay with people.
Suggest no more than five changes, in order of importance.

Act as a careful checker, not a cheerleader. Review the draft below line by line. Do not rewrite it.

[PASTE DRAFT]

List:
- every factual claim, number and name, and whether the source supports it
- anything that sounds certain but may be wrong
- anything missing that the reader will expect
- any sentence that promises more than we can deliver

End with one verdict: safe to send, send after fixes, or do not send.