Write your own command
Turn work you repeat into a brief you can run by name, kept to yourself or shared with the team.
A command of your own is a written brief: what the work is for, what should come back, and how you want it done. Write it once and run it by name in any deal, the same way you run the commands that ship with the product.
Open the user menu and choose Commands. The list opens in a new tab and holds everything you've written, marked Private or Shared, with a search box and filters for All, Private, Shared and Unsaved. New command starts a fresh brief.
Write the brief
Give the command a title, then answer "What should this command accomplish?" underneath it. Both are required, and both are what you and your teammates read in the list, so name the work rather than the tool: "Screening memo from the OM" beats "memo builder".
Two settings sit under the title. Execution decides how the work gets done: Directly keeps it with the terminal you're talking to, May delegate hands parts off when that improves the result, and Agent team coordinates delegated work into a single result. Kickoff decides whether the work starts right away or a plan comes back for your approval first. Plan first is worth it on long work you'd rather redirect early.
Say what should come back
Under Deliverable: What would you like to get done?, each row reads as a sentence: create a new file, update the existing one, or write an answer in the conversation. A file row takes a type (xlsx, docx, pptx, pdf, csv or md) and where it lands: Drafts, Outputs, or a folder in the Library. Then describe what the file should contain.
At least one deliverable is required. It's the only required part of the brief.
Attach an example to a deliverable to have the work match it. Attachments upload when you save.
Add the parts you need
Four more parts are optional, offered under "Add anything else it needs":
| Part | The question it answers | Put here |
|---|---|---|
| Sources | "What should I read before getting started?" | The files, folders and places the work should be built from. Attach a reference file to a line. |
| Final checks | "What should I check before handing back the work?" | The tests the finished work has to pass: totals tie, every figure cited, no placeholder left in. |
| Preferences | "How would you like the work done?" | House rules that shape the result rather than define it: naming, rounding, tone, order of sections. |
| Questions | "What should I ask you before getting started?" | The things worth confirming with you rather than assuming: the hold period, which rent roll is current. |
Type @ in any line to insert a Library folder, a document type or a source (Outlook, Data room, Web research) by name.
Set how binding each line is
Every line in those four parts opens with a strength word you pick, and each part has three, from binding to advisory:
| Part | Binding | Default | Advisory |
|---|---|---|---|
| Sources | Use | Start from | Find |
| Final checks | Must | Should | Ideally |
| Preferences | Always | Prefer | FYI |
| Questions | Always | Unless clear | If unsure |
A new line starts on the middle word. Keep it there for most lines: the binding word is for the handful of rules a wrong answer would make useless, and a brief where everything is binding leaves no room to use judgment on the rest. In Questions, the binding word pauses the run every time, so reserve it for what you genuinely want to be asked on every deal.
Save it Private or Shared
The visibility control at the top of the brief offers Private to you or Shared with the team. Private means yours alone. Shared puts the command in front of everyone in your organization, and only an admin can save one.
Keep a command private while you're still finding out what it should say, and run it on a couple of deals first. Share it once the result is what you'd hand a colleague without editing, or when you want everyone producing the same thing the same way. A shared command you can't edit yourself offers Duplicate, which gives you a private copy to change freely.
Run it
Run a private command as /user:<name> and a shared one as /org:<name>, where the name is the title in lowercase with hyphens: "Screening memo from the OM" becomes /user:screening-memo-from-the-om. It also appears in the / menu with the rest.
New sessions pick up a command you just saved. In a session you already have open, run /reload-plugins.
Change one later
Save keeps the previous text: History lists earlier versions with Restore on each. Duplicate copies the brief into a new private command, which is the safe way to try a variant of something shared. Delete removes it from the list and from sessions; deleting a shared command removes it for the whole team.
If a teammate saved over the command while you had it open, a notice says so, your draft is kept, and you can reload theirs or save yours as a duplicate.
Next steps
- Commands: the commands that ship with the product, and the four verbs.
- Output Formats: attach house templates so what a command drafts follows your format.