Commands
Ask in plain language, or use a command when you want a known type of output.
Ask the terminal for anything in your own words: "pull apart the rent roll", "what's the debt yield at the ask?", "draft the term sheet".
A command is work Cap Orbit knows how to do end to end. Use one when you want a known type of output or review; your documents, templates, and instructions still shape the result. The quick-starts on a new session are commands too.
Run a command
Type / in the composer to browse, or run /help and open its Commands tab for the whole list. Work commands are named /<group>:<name>, and the group tells you the kind of work:
extract,draft,update,review: the four verbs belowdeal: work on the deal itself, like saving a fact to deal memory or finalizing a packagedocuments: document production and checksportfolio: work across every deal, in Portfolioorganduser: the commands your organization wrote, and the ones you wrote yourself
Type @ to hand a command a specific file.
The four verbs
The same verb means the same thing in every group:
| Verb | What it does | Example |
|---|---|---|
| extract | Organizes source information into cited data, without producing a recommendation. | /extract:rentroll |
| draft | Builds a new deliverable from deal data, models, and your templates. | /draft:screening-memo |
| update | Revises an existing deliverable for what changed, and reports what moved. | /update:screening-model |
| review | Checks a deliverable against its references and reports findings; fixing is a separate step you ask for. | /review:memo |
Drive a closing checklist
/draft:closing-checklist reads the deal's commitment, loan agreement, purchase agreement, and the paper around them, and lists every condition to close: the item, the section it comes from, the party who delivers it, its due date, and its status, grouped into closing, funding, and post-closing.
As deliveries arrive, /update:closing-checklist revises the checklist you already have for what moved: items in, conditions waived, dates slipped. Whether a condition is satisfied stays with you and counsel.
Turn work you just did into a command
/power-up saves a piece of work as a command you can run again. Run it once the current turn has finished, answer the round of questions about what the command should cover, and it saves the result as your own command, which runs as /user:<name>.
Where results land
File-producing commands save their results as Office files (xlsx, docx, pptx, or pdf) in Drafts. /deal:finalize snapshots a package into a dated Outputs folder as the version of record.
New commands
A session you open has whatever was published before it. When commands are published while you're working, an update notice appears: run /reload-plugins to pick them up in the conversation you're already in.
Next steps
- Write your own command: turn work you repeat into a command of your own, kept private or shared with the team.
- The composer: the
/menu, the@picker, and keyboard shortcuts. - Output Formats: attach house templates so drafted work follows your format.