Your quarter has the context,your OKRs should too
OKRs written the night before the planning review read like it: vague objectives, key results with no baseline. Khint collects the quarter's real context in a work session (sprint data, decisions, whiteboards) and drafts objectives and key results from it, behind one keyboard shortcut, in the doc where you're already writing.
OKRs fail in the drafting,
not the reviewing
The raw material for good OKRs exists. It is just scattered across six weeks of strategy meetings, a Slack thread, last sprint's Jira board, and a whiteboard photo from the offsite. By drafting day, most of it has faded, so the objectives get written from memory and the key results get invented to fit. A chatbot doesn't fix that: it has none of your context and will happily produce generic, plausible-sounding goals. Khint takes the other route: gather the quarter's context as you go in a Memory session, then let a drafting action work from what actually happened.
From six weeks of planning to one OKR page
Collect the context all quarter, spend it on drafting day.
Open a Memory session for the planning cycle
Start a Memorysession named “Q3 planning” when the first strategy meeting lands on your calendar. From here on, everything you capture, pull, and draft is logged into it, and Khint keeps a compacted summary of the whole cycle, so the context that shapes your OKRs accumulates instead of evaporating between meetings.
Pull in the evidence a good OKR needs
Key results need baselines, and baselines live in your tools. With Jira connected, pull the active sprint or the quarter's key issues from the palette; with Slack connected, pull the strategy thread where the trade-offs were argued. Snap the roadmap slide or the whiteboard from the offsite with Capture and its text joins the session too. Each pull is one palette row, and each lands as an entry in your planning session.
Build a Draft OKRs action: your format, once
In Agents, create a Draft OKRsAction. Describe it in a line, “turn planning notes into at most 3 objectives, each with 2–4 measurable key results stating a baseline and a target”, and press Generate; Khint drafts the prompt, and Improve tightens it later. Your house OKR rules are now encoded in a reusable action instead of re-explained to a chatbot every quarter.
Select your raw notes and run it, anywhere
In whatever app your messy planning notes live (a doc, an email, your notes app), select the text and hit Cmd+Shift+K. The action sees your selection plus the compacted session context: the sprint you pulled, the Slack decision, the whiteboard. The draft objectives and key results paste back where you were typing, grounded in the quarter you actually had, ready for your edit.
Publish the page to Confluence in one step
When the draft survives your red pen, use the palette's Confluence → Create page row to publish it: Khint formats the page with a saved action, enriched by the same session context. Or wire the whole routine as a Workflow: draft, tighten, create the Confluence page. One keystroke from notes to a page the team can argue with.
One drafting standard, every quarter, and every teammate
Because the Draft OKRs action is a saved Agent, not a prompt in your head, next quarter starts from the same standard, and so can the other POs. Bundle the drafting and tightening actions into a pack and share it with your team: everyone's objectives come out in the same shape, which makes the roll-up review about the goals, not the formatting. Sensitive strategy notes stay off browser chatbots along the way: sessions live locally, and only what you select leaves your machine.
Common questions
Does Khint come with a built-in OKR template?
No, and that is the point. You author a Draft OKRs Action once, encoding your house rules: how many objectives, how many key results each, whether KRs must carry a baseline and a target. Type a one-line description in the Action editor and press Generate to get a first prompt, then Improve to refine it. From then on your format is the format, every quarter.
Won't the AI just invent plausible-sounding metrics?
A draft is only as grounded as what it can see, which is why Khint pairs the action with Memory. The draft is built from the text you select plus the compacted context of your active planning session: the sprint data, decisions, and notes you actually pulled in. And it lands as editable text right where you are writing, so you review every number before anything is published.
Where does my strategy material go?
Memory sessions live in a local database on your machine; they are not synced to Khint's cloud. When you run an action, only the text you selected plus the session's compacted summary are sent for processing. Draft objectives, unannounced bets, and internal metrics are exactly the material you don't want pasted into a browser chatbot.
Can I publish the finished OKRs to Confluence without leaving Khint?
Yes. With Jira and Confluence connected, the palette has a Create page row: Khint formats your draft using a saved Action (enriched with the planning session's context) and creates the Confluence page. You can also chain it: a Workflow can run your drafting and tightening actions and end on a Create Confluence page step, so notes-to-published-page becomes one keystroke.
Draft OKRs from your real quarter
Free with 10 AI actions and 5 captures per day. No credit card. Start the planning session today; thank yourself on drafting day.