
Sauna reads your Jira board and standup thread, drafts the sprint report, flags blockers, prepares the retro board, and chases the stale tickets so the team stays moving.
What it does
Sauna pulls velocity and completion data from Jira and drafts a sprint report in Confluence with what shipped, what slipped, and why.
It reads the standup thread and the board and posts a Slack summary of which tickets are blocked and on whom.
Sauna assembles a retro board in Miro-style notes within Confluence, seeding it with themes from the sprint's tickets and comments.
When a ticket sits untouched past its column SLA, it drafts a gentle Slack nudge to the assignee with the ticket link.
Put Sauna to work on this.
Get started for freeIn context
Sauna shows up where you already work — the web app, Slack, email, iMessage, and Superhuman. It reads what it needs, does the task, and comes back with the draft for your approval.
Try it
The literal prompt for this job. Open it in Sauna and it picks up from there.
“Pull this sprint's data from Jira, draft a sprint report covering what shipped and slipped, and post a blocker summary to the team channel before standup.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. It surfaces blockers and stale tickets and drafts nudges; reassignment stays with the team.
Every nudge is a draft you can edit or hold; nothing posts to a teammate until you send it.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring