Why this lesson exists. You can now write a brief that works. The problem is that a good brief takes a minute to write, and the same job comes round every week, for everyone on the team, each of whom writes it slightly differently. This lesson turns a brief you have got right once into something the whole team gets right every time.
By the end of this lesson you will be able to save a working brief as a reusable skill, because you will have built one for a task you actually do.
A small consultancy has three people who each write a weekly client update. Each has worked out a brief that produces a decent draft. Each brief is a little different: one asks for bullet points, one for prose, one forgets to mention the tone. The client receives three styles of update from one firm and quietly wonders how organised they are. Meanwhile, the newest team member has not worked out a brief at all and spends forty minutes a week on what takes the others five.
Then someone takes the best of the three briefs, adds two of last month's updates as examples, and saves it under the name "Weekly client update". Now everyone runs the same thing. The updates read as if one careful person wrote them. The new starter's forty minutes become five. And when the firm decides the updates should open with the single most important development, someone edits the saved brief once and every update changes from then on.
Every major AI tool lets you save instructions, examples and reference material as a reusable package. The names vary: Claude calls them skills and projects, ChatGPT has custom GPTs and projects, Gemini has Gems, Copilot has agents. The idea is identical. A skill is a laminated instruction card you hand to a colleague: "when I ask you for X, here is the format, here is the tone, here are examples of what good looks like."
The reason skills matter more than any single clever prompt is that the effort is paid once and the benefit repeats. A brief that took twenty minutes of back-and-forth to get right becomes a twenty-second task forever, for everyone. Improvements accumulate in one place instead of being rediscovered by each person. And consistency, which nobody thinks about until a customer notices its absence, comes for free.
Exactly the five parts from Lesson 2, plus examples:
Role and audience, written once. "You write as a member of our team, in our voice, for [type of reader]."
Task, as a description of the job rather than a single request. "Produce our weekly client update."
Context that does not change: a paragraph about the company, the product, the tone. (Lesson 6 gives this a permanent home so you can reference it rather than paste it into every skill.)
Format, precisely. Sections, length, what goes first.
Constraints, including a short list of words and phrases you never use.
Two or three real examples of output you were happy with. Examples do more work than instructions. The model will match them more faithfully than it follows any adjective.
What does not go in: anything that changes each time (this week's facts), and anything from Lesson 5's list of things that must never sit in a shared place.
