Get to a defensible view on an unfamiliar market
Asking for the disagreements is what stops a briefing reading as more certain than the evidence is.
1 field to fillResourcesPrompt library
Eighteen prompts that work, with a line under each explaining which part of the wording is doing the work. Copy one, replace the angle-bracketed parts, and run it against your own systems. When one of these becomes something you run weekly, turn it into a skill.
The library
The note under each prompt is the point. Most of these work because of one constraint in the wording, and copying the prompt without it gets you a different answer.
Asking for the disagreements is what stops a briefing reading as more certain than the evidence is.
1 field to fillSplitting internal from external keeps the reader clear on which half is yours.
1 field to fillGrouping by conclusion turns a reading list into an argument.
1 field to fillNaming the threshold in the prompt is what keeps the answer to one page.
3 fields to fillAsking for row counts at each step is the cheapest way to catch a bad join.
3 fields to fill‘Only what is genuinely outstanding’ is doing the work here. Without it you get the whole checklist back.
nothing to fill inThe distinction between a breach and a variation has to be yours; state it or you get everything back.
1 field to fillThe inference flag is the difference between a chronology and an assertion.
2 fields to fillThe last line is the one people forget, and it is the one the partner asks about.
2 fields to fillHolding back the drafting keeps the first pass an assessment rather than a rewrite.
2 fields to fill‘Not from prior working papers’ stops last quarter’s conclusion being recycled as this quarter’s evidence.
2 fields to fillClock skew across systems is the thing that quietly breaks a timeline.
3 fields to fillThe known/inferred split is what makes the write-up usable in a review rather than defensive.
1 field to fillQuery history is where the undocumented dependencies live.
1 field to fillThe last line has paid for itself more than once.
1 field to fillAsking for questions rather than facts is what makes the brief usable in the room.
1 field to fillOne signal per account keeps the output actionable instead of a dashboard.
1 field to fill‘Do not invent one’ is the whole prompt. The rest is scaffolding.
1 field to fillNothing matching that yet? Tell us the question you are actually trying to answer and we will write the prompt with you.
Writing your own
Say which systems to read and in what order. ‘Our records first, then the web’ produces a different answer from the same question asked without it.
What counts as a breach, a variance, a risk. The judgement is yours; the work of applying it consistently is what you are handing over.
Where the sources disagree, what was inferred rather than stated, what would change the conclusion. An answer that names its own limits is one you can act on.
‘Do not invent one’, ‘do not suggest wording yet’, ‘escalate breaches, not variations’. The prohibition is usually the line carrying the whole prompt.
Once a prompt has been rewritten the same way three times, it has stopped being a prompt. Save it as a skill so the fortieth person to run it gets the same wording as the first.
Bring the question you actually need answered and we will run it against your own systems on the call.