How do I get a Miro or FigJam retro board into the bot?

Select the sticky notes and copy — both tools paste as plain text lines — then send that to @vustbot with the column labels typed in. There's no board plugin or integration; text is the whole interface. Even a typed-up whiteboard photo works if you transcribe the cards.

Can AI spot the same retro complaint recurring across sprints?

Yes, if you feed it the history: paste last retro's summary alongside the new board and ask "flag themes appearing in both". A complaint surviving two retros unaddressed is your real process bug, and this two-paste comparison surfaces it more reliably than anyone's memory of six weeks ago.

Should the retro summary include who wrote which card?

No — retros run on qualified anonymity, and a summary that attributes complaints teaches people to write blander cards. The template here strips names except in the experiment-owner column, where accountability is the point. Themes stay collective; commitments stay personal.

Write a Retrospective Summary with AI

Export or copy your retro board — the went-well, went-poorly and try-next columns — paste it into @vustbot, and ask for a themed summary with the agreed experiments and their owners. Twenty sticky notes collapse into three themes and a commitments list you can actually check next retro. Paste in, artifact out, priced per action.

Retros produce the most honest text a team writes all sprint — and then it dies on the board. The gap between "we discussed it" and "we changed it" is a written summary with owners, which is a five-minute AI job on text you already generated together.

Open @vustbot in TelegramPay per action · no signup beyond Telegram

What the AI does in this scenario

Twenty sticky notes → 3-4 named themes, duplicates merged
Agreed experiments listed with owner and a check-by date
Recurring complaints flagged when you paste last retro's summary too
Neutral wording that survives being read by people outside the room
Board export, Miro copy-paste or typed notes — any text works

Worked example: write a retrospective summary with ai

Input

Went well: demo prep smooth / pairing on the parser / release checklist held. Went badly: 3 cards say some form of "QA started too late" / scope creep on search / flaky CI x2. Try: QA joins planning. freeze scope after day 3. Vlad owns CI flakiness.

Output

Retro summary — Sprint 14. Themes: 1) Late QA involvement (3 of 8 negative cards — dominant theme). 2) CI flakiness (recurring, now owned). 3) Scope discipline. Wins to keep: release checklist, parser pairing. Experiments: QA attends planning (owner: needed!), scope freeze after day 3 (team), CI flakiness audit (Vlad). Check all three at Sprint 15 retro.

How to write a retrospective summary with ai — step by step

1
Dump the board as text
Copy the columns out of Miro, FigJam or the whiteboard photo you typed up — column labels included. @vustbot has no board integration; the paste carries everything.
2
Ask for themes, not a list
The instruction that matters: "merge duplicate cards into themes and count how many cards each theme absorbed". Three cards saying "QA too late" is a signal; a summary that lists them separately wastes it.
3
Nail down owners while the room remembers
The generated experiments list will expose ownerless items — assign them in the team chat the same day, and paste this summary into next retro's prep to check what actually changed.

AI vs doing it manually

The scrum master's hand-written retro summary has one advantage AI can't match: they were in the room and know which card carried heat. Its weakness is that it takes 30-45 minutes nobody has after a retro, so it often shrinks to a photo of the board — write-only memory. The AI summary takes two minutes on the same text, merges duplicates honestly, and never softens a theme because someone senior wrote the card. Best split: model produces the themed draft, facilitator adds the one line of room-context per theme, team gets it while the retro is still warm.

The prompt to copy

Summarize this retrospective board. Merge duplicate cards into themes and state how many cards each theme absorbed; rank themes by card count. Sections: Themes (ranked), Wins to keep, Agreed experiments as Experiment — Owner — Check-by date (mark missing owners as NEEDED). Neutral tone, keep team members' names only in the owner column. Board: [PASTE COLUMNS]

Frequently asked questions

Related in Meetings

Try it on your real task

The welcome bonus covers a first run — send the prompt above with your own facts and judge the output yourself.

Open @vustbot