You will build a library of at least eight tested templates covering the work you do most often.
Picture the start of a busy week. A client wants a proposal by Thursday, your manager wants a summary of a forty-page report, and there are a dozen emails that each need a careful reply. Without a library, every one of those starts with a blank chat box. With one, each starts with a tested template you trust, and the time goes into the parts only you can do.
This project builds that library. It draws on the whole course, and it is the first deliverable of the final project. Allow about an hour, though you can spread it over a few sittings.
Build a library of at least eight templates covering the work you do most often. Each template has blanks for the parts that change, a when-to-use line, a checking level and notes from two test runs. The library lives in the place you chose in lesson 9.2, Store and organise it where you work, organised by job.
The eight should cover a mix. At least two are writing tasks, such as client emails, announcements or reports. At least one is a document task, such as summarising a long file with page references or extracting information into a table. At least one is a planning task, such as an outline-first plan or a questions-first brief. At least one is a checking or critique task, such as the fresh-chat critique from lesson 7.2, Ask for a critique, and know its limits. The rest are whatever you do most.
You already have more than you think. Go back through the work you produced in this course: the rewritten prompts from lesson 1.4, the example set from lesson 2.4, the step log from lesson 3.5, the feedback rounds from lesson 4.4, the summary prompts from lesson 5.4, the project instructions from lesson 6.4 and the two templates from lesson 9.1. Add prompts from your chat history that gave you good results.
List them, then pick the ones that match tasks you do at least every month. Fill the gaps in the mix with new prompts written for the purpose.
Step 2 is the conversion. For each one, follow lesson 9.1, Turn a prompt that worked into a template. Keep the context, examples, constraints, format and things to avoid. Turn names, figures, dates and specifics into labelled blanks in square brackets. Add the when-to-use line. Paste a good sample output underneath, with confidential details removed.
Daniel, the furniture shop's customer service lead from module 2, built his library in this order: delivery query reply and damaged item reply as his two writing tasks, a supplier invoice extractor as his document task, a questions-first prompt for planning promotions as his planning task, and a fresh-chat critique of customer-facing announcements as his checking task. His other three were a product description, a weekly sales summary for his manager and a refund-decision checklist that reads the returns policy he uploads.
A template is not tested until it has worked on inputs it was not built from. For each one, run it twice on new, real inputs, each in a fresh chat. Read each output and note how much editing it needed.
If either run needed heavy editing, fix the template using the approach in lesson 9.1: look at what you kept changing, tighten that instruction or swap the sample, and test again. If two rounds of fixing do not help, drop it and pick another task.
Write brief notes on each run: the input, how the output did, and what you changed. Daniel's damaged item reply passed first time on both runs. His product description template produced the same opening sentence for a sofa and a bookshelf, so he replaced the sample output with a shorter, plainer one, and the next two runs varied properly.
Give every template a checking level from lesson 7.1, Match the check to what is at stake, and write it at the top, beside the when-to-use line. Writing it down now matters because the day you most need the template is the day you are most tempted to skip the check. Daniel's refund checklist is marked primary source, because it touches money and the customer's rights, so he always checks its conclusion against the actual policy wording.
Step 5 deals with the fact that a library goes stale. Products change, your work changes, and a template that worked in March may drift by August when your assistant moves to a new model. Set a monthly reminder in your calendar. At each review, retire templates you have not used in the past month or two, update any that mention old prices, policies or names, and retest any you rely on heavily after your assistant announces a major update.
A finished library has at least eight templates in one place, grouped by job. Each has a when-to-use line, a checking level, labelled blanks, a sample output and notes from two test runs. Your calendar has a monthly review booked.
When it is done, try using it for one full working day and notice how often you reach for it. That count is the best measure of whether you built it for the work you really do. To begin, open the place your library will live and list every candidate prompt from your course work.
Complete a library of at least eight templates, each with blanks, a when-to-use line, a checking level and notes from two test runs.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).