Hand over the project,not a pile of links
Rotating squads, going on leave, leaving the company: the handover doc always gets written in a panic on the last afternoon, from memory. Khint lets you assemble the real project state over your final week: pull Jira and Confluence into one work session, add what's in your head, and let AI draft the document from that context.
The project state lives in five tools,
your successor gets one afternoon of you
A handover written from memory misses exactly the things that hurt: the ticket that's blocked on legal, the decision that looks wrong until you know the constraint behind it, the workaround nobody documented. Khint's three pillars, Agents, Capture, and Memory, turn the handover into a week of small pulls and notes instead of one heroic writing session: collect the real state as you wind down, then draft the document from that collected context in one Action.
One week, one session, one page your successor reads
From “I'm rotating off” to a published Confluence page, without a last-day panic.
Start a session the week you know you're leaving
You're rotating to another squad at the end of the sprint, or heading out on a long leave. Start a Memorysession and name it “Handover · Payments squad”. From now on, everything you pull, capture, or draft for the handover lands in one place, on your machine, instead of in a scratch file you'll lose.
Pull the live project state into the session
Open the palette with Cmd+Shift+K and use the Jira rows: pull the active sprint, pull the two issues that are genuinely stuck, search for the tickets tagged to the migration. Pull the Confluence page that holds the architecture decision from March. Each pull lands as an entry on the session, so the handover is grounded in what the project actually looks like today, not what you remember of it.
Capture what has no clean text
Some context only exists on screens: the vendor dashboard, the legacy admin tool, the error your team keeps hitting. Run Extract text from the palette, drag over the region, and the text lands on your clipboard and in the session. No screenshots-in-a-folder that nobody will open later. How Capture works →
Add the things that live only in your head
The stakeholder who needs a heads-up before any schema change. The reason the team parked the redesign. The workaround everyone uses but nobody wrote down. Type these into the session as you think of them over the week; Khint keeps compacting the pile into a tight summary in the background, so nothing gets buried.
Draft the handover with one Action
Save an Actiononce: “Write a project handover: current state, in-flight work, key decisions and why, risks, who to talk to, first week checklist.” Run it, and because the session is active, its compacted context rides along on the prompt. The draft already knows the sprint state, the stuck tickets, and the decisions you pulled in, and you edit instead of staring at a blank page.
Publish to Confluence, where your successor will look
From the palette, run Confluence's Create page: the handover lands in your team's space with the title taken from the first line. Your successor gets one page that answers the first twenty questions they would have asked you, and your session stays on-device for replay if something comes up after you've moved on. How integrations work →
Why not just ask a chatbot to write the handover?
A chatbot writes a handover template: current state, risks, contacts, all headings and no facts, because it doesn't know your project. To make it useful you'd spend the afternoon pasting tickets and pages into the chat, which is the panic you were trying to avoid, routed through a browser tab. Khint inverts it: the facts accumulate in a Memory session as you wind down, pulled straight from Jira and Confluence or captured off the screen, and the drafting Action inherits that context automatically. The document comes out specific on the first pass. And because sessions never leave your device, the raw working notes behind the handover, the candid ones about what is stuck and why, stay yours; only the page you choose to publish goes to Confluence. If you want a recurring version of the same move while the project is still running, see the status report workflow.
Common questions
What actually goes into the handover session?
Whatever you put there, and nothing else. Start a Memory session and every move you make while it is on lands as an entry: the Jira issues and sprint state you pull from the palette, the Confluence pages you bring in, the screen captures of dashboards or legacy tools, the notes you type, the drafts you run. Khint compacts it all into a short running summary in the background, so by the time you sit down to write, the context is already assembled instead of scattered across ten tabs.
Does Khint write the Confluence page for me?
You draft the handover with a saved Action, then publish it from the palette with Confluence's Create page. The create flow formats your selected text with a saved Action you pick, and because your handover session is active, its compacted context rides along, so the page is grounded in the sprint state and decisions you pulled in, not written from a cold prompt. The title comes from the first line, you choose the space, and you confirm a preview before anything is created.
Can my successor read my Memory session directly?
No, and that is by design. Sessions live in a local database on your machine and are never synced to Khint's servers, so your raw working context stays yours. The handover artifact is the document you publish: a Confluence page they can read on day one. If your successor uses Khint too, they start their own session on the same project and build their own context from there.
We use Linear, not Jira. Does this still work?
Yes. Connect Linear from the MCP page and the palette gains Linear rows, so the drafting side of the flow works the same: run your handover Action with the session context attached and file the open follow-ups as Linear issues. The pull-heavy part of this walkthrough leans on the Jira and Confluence rows; for the Linear side, see how issue drafting works on the Linear issue drafting page.
Start collecting before your last week
Free with 10 AI actions and 5 captures per day. No credit card. Start the handover session early and let the context build itself.