Your system · walk in prepared
An add-on for the people side of your work: client calls, discovery calls, sales conversations. Before each one, everything you already know about the person gets gathered onto a single page: your past notes on them and the note they wrote when they booked. It also checks their public pages and anything you promised them last time. You walk in already knowing them, and the first minutes of the call go to the conversation instead of the scramble. One file per person, in your words, on your machine.
Add it to your systemIt reads the system you already built and slots in. No full system yet? It brings a small starter and runs on its own.
See the difference
The version where you are searching your inbox with one eye on the clock, and the version where the page is already open. Flip between them.
Four tabs open. The booking email is somewhere in the inbox. Was it the rebrand or the launch? You said you would send something after the last call, and you cannot remember whether you did. Their website is still loading in tab five.
The first ten minutes of the call go to rediscovering what you already knew, and they can feel it happening.
One page, ready before you say hello. Who they are, in your own words from your own notes. Why this call: what they wrote when they booked, verbatim. Where things left off, what you promised and when, one thing to remember.
At the bottom, a suggested first question that starts from where you actually are with them, instead of "so, tell me about yourself".
Anything missing is marked plainly: "not in your notes" means exactly that, so you know what to ask on the call.
The brief is built from your own files and their public pages, so what you carry in is what you actually know, marked where it thins out.
The whole loop
Six moves that live inside your own system. One file per person, and every call makes it warmer.
A new name comes up and prep-a-call asks 3 or 4 quick questions: who they are, how you met, where things stand. Your answers land verbatim in their own file.
What they wrote when they booked goes on the page in their exact words, with the date. What someone writes at booking is often the clearest ask you will ever get from them.
Claude reads their file: the thread, the promises, what they said last. If their website or a public profile is on file, it checks what those say, attributed, and flags anything that looks stale.
Who, why this call, where things left off, what they asked for, what you promised, one thing to remember, a suggested first question. Anything missing is marked "not in your notes".
The first ten minutes go to the conversation instead of the archaeology. Remembering what someone told you reads as care, and they feel it in the first minute.
Tell it how the call went while it is fresh and the page gets the update: what happened, any promises in either direction, their exact words where worth keeping. The next brief starts where this call ended.
The pack keeps people in people/firstname-lastname.md, one plain file each: who they are in your words, where things stand, what you promised, what they said last. Any other pack in your system that keeps notes on people can read and grow the same files, so the person stays whole across everything you do with them.
A fresh chat forgets the person by tomorrow. Your files hold the booking note from May, the promise you made in June, and the exact words they used about what they want, so the second call starts warmer than the first. It is a Mind practice, and it lives in a system that is yours.
The part that makes it yours
Generic call prep fits a client who exists on average. Yours have their own history with you, their own words, their own open promises. The brief works with those.
The page holds your one-paragraph version of a person and their exact words, untouched. The polished summary hides what you actually noticed, and what you noticed is the useful part.
Every brief is written as if the person might read it, because preparation is for their benefit too. Nothing lands in a file that you would be uncomfortable showing them, and that keeps the whole practice honest.
"Not in your notes" is a complete line. A marked gap tells you what to ask on the call; a smooth guess tells you a plausible wrong story. The brief always chooses the marked gap.
It cannot see your email or calendar unless you have connected those integrations in your own system, and it works without them: you paste the booking note in, which takes ten seconds. It cannot know what someone did not write down: the brief is only as good as your notes, and the 2 minutes of telling it how each call went are what make the next brief good. And it does not scrape private profiles: public pages only, so everything in a brief is something you know or something anyone could see.
A peek inside
Plain files that drop into your root system, in folders you own and can open in anything.
The promises
Built the same way as the rest of your system, because it is your relationships on the line.
The brief holds what your files and their public pages actually say. A gap stays a marked gap and anything uncertain is called uncertain, because a confident wrong line five minutes before a call costs you the call.
Their booking note, their exact words, your one-paragraph read of them: kept as written. It cleans an obvious typo and touches nothing else, because your phrasing is what you will recognize mid-call.
Briefs are for the person's benefit too. If a line would be uncomfortable for them to read, it does not get written. Preparation reads as care only when it is care.
One plain file per person, in a folder you own rather than on a platform you rent by the month. Open it, read it, take it with you.
How to use it
Install takes about 5 minutes. A brief takes 2 to 3 to generate and one to read; the note after the call takes 2.
Download and unzip into your root folder. The skill joins your existing skills and the people folder gets a home. No full system yet? It brings a small starter so it runs on its own.
Run prep-a-call for whoever you are seeing next. If they are new, paste the booking note and answer 3 or 4 quick questions. The brief comes back in full, one page, gaps marked.
Prep when a name comes up or a call is close, walk in knowing them, then tell it how the call went. Every pass through the loop makes the next brief warmer.
# one line in your root CLAUDE.md, once
- Before the call: when I say "prep my call with [name]" or
"I have a call with [name] tomorrow", read before-the-call's skill and run it.
When I tell you how a call went, add it to that person's page.
Start a page for the person you are seeing next, run prep-a-call five minutes before, and walk in already knowing them. The remembering is done before you say hello, so the call gets all of your attention.
Add it to your systemWant to build it live with us instead? Come to the next live session.