Chapter 02 : The art of the brief
When an answer disappoints, nine times out of ten the request was vague. Jay only knows two things: what you tell it, and what it finds in the folder you've opened for it. A good brief takes one page to learn, and it saves you three rounds of back-and-forth on every task.
Think of a brilliant new colleague who arrives on a Monday morning. "Do the reporting" will get you something generic. "This month's reporting for the committee, in the format of September's, which is in the folder, with the anomalies up top" lets them be useful from the first hour. Jay is that colleague, with one advantage: it has already opened the folder.
The 5-point brief
| Element | The question to ask yourself | Example |
|---|---|---|
| 1 · Goal | What will the result be used for, and by whom? | "An email so my partner approves the quote without calling me back." |
| 2 · Context | What can't Jay guess, even by reading the folder? | "The client has already turned it down twice over price." |
| 3 · Deliverable | What form, what length, and where should it land? | "A document in the Atelier, two pages, then a PDF in the Quotes folder." |
| 4 · Criteria | How will you recognize a good result? | "Every figure points to a row in the spreadsheet." |
| 5 · Example | Do you have a past result you liked? | "Use the template from report-september.docx." |
The third point is specific to Jay. On your computer, a result has an address: a file in a folder, a piece in the Atelier, a draft in your email. Say it, or Jay chooses for you.
Before / after
Sort my invoices.
In the Downloads folder, find the PDF invoices received since October 1. Move each one to Accounting/2026/[month] and rename it "YYYY-MM-DD supplier amount". Don't delete anything. At the end, give me the list of what you moved and of anything that seemed doubtful.
The second request takes thirty more seconds to write. It saves you from checking forty files one by one.
Ten techniques that change the answers
Ranked from simplest to most advanced. The first three are enough for most requests.
- Give an audience and a stake. "For a busy buyer who has to decide tomorrow" sets the tone and level of detail far better than a role like "you are an expert".
- Get yourself interviewed. End with "Ask me the questions you need first". Jay often spots what's missing better than you do.
- Specify the deliverable. A table, a 120-word email, a two-page document in the Atelier, a spreadsheet with specific columns. With a precise format, the result is usable as is.
- Point to an example in the folder. "Do it like report-september.docx" beats a paragraph of instructions. Jay picks up the tone, the structure and the formatting.
- Separate the ingredients. Wrap each block in angle-bracket tags: <context>, <document>, <instructions>. Jay no longer confuses your instructions with the text to process.
- Have it read before it writes. "Before answering, read the last three meeting notes in the folder." On your computer, the information is often already there: ask Jay to go get it.
- Ask for a plan before action. For anything that touches files, turn on Plan mode (the "+", or /plan) or write "Show me your plan and wait for my approval". A misunderstanding at the start repeats across every file.
- Move up to Thinking mode to decide. Analyses, calculations and hard choices benefit from Thinking or Expert mode; everyday work stays in Adaptive (chapter 1).
- Edit your first message. If the result misses the mark, edit the original request instead of piling up corrections. The session stays clean.
- Ask for a self-critique. "Reread your work like a demanding expert: what's weak, wrong or missing? Then fix it." Quality goes up a notch, right away.
The skeleton of a complete brief
<context> I'm [your role]. This work is for [audience], who needs to [decision or action]. [What Jay needs to know: constraints, history, stakes] </context> <task> [What you want to get, in one sentence] </task> <deliverable> [Form, length, tone, language, and where the result should land] </deliverable> <criteria> A good result: [what makes it excellent] </criteria> If you're missing a piece of information, look for it in the folder first. If you can't find it, ask me your questions before you start.
The meta-prompt: have Jay write the brief
For a task you'll do often, there's no need to hunt for the perfect brief on your own. Ask Jay to build it with you, then store it in the project's JAY.md or in a Skill (chapters 4 and 11).
I want a reusable brief for this task: [describe the task]. First, ask me the questions you need to understand it well: goal, audience, deliverable and location, quality criteria, examples in the folder. Then write the complete brief with tags, and tell me which parts to adapt each time I use it.
Library: 14 ready-to-use prompts
Copy, replace the brackets, send. Keep your favorites in a "Prompts" project or in a Skill.
Write
Help me write an email to [recipient] to [goal: decline, follow up, deliver bad news]. Context: [situation]. My relationship with this person: [relationship]. Look up our latest exchanges in my email before writing. Suggest 2 versions, one direct and one more diplomatic, 120 words max each. No empty phrases. Prepare them as drafts, don't send anything.
Rewrite this text for [new audience], who knows [level] about the subject. Keep the ideas, change the vocabulary, the examples and the length ([length]). <text>[paste the text, or give the file path]</text>
Here's a rough idea: [your idea, even jumbled]. Turn it into a LinkedIn post for [audience]. Give me 3 different hooks, then the full post with the best one. 150 to 200 words, short sentences, a single idea, a closing question. I'll post it myself.
Summarize
Find yesterday's meeting, "[title]", in my meetings and read its transcript. Write: 1) the decisions made, 2) the action items with owner and deadline, 3) the open questions, 4) a follow-up email ready to send. Flag anything ambiguous instead of guessing. Save the notes in [folder] and prepare the email as a draft.
Summarize [file path] for someone who has to decide [decision] and only has 2 minutes. Format: the essentials in 3 sentences, then 5 key points with the page where each appears, then the 3 questions I should ask the author.
Decide
I have to choose between [option A], [option B] and [option C] for [goal]. My criteria, in order of importance: [criteria]. Build a comparison table scored out of 5, explain each score in one line, then give your recommendation and what could change it.
It's 6 months from now and [project] has failed. Describe the 7 most likely reasons for this failure, from most to least likely. For each one: the warning sign to watch for starting now, and one action to prevent it.
Here's my position: [your position and your arguments]. Play the smartest devil's advocate possible. Give the 5 best objections, then tell me which ones are truly dangerous for my reasoning.
Prepare and organize
I'm meeting [person, company] tomorrow about [goal]. Look up our past exchanges in my email and the related documents in [folder]. Prepare for me: 3 goals for this meeting, 8 questions to ask, the 3 likely objections with an answer for each, and the opening line.
Here's my task list for the week, in no particular order: [list]. My constraints: [meetings, deadlines, energy]. Sort them into: do it myself, delegate, hand to Jay, drop. Then suggest a realistic day-by-day schedule.
Analyze
Open [file path]. Start by describing what it contains and the quality issues you see: blanks, duplicates, inconsistencies. Then answer this question: [your question]. Do all the calculations with code, and show me the result in a table and a chart.
Here's a problem: [description, figures, timeline]. Ask me questions one at a time to get to the root cause, like a consultant using the 5 whys method. When you have enough to go on, give the 3 most likely causes and how to check each one.
Here's [my text, my presentation, my offer]. Give me candid feedback, like a demanding expert who wants me to succeed. Format: what works (3 points), what doesn't (3 points, from most to least serious), and the single change that would have the most impact.
On the computer
Go through the folder [path] without changing anything. Tell me what it contains: the file types, likely duplicates, what hasn't been touched in a year, and what looks misfiled. Then suggest a tidy-up plan in 5 steps max, and wait for my approval before moving anything.