You run the ceremonies,Khint files the outcomes
Standups, planning, review, retro: you facilitate four ceremonies a sprint, and the useful bits scatter into a dozen docs. Khint turns each ceremony's notes into a clean artifact behind one shortcut, and posts it where the team will see it: Slack, Jira, Confluence.
You capture everything,
none of it lands anywhere
A scrum master's value is in the follow-through: the impediment that gets cleared, the retro action that actually happens next sprint. But the notes live in a running doc no one reopens, and re-typing them into Jira or Slack is the chore that quietly gets skipped.
Khint closes that gap without replacing your tools. Select any note in any app and run an AI Action on it in place, reshaped into a recap, an impediment, or a decision log. Keep a Memory session running for the whole sprint so every ceremony knows what the last one decided. And when an artifact is ready, push it into Jira, Linear, Slack, or Confluence from the same palette. One write per run, so every update is deliberate.
One sprint,
every ceremony in the same session
Every step below is a shipped feature, not a roadmap slide.
- PlanningOpen one session for the whole sprintBefore planning starts, press Start on a Memory session called 'Sprint 24'. From now on, everything you capture and every Action you run gets compacted into a short running context, so by the retro, the session still remembers what the team committed to on day one.
- StandupJottings → async recap, postedType the round-the-room notes as they come. Select them, run a 'Standup recap' Action, and get a clean Yesterday / Today / Blockers summary, then post it to Slack from the same palette, so the async channel is updated before you leave the huddle.
- Mid-sprintA blocker becomes a tracked impedimentSomeone raises a dependency that's stalling two stories. Select the note, run an 'Impediment' Action to sharpen it into a problem statement and owner, then use the Jira Create issue or Linear Create issue row: the impediment is a ticket you can follow up on, not a line in a doc.
- ReviewTurn the demo notes into a summaryDuring sprint review, capture what shipped and the feedback in the room. A 'Review summary' Action reshapes it into a stakeholder-ready recap; because the session is active, it already knows the sprint goal you set at planning.
- RetroRaw retro notes → recap + trackable actionsPaste the sticky-note dump. One Action returns a clear recap plus the improvement actions with owners; file each as an issue so next sprint actually inherits them. Publish the recap to Confluence with Create page for the team to read.
Impediments are your job,
make them tickets, not sticky notes
The blocker raised in standup is worth nothing until it's assigned and visible. In Khint, save an Impediment Action: no prompt to write, type a one-line description and press Generate, or clone a starter pack and edit it. Select the raw note, run it, and get back a tight problem statement, the affected stories, and a suggested owner. Then chain it: a Workflow can run the reshape Action and end with a Jira Create issue or Linear Create issue step, so one shortcut takes a spoken blocker to a tracked ticket with a link you can paste back into the channel. Use Change statusto close it out when it's cleared.
The four pieces you'll lean on
Common questions from scrum masters
How does a scrum master actually use Khint?
You facilitate; Khint captures the outcome. In any ceremony, select your rough notes (a blocker someone raised, a retro theme, the standup jottings), hit Cmd+Shift+K, and run a reusable AI Action that turns them into a clean, shareable artifact. The same palette posts a standup recap to Slack, creates an impediment as a Jira or Linear issue, or publishes a retro summary to Confluence, so nothing you facilitated dies in a scratch doc.
Isn't this the same as the product owner using Khint?
The tool is shared; the job isn't. A product owner grooms the backlog and writes stories. A scrum master runs the ceremonies and clears the path, so your Actions are tuned for facilitation output: standup recaps, retro action items, impediment tickets, decision logs. One Memory session spans a whole sprint's ceremonies, which matches how a scrum master works: the same session carries planning into every standup and into the retro.
Where do impediments and team notes go?
Only what you explicitly act on leaves your machine. An Action sees the text you selected plus, if you opt in, the active Memory session's compact summary, nothing else. Memory sessions live in a local SQLite file on your Mac and are never synced to a server; Atlassian, Linear, and Slack credentials stay in your OS keychain. Stop the session and that context is closed.
Is there a free plan, and what does it run on?
Yes, the free tier includes 10 AI actions per day and 5 screen captures per day, no credit card. Paid plans start at €7/month: Pro at €29/month gives 100 AI actions a day, and every plan includes all the work integrations. Khint runs on macOS 13+ and Windows 10 22H2+, and connects to Jira, Confluence, Linear, Slack, Notion, and Gmail with your own API token or OAuth: it writes into those tools, it doesn't replace them.
Run your next ceremony with it
Free with 10 AI actions and 5 captures per day. No credit card. Connect Jira, Linear, or Slack when you're ready: it takes an API token, not an admin.