You run the ceremonies,Khint files the outcomes
Standup, planning, review, retro: you facilitate four ceremonies a sprint and the useful part scatters into a dozen docs. Khint turns each one's notes into something that lands where the team looks.
One note, three places
it needs to end up
A retro outcome belongs in Slack, in Confluence and in the tracker at the same time. A workflow can fan out to all three from one run, so you write it once and stop pasting the same paragraph into three tabs. The same session carries the whole sprint: what was committed at planning is still there when the retro asks what happened to it.
A real workflow: the note leaves the document it was written in and lands in the tools the team reads.
Two ways to keep what a ceremony produced
You facilitated the same hour either way. What differs is whether the outcome ends up somewhere the team will look again.
One note, three tabs to paste it in
You facilitated the same hour either way. What decides whether it mattered is where the outcome ends up, and how many hands carry it there.
- The retro outcome belongs in Slack, in Confluence and in the tracker, so the same paragraph gets pasted three times and drifts by the third.
- The blocker someone raised at standup stays a line in a scratch doc, which isn't a thing anyone can chase.
- Each ceremony gets its own document, so by the retro nothing remembers what the team actually committed to at planning.
- The recap gets written after the huddle, when half the round-the-room detail has already gone.
Pasted on the page
Pasted on the ticketKhint, one run, three destinations
A parallel step dispatches the same outcome to the tools your team actually reads, so it's written once and lands in all of them together.
- A parallel step dispatches to between two and four tools at once, so the outcome is written once and lands in all of them together.
- Select the note, run an Impediment agent to sharpen it into a problem statement with an owner, then file it as a Jira or Linear issue.
- One Memory session spans the whole sprint rather than a single meeting, which is the shape the job actually has.
- Post the standup recap to the channel from the same palette, before you leave the huddle and while the detail is still there.
The four pieces
a sprint of ceremonies runs on
A product owner grooms the backlog and writes stories. You run the ceremonies and clear the path, so these four are tuned for facilitation output rather than for backlog writing, and each is a shipped feature rather than a roadmap slide.
Workflows
A parallel step dispatches to between two and four tools at once, so the retro outcome reaches all of them from a single run.
Agents
Tuned for facilitation output: standup recaps, retro action items, impediment tickets, decision logs, on the notes as you type them.
Memory
One session spans the whole sprint, not one meeting, so the retro still remembers what was committed to at planning.
Integrations
The recap to a channel, the impediment as an issue, the retro published as a page, each one with your own token.
What changes across a sprint of ceremonies
Three things, and none of them adds a ceremony to your calendar.
- StopsPasting the same paragraph into three tabsOne run fans the retro outcome out to Slack, Confluence and the tracker together, so the note is written once and lands three times unchanged.
- LandsWhere the team already looksThe standup recap in the channel before you leave the huddle, the impediment as an issue you can chase, the retro summary on the page.
- Gets backThe facilitation that used to die in a scratch docEvery ceremony ends with something filed rather than something typed into a document only you'll ever open again.
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 agent 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 agents 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 agent 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 300 credits a month, about 10 AI actions a day, no credit card. Paid plans start at €7/month: Pro at €29/month gives 4,000 credits a month, 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 300 credits a month, about 10 AI actions a day. No credit card. Connect Jira, Linear or Slack when you're ready: each one takes your own token.