rtro collects your team's cards all sprint and keeps them face down until the meeting. You walk in with the board already full, and walk out with tickets.
It's the real board, not a video. Click anything to take over.
Staging breaks on Tuesday. You add a card on Tuesday, while you still remember why. One link, no account needed to write a card.
The facilitator reveals every card at once. Nobody wrote theirs after reading the loudest person's. Three votes each, then talk about what won.
Actions get an owner and go to your tracker as real issues. Next retro opens with their status, so "we said we'd fix that" has an answer.
Most tools stop at "export". rtro creates a real issue for each action in GitHub, Linear or Jira, then pulls its status back when the next board opens. What your team promised is the first thing everyone sees.
No more scrolling through last month's doc to ask what happened to the staging fix.
The server never sends a card you are not allowed to read yet. Not to teammates, not to the facilitator.
Author names never leave the server, in any phase. Cards get judged on what they say.
A fixed budget, stackable on one card. The meeting's time goes to what actually won.
An action without a name attached is a wish. rtro asks for the name before it leaves the room.
The outcome copies as plain Markdown, ready for the sprint notes, Slack or the wiki.
Name a board and share one link — nobody signs up. It disappears after 24 quiet hours, so export the outcome before it goes.
Connect a tracker once per team. Each action becomes a real issue — titled by the action, with the owner, the source card, the votes and a link back to the board in its body. Status flows back before your next retro.
Installed as a GitHub App on your org, so issues open where the code lives. Closed comes back as done.
Connects with OAuth and maps your workflow states, so started reads as in progress and completed as done.
Connects with OAuth. Pick a project once, and every synced action files itself as an issue there.
One-way by design: rtro creates issues and reads their status. It never edits, closes or imports them.
A retro only works if everyone is in it. Invite the contractor, the designer and the new hire without doing seat math.