SmartRetro helps engineering teams run better retros, spot recurring issues, and turn discussion into action. It watches the working signals your team already produces — Slack channels you opt in, repo and tracker events — and stays quiet until something is worth your attention.
The loop
SmartRetro runs one loop, continuously:
- Listen. Connected sources send events. Nothing is read until an admin opts a channel or repo in.
- Surface. When activity crosses a threshold — a blocker that keeps coming up, work that says “done” but isn’t, the same theme in a third retro — it becomes a signal in your feed. Every signal links back to its raw source. If we can’t show the source, we don’t surface it.
- Decide. People give each signal a verdict: real, noise, worth discussing, or mute. SmartRetro tunes itself from your calls. AI detects and recommends; your team decides.
- Meet. Before each retro, SmartRetro assembles a brief: what happened since last time, what’s recurring, and which action items are still open.
- Follow through. Action items keep owners, due dates, and status. Overdue items nudge their owner and carry forward into the next brief so nothing quietly disappears.
Teams are the unit
Everything in SmartRetro — signals, retros, action items — lives inside a team. The team switcher in the sidebar sets your scope: one team’s workspace, or “All my teams” with every row tagged by team.
What SmartRetro doesn’t do
It doesn’t read direct messages, store your source code, or take action on its own. The specifics of what we read and store are on the Trust & security page.
Currently in beta
SmartRetro is in a closed beta. If you don’t have access yet, join the waitlist.