Level 3 opens once Level 2 is complete — every step of it. Level 2 is where you find out how your tool handles your task, which is what this level builds on.
Stop re-improvising the same task.
Take one thing you do over and over and turn it into a saved prompt template you have written, tested, improved and checked. You finish with an asset, not a memory — and the level spells out what makes one genuinely reusable.
- 3
- Phases
- 7
- Steps
- ~70 min
- Typical time
- 100%
- Free
You solved it in March. In June you solved it again.
The task comes round, you open the tool, and you think the whole thing through from scratch — the context it needs, the constraints, the shape you want back. It works. Then next month you do all of it again, slightly worse, because you cannot remember what you asked for last time.
That is the difference between using AI and having an AI workflow. One is a series of good afternoons; the other is something that is still there when you are busy, and that a colleague could run without asking you.
Level 3 is where the second one gets built, once, for a task you choose.
After Level 3 you can
- Spot which of your recurring tasks is actually worth templating, and which is not
- Write a prompt template where everything constant is baked in and everything variable is a named fill-in
- Test a template against a real instance and read the result as a test, not a verdict
- Trace every improvement back to something the test actually exposed
- Define quality criteria specific enough to check, and hold your own work to them
- Hand the finished template to a colleague without explaining it first
What you'll do
- 1
Choose the task and the tool
Steps 1 and 2. A reusable workflow is only worth building for something that actually recurs — so the first decision is what, and the second is where.
- 2
Build and test
Steps 3 and 4. Write the instructions and the template, then run it on a real instance of the task and find out what it actually does.
- 3
Refine, confirm, save
Steps 5 to 7. Record what the test changed, produce the refined template, and confirm it against at least four quality criteria before you call it done. Sharing it is optional.
This level is for you if
- You have finished Level 2
- There is a task you do at least monthly that you rebuild from scratch every time
- You want something reusable out of the time you spend prompting
- You want a coach to tell you whether what you built is actually good
What makes this level different
Checked against criteria, not taste
Both deliverables — the first draft and the refined version — are checked against the quality criteria the level hands you, item by item. You find out whether the template is genuinely reusable, not just finished.
Two deliverables, on purpose
You write a template, then test it, then produce a refined one. Handing in only the polished version would skip the loop that makes it work — so both are submitted, and the difference between them is the point.
You leave with an asset
Not notes about a workflow. The actual template, saved, tested against a real instance of the task and ready to run next time it comes round.
Questions before you start
Why do I have to finish Level 2 first?
Level 3 builds a template for a task you have already run through the tool and documented — which is exactly what Level 2 produces. Without that evidence you are designing a template around a guess about how the tool behaves.
Do I need to be technical to write a prompt template?
No. The template is written in plain markdown — headings, a few labelled fields and a fill-in or two. There is no programming in this level, and a starting scaffold is supplied for both deliverables.
Which AI tool do I need?
One that you are actually allowed to use at work. Any general assistant works — ChatGPT, Claude, Gemini or Microsoft 365 Copilot. If your employer has an approved list, that list wins over anything we suggest, and the level walks you through checking your plan and your permissions before you start.
Does anything wait on someone else?
No. Every step completes as you finish it, the two template deliverables included — nothing sits in a queue. What you hand in stays on the step, so you can open the first draft next to the refined version and see what changed.
What if I do not have a task worth templating?
The first step is working out whether you do. Good candidates repeat at least monthly, take long enough that you notice, and produce something with a recognisable shape. If nothing qualifies, a pathway is a better use of your time than this level.