← All use cases
Build the retro one-pager
The AI teammate that preps the retro.
Before retro starts, Lindy groups the sprint’s closed tickets by theme, works out velocity and shipped versus bounced, and posts the one-pager.
#eng9 members
+5
+5
Message #eng
#eng9 members+5
+5
Message #eng
#eng9 members+5
+5Building the retro one-pager
linear.readsprint 34 · 41 closed tickets✓
github.readmerges · mapped to tickets✓
slack.post_message#eng · one-pager posted✓3 tool calls · done in 1m 30sOne-pager posted. Themes, velocity, shipped versus bounced, and three discussion prompts, in the channel 30 minutes before retro starts.
📈 2🙌 2＋
Message #eng
Sprint 34 · retro one-pagerPostedVelocity52 points · up 8% on sprint 33Up
Shipped38 tickets · billing polish + mobile crashesDone
Bounced3 tickets · edge cases missed in reviewDiscuss
Carry-over6 points into sprint 35 · both paymentsWatch
Notion
PostHogPeople use Lindy at some pretty cool places.
Stop spending retro reconstructing the sprint.
The first twenty minutes go to remembering what even happened: someone scrolls the board, someone disputes the numbers, and the real conversation never starts.
Without Lindy
- ×Twenty minutes rebuilding the timeline.
- ×Velocity numbers disputed from memory.
- ×Bounced tickets nobody brings up.
- ×The real conversation never starts.
With Lindy
- The sprint summarized before you walk in.
- Velocity computed from the board.
- Bounced tickets named, with the pattern.
- Retro starts at the discussion.
More use cases
More things Lindy can take on.
Ready when you are.
Free to try. In your Slack in two minutes.
Prep your next retro7-day free trial • Cancel anytime