Outcome
By the end of this article, you'll have something you can open next Monday morning: a personal playbook of your best AI prompts, organized by task, ready to reuse without reinventing them from scratch.
If you've worked through automating your inbox, your meetings, your documents, or your research, you already have a handful of prompts that worked well. The problem is, most people never see them again. They're buried in a chat history from three weeks ago, half-remembered, waiting to be reinvented under deadline pressure. A playbook fixes that. It's the difference between "I got AI to do this once" and "I have a system that does this every time."
Concept
A playbook is just three things:
- An audit of which recurring tasks actually eat your time.
- A template for each task worth delegating — a prompt built to be reused, not just a prompt that happened to work.
- A place to keep them so you can find the right one in ten seconds, not ten minutes.
None of this requires new tools. You've already done the hard part across earlier lessons — writing prompts for your inbox, your meeting notes, your documents, your research. This lesson is about noticing the pattern in what you've already built and turning it into something durable.
The one-off vs. the template. A one-off prompt describes a specific situation: "Summarize this email thread about the Q3 budget and draft a reply agreeing to the deadline." It worked, but only for that thread. A template describes the shape of a situation, with the specifics swapped out for placeholders: "Summarize this email thread and draft a reply that [does X]. Keep the reply under 100 words and match my usual tone." Same underlying task, but now it works on Monday's thread, next month's thread, and every thread after that.
The tell-tale sign a prompt is ready to become a template: you've used a version of it more than twice without really changing what you're asking for — just the input.
Not everything belongs in the playbook. This is worth repeating from Foundations: delegation is a judgment call, not a default. If a task requires your specific relationship context, a sensitive human read, or a decision only you're accountable for, it stays off the list — even if AI could technically draft something. A playbook full of tasks that shouldn't be there is worse than no playbook, because you'll start trusting it blindly. Good candidates are repetitive, low-stakes-per-instance, and pattern-based: recurring summaries, routine replies, first-draft documents, research digests. Bad candidates are one-of-a-kind, high-stakes, or emotionally loaded.
Build
Here's the exercise, start to finish. Set aside 20 minutes — this is a one-time setup, not a new weekly chore.
Step 1: Audit your week. List the tasks that ate your time in the last five working days. Don't filter yet — just capture. For each one, note roughly how long it took and how often it recurs (daily, weekly, occasionally, rarely).
Step 2: Score each task. For every task, ask two questions:
- Does this recur? (One-offs usually aren't worth templating.)
- Does it follow a pattern I could describe once and reuse? (If every instance is genuinely unique, skip it.)
Anything that scores yes on both is a playbook candidate.
Step 3: Turn each candidate into a template. Take your best one-off prompt for that task and rewrite it with placeholders instead of specifics. Here's a real example, going from one-off to template:
One-off (what you might have typed the first time): "Read this thread with our vendor about the shipping delay and draft a reply that pushes back politely but firmly on the new timeline."
Template (reusable version):
You are helping me reply to an email thread.
Context: [paste the thread or a summary of it]
Write a reply that:
- Acknowledges the other person's point in one sentence
- Makes my position clear: [state your position, e.g. "pushing back on the timeline" or "confirming agreement"]
- Stays under 120 words
- Matches a professional but friendly tone
- Ends with one clear next step or question
Do not add extra pleasantries or hedge the main point.
Notice what changed: the specifics (vendor, shipping delay) became placeholders you fill in each time, but the structure — the shape of a good reply — stays fixed. That structure is the actual value. You spent real effort getting a prompt to produce a reply in your voice, at your preferred length, with your preferred level of directness. A template lets you keep that effort instead of re-deriving it every time.
Step 4: Save it somewhere findable. The playbook itself doesn't need to be fancy. Pick one:
- A single doc or note, organized with a heading per task ("Vendor emails," "Meeting recaps," "Weekly research digest").
- A folder of saved prompts in whatever note-taking app you already use.
- The site's prompt library, if you'd rather start from templates already built for common roles and swap in your own details.
The only requirement is that you can find the right prompt in under a minute. If your system takes longer than that to search, you'll default back to writing from scratch — and the playbook quietly dies.
Step 5: Note what's excluded, on purpose. Add a short line under your playbook: "Not delegating: [task], because [reason]." This isn't busywork — it's what keeps the playbook trustworthy. Six months from now, when you're deciding whether to add something new, this note reminds you what your own bar was.
Run
Your playbook only earns its keep if you actually open it. A simple habit: the next time you catch yourself about to write a prompt from scratch for something you've done before, check the playbook first. If it's there, reuse it. If it's close but not quite right, update the template — that's how it improves over time instead of going stale.
Revisit the whole list monthly, not daily. Tasks that were worth automating in January might change by June; new candidates will show up as your role shifts. A playbook is a living document, not a one-time project — but it should take minutes to maintain, not hours.
You now have the full loop: notice a recurring task, write a prompt, turn it into a reusable template, save it somewhere findable, and know when to leave a task off the list entirely. That loop is the actual skill. The tools will change; the habit won't.
If you haven't worked through the earlier lessons yet, or you want the full walkthroughs behind inbox, meetings, documents, and research automation, start from the beginning.