Skip to the template

Pruning review

Suggestions for pruning a Space, grouped by what to do, with the evidence and reason for each. Nothing changes until you decide.

Have your agent do it

Would you like this done once, or automatically?

A regular review keeps the Space trustworthy before clutter builds up. Fill in the parts in [square brackets], then paste this to your agent.

Once
Review the [name of your Space] Space and suggest how to prune it, with the reason for each suggestion. Don't change anything yet. Use the template at https://avalandra.com/help/template-files/pruning-review. Name it "Pruning review" followed by today's date, and nothing longer.
Automatically
On the [first Monday of each month, or another rhythm], review the [name of your Space] Space and suggest how to prune it, with the reason for each suggestion. Don"t change anything. Use the template at https://avalandra.com/help/template-files/pruning-review, named "Pruning review" followed by today"s date, and tell me it"s ready.

When to use it

  • It's time for a regular review of a Space.
  • A project phase ends, or someone new is about to join.

What to name it

Pruning review [date], such as “Pruning review 10 Nov”. Keep it that short; agents otherwise tend to write long, descriptive titles.

What it looks like

Filled with sample contentOpen the file on its own
DocumentPruning review 10 Nov

Used in

  1. Space changesWhat was moved, archived, removed or shared in a Space, and why.
  2. Decision recordOne decision with its reason, who made it, its source and what it replaces.

For agents

  • Fetch the template from https://avalandra.com/help/template-files/pruning-review.
  • Keep its <style> blocks and class names. Replace every piece of sample content with content from the record, and never carry over its names, Spaces, documents or dates.
  • Title the document Pruning review [date], filled in, such as “Pruning review 10 Nov”. No longer, descriptive titles, and no title or label repeated inside the document: Avalandra shows the name above it.
  • Delete sections with nothing in them, and link every claim to its source with web_url.
  • Create it with ava document create (kind html, source_format html, and a parent_id for the folder), then read warnings in the response for anything the renderer removed.
  • If the prompt still contains [square brackets], ask the person what goes there.
Support