Building Reusable Workflows: Your Own Prompt Playbook
Templates with variables, chained multi-step workflows, a worked weekly-report example and how to organize and measure it.
If you do a task again and again, save a good prompt for it. Replace the parts that change with blanks, like {{name}}. For bigger jobs, use a few small prompts one after another and add a final check step. Keep them in one place so you can find them.
- Template
- A saved prompt with blanks you fill in each time.
- Variable
- A blank in a template, like {{client_name}}.
- Chain
- Several small prompts used in order, each using the last answer.
One great prompt saves you time once. A library of tested prompts, linked into workflows, saves you time every week for as long as you do that work. This lesson turns the skills from the last three lessons into your own playbook. It is a small, organized set of reusable prompts and multi-step routines for the work you really repeat.
What deserves a place in your playbook
- You will do it again, at least monthly and ideally weekly.
- It took real effort to get right the first time.
- You can recognize a good result, and a bad one is easy to spot.
- The task has the same shape each time, with changing details. Examples are a weekly report, a customer reply and a meeting follow-up.
Turn a good prompt into a template
Replace everything that changes between uses with a named blank in double braces. Keep everything that stays the same. Add one line saying when to use it. This is the same {{variable}} pattern used in this site's prompt library.
NAME: Meeting follow-up email USE WHEN: after any client or team meeting
VERSION: 3 (added "decisions first" rule)
You are writing on behalf of {{my_name}}, {{my_role}}.
Audience: {{attendees}}. Tone: {{tone}}.
From these raw notes, write a follow-up email:
<notes>
{{raw_notes}}
</notes>
Rules:
- Start with the decisions made, as a short list.
- Then action items as: owner - task - due date. If an owner or date is missing write "TBC", never guess.
- End with one sentence about the next meeting: {{next_meeting}}.
- Under 150 words. No filler such as "I hope this email finds you well".From prompts to workflows: chaining
Many jobs are really several small jobs in a row. Do not write one giant prompt. Give each step its own focused prompt, and pass the result of one step into the next. Small steps are easier to check and easier to fix. You can also rerun only the step that went wrong. A common chain is: pull out the facts, change them into the shape you need, write the draft, then check it.
WORKFLOW: Weekly status report (about 10 minutes instead of 60)
STEP 1 - EXTRACT Paste your raw notes, tickets and numbers.
Prompt: "List every concrete fact, number, decision and blocker in this material as bullet points.
Do not interpret. Mark anything unclear with (?)."
STEP 2 - ORGANIZE Paste the Step 1 list.
Prompt: "Group these into: Progress, Metrics, Risks, Decisions needed. Remove duplicates.
For each risk suggest a mitigation, labelled as a suggestion."
STEP 3 - DRAFT Paste the Step 2 output plus last week's report as a style example.
Prompt: "Write this week's report for {{audience}} in the same structure and tone as the example.
Max 250 words. Lead with the single most important thing."
STEP 4 - CHECK Paste the draft and the Step 1 list.
Prompt: "Compare the draft to the fact list. List any claim in the draft not supported by the
facts, and any important fact that's missing."
You still do: read the final version, fix anything the check found, send it.Organize it so you can find things
- Keep the playbook in one place: a notes app, a document or a project in your assistant. Search works better than folders.
- Name entries by the job, not by something clever. Client follow-up email is better than Prompt 17.
- For each entry, write when to use it, the variables, the version and one example of a good result.
- Keep versions. When you improve a prompt, add one line about what changed and why.
- Retire what you no longer use. A short list you trust beats a long list you do not.
Measure what it saves
For your first five entries, time yourself once the old way and once with the template, including the checking. Write the numbers in the entry. This keeps you honest about which templates earn their place. It also gives you real figures if you ever show your boss or a client what AI changed.
Where this leads
Some workflows become stable, and you run them all the time. You can then move them from I paste things into each step to automation. Automation tools run the chain for you on a schedule, or when an email arrives. The AI Automation Builder path covers that. Share your best templates with colleagues too. A team playbook grows faster than a personal one.
- ✓Save prompts that you will reuse and that took effort. Turn the changing details into {{variables}}.
- ✓Chain small, focused steps, such as pull out facts, organize, draft and check, instead of one giant prompt.
- ✓For each entry, record the use, the version and an example. Name it by the job.
- ✓Time your templates to prove they pay off. Automate stable workflows later.
Build your first three-entry playbook
- List three tasks you repeated in the last month.
- Turn each into a template with variables, a when-to-use line and a version number.
- Take the one with the most steps and turn it into a chain of three or four steps, ending with a check step.
- Time each task once by hand and once with the template. Write the numbers next to each entry.
Q1Why chain several small prompts instead of using one big one?show answer
Each step is easier to check, fix and rerun. Focused prompts also give more dependable results than one overloaded instruction.
Q2What is the point of a final check step in a workflow?show answer
It compares the draft with the source facts. This catches claims with no support and missing points before you send it.
Q3What should you record with each playbook entry?show answer
When to use it, its variables, the version and what changed, and an example of a good result.