
Sauna reads your Jira tickets, stakeholder threads, and process docs, then drafts the requirements doc, the as-is/to-be flow, and the acceptance criteria for your review.
What it does
From a Slack discovery thread and existing Confluence pages, Sauna drafts a structured BRD in Google Docs with scope, assumptions, and open questions flagged.
Sauna turns each user story in Jira into Given/When/Then acceptance criteria and posts them back on the ticket for the team to confirm.
It reads interview notes and builds a step-by-step as-is/to-be process table in Confluence, marking the gaps you'll need to validate with stakeholders.
Sauna keeps a decision log in Notion, watching Slack for resolved questions and drafting updates that mark each as decided or still pending.
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.
“Read the #project-onboarding thread and the current Confluence spec, then draft a requirements doc with scope, assumptions, and a list of open questions for me to review before I share it.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. It works only from your tickets, threads, and docs, and flags anything missing as an open question instead of filling it in.
It drafts comments and criteria, but nothing posts to a ticket until you approve the exact text.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring