What you can do with your agent
Everyday things to ask your agent once it's connected, from catching up and recording decisions to writing documents and answering comments.
Have your agent do it
Paste this to your agent. It reads this guide and works through it with you.
Read https://avalandra.com/help/what-your-agent-can-do.md. Then look at what's in my Spaces and suggest three of these I'd get the most from this week.Once your agent is connected, you work with Avalandra by asking it in your own words. It reads your team's record, answers with where each answer came from, and writes back what's worth keeping. Everything it writes shows its name, such as "[Your name]'s agent (Claude)".
Each request below is something your agent can do today. Copy one, fill in the parts in [square brackets] with your own Space, documents and people, and paste it to your agent. If you leave a bracket in, your agent should ask you what goes there.
Claude connected through the connector can do the catch-up, decision, meeting, document and comment requests. Organising Spaces and exporting a Space need an agent connected with the install command, such as Claude Code.
When a request produces a document, the prompt points your agent at one of our templates, so what it writes is easy to read in light and dark and on a phone. Each template below is filled with sample content to show the layout; your agent fills it with yours. You can see every template at the end of this guide.
Catch up
Find out what happened while you were busy or away.
I've been away since [date]. Read the [name of your Space] Space and write me a catch-up: what we decided, why, and what's waiting on me. Link each point to where it came from. Use the template at https://avalandra.com/help/template-files/catch-up. Name it "Catch-up" followed by today's date, and nothing longer.What's waiting on me in Avalandra? List the comments that mention me and the replies to my comments, newest first. Use the template at https://avalandra.com/help/template-files/waiting-on-you. Name it "Waiting on you" followed by today's date, and nothing longer.Ask about a decision
Get the answer from the record, with who decided and the source.
Why did we decide [the decision you're asking about]? Look in the [name of your Space] Space, tell me who decided and when, and link me to where it was decided. If I ask you to save the answer, use the template at https://avalandra.com/help/template-files/decision-explainer. Name it "Why" followed by a topic of a few words, and nothing longer.Record a decision
Keep the reason with the decision, so nobody has to remember it.
Record a decision in the [name of your Space] Space: [what was decided], because [the reason]. Link it to [where it was decided, such as today's meeting]. Use the template at https://avalandra.com/help/template-files/decision-record. Name it "Decision" followed by a topic of two or three words, and nothing longer.Ask about a meeting
Meetings come in from Granola and Zoom once they're connected. See Bring in your meetings.
What did [person] say about [topic] on [the meeting]? Quote their words, say who else spoke, and link me to the transcript.Summarise [the meeting] into the [name of your Space] Space from its sanitized transcript: decisions, actions with owners, and open questions. Use the template at https://avalandra.com/help/template-files/meeting-summary. Name it with the meeting's short name, the word "summary" and the meeting date, and nothing longer.Write and update documents
Your agent can write a document into a Space or update one that's already there.
Write a one-page brief for [what it's about] from what's in the [name of your Space] Space, and put it in the [folder name] folder. Use the template at https://avalandra.com/help/template-files/brief. Name it with a topic of two or three words followed by "brief", and nothing longer. Tell me the link when it's done.Update [the document] in the [name of your Space] Space: [the changes you want]. Keep the rest as it is.Comment and reply
Your agent can comment on a document, reply in a thread and mention a teammate. Comments are plain text, so there's no template. Ask for a short reply that answers first and links its source.
Read [teammate]'s comment on [the document] and reply with what we decided about [the topic]. Answer in one or two sentences, link the decision, and mention [anyone who should see it].Follow up after a meeting
Turn a meeting into an update for people who weren't there. See Follow up after a meeting.
Write a short update for [the person, such as a client] from this week's work in the [name of your Space] Space: what's done, what's next and anything we need from them. Leave out internal discussion. Use the template at https://avalandra.com/help/template-files/client-update. Name it "Update for" followed by their name and today's date, and nothing longer.Organise your Spaces
Move documents to where they belong, and share a Space with a teammate who already has an account.
Move [the documents] in the [name of your Space] Space into the [folder name] folder, and add [teammate] so they can edit the Space. Then write down what changed, using the template at https://avalandra.com/help/template-files/space-changes. Name it "Space changes" followed by today's date, and nothing longer.To bring someone new into your team's Avalandra, an admin invites them by email and they accept in their browser. Your agent can't accept an invite for anyone.
Templates
Each template is a ready-made Avalandra document filled with sample content. Your agent swaps in your content and keeps the layout.
- Catch-up: what changed while someone was away
- Waiting on you: mentions, replies and review requests
- Why it was decided: the answer, who decided, the reasons and sources
- Decision record: one decision with its reason and source
- Cleaned transcript: a full transcript with private discussion taken out
- Meeting summary: decisions, actions, quotes and open questions
- Brief: a new working document, such as a brief or spec
- Update for a client: what's done, what's next, what you need
- Space changes: what moved and who was added
- Export record: when a Space was exported and where the file is
Questions
Who can see what my agent writes?
Everyone who's a member of the Space it writes in. Each change and comment shows your agent's name. Anything in your private Space is visible only to you.
Does Avalandra remember what I said to my agent?
Only what gets written into a Space. Your conversation stays in your agent's own tool. When something's worth keeping, such as a decision and its reason, ask your agent to record it in the Space.
Can my agent accept an invite for me?
No. Invites are for people. You open the link in the email and sign in in your browser. Agents connect with their own one-time code instead.
Can I move a document to another Space?
Yes. Ask your agent to move it. Its link keeps working after the move.
Can I take my data out?
Yes. Ask your agent to export the Space, with its history, to a ZIP file on your computer, and it does the whole thing for you. A large Space can take a few minutes. The file isn't encrypted, so keep it somewhere only the right people can open. This needs an agent connected with the install command, such as Claude Code. Your agent can also note the export in the Space using the Export record template.
Can I bring an export back in?
Yes, into a new, empty Space. An export doesn't merge into a Space that already has things in it.
For agents
What each request above uses:
- Read and answer:
ava document tree --space SPACE_ID,ava document get DOC --space SPACE_ID --json,ava document render DOC, andava changes list --space SPACE_IDfor what changed. Cite records with therefthe CLI returns, and give peopleweb_url. - What's waiting:
ava agent check-in --json. It is read-only and lists mentions, replies and review requests. - Write a document:
ava document createwith"kind":"html"and aparent_idfor the folder. Replace an HTML document's source withava document edit DOC --expected-revision REV. - Comment:
ava document comment create|replyon HTML documents andava document text-comment create|replyon text documents. A mention needs@Namein the body and an entry inmentionsfromava comment mention-suggestions. - Organise:
ava document movewithin a Space,ava document transferbetween Spaces. Re-readava document treeafterwards. - Share a Space:
ava space members grant --space SPACE_IDwith the person'sprincipal_idfromava user list. Only an organization admin can create invites, and only a person can accept one. - Export:
ava space export SPACE_ID --output PATH --idempotency-key KEY. It waits for the archive, checks it and writes it with owner-only permissions; a large Space takes minutes (a 126 MB Space took about two). The response'sverifiedshould betrue, andsecurityreadsunencrypted, so tell the person.ava space exports SPACE_IDlists past exports. - Templates: fetch the template the person's prompt names, and title the document with the template's short name pattern (on its page and in the file's top comment), such as "Catch-up 10 Nov", never a long descriptive title, and don't repeat the title inside the document. Keep its
<style>block and class names, replace every piece of sample content with content from the record (never carry over its names, Spaces, documents or dates), and delete sections that have nothing in them. Create it withava document create("kind":"html","source_format":"html") and readwarningsin the response, which lists anything the renderer removed, such as scripts, forms, external images and fonts. - If a prompt still contains [square brackets], ask the person what goes there. Never invent a Space, document, folder or person, and never create a Space to match a name you can't find.
- Every write takes
--idempotency-key. Before writing anything people will read, confirm the destination and its readers with the person.