Write the prompt once,the whole team runs it

Five product owners each keep a slightly different prompt for turning notes into tickets, and the output drifts. Khint lets one person build an AI action, bundle it into a pack, and share it, so every teammate clones the same house-style action and runs it behind the same keyboard shortcut.

For product owners, business analysts, and the teams they run with. Works in any app: the tracker, the doc, the browser.

Everyone reinvents
the same prompt

A prompt that turns rough meeting notes into a clean Jira ticket is worth writing well: once. But on most teams it gets rewritten by everyone, badly: one PO pastes into a chatbot with a prompt they tuned last quarter, another uses a different one, a new BA gets none of it. The output shape drifts, tickets read inconsistently, and onboarding means teaching folklore. Khint fixes this at the source: build the action as a reusable Agent, bundle it in a pack, and share the pack so the good version is the version everyone runs.

From one person's action to the team's standard

Build it, bundle it, share it: teammates clone and run.

  1. Build the action once, the way the team should do it

    In Agents, save the Action you keep re-typing: “Meeting notes → Jira ticket”, “Refine to Definition of Ready”, a house-style status update. No prompt yet? Type a description and press Generate; tighten it later with Improve. This is the version your team should run, authored and tested by one person instead of five.

  2. Bundle related actions into a pack

    A Pack is a bundle of Actions and Chains. Group the ones that belong together (everything a PO needs for the intake loop, say) so the palette stays scoped to the active pack and nobody scrolls past twenty unrelated actions to find the right one. Drag rows to set the order teammates will see.

  3. Share the pack with your team

    Own a team and press Share on the pack. Khint takes a snapshot and publishes it to the team, where members see it below their personal packs as a read-only Team Pack. Update the pack and re-share to push a fresh snapshot. Your teammates always see the current house standard, not a stale forwarded prompt.

  4. Teammates join and clone in one click

    Send the invite link (khint.app/join/<code>); a teammate signs in and joins. Your shared pack appears in their app. They click Copyto clone it into their personal packs, and a preview modal first shows every Action's prompt and every workflow's steps, so they adopt the pack with eyes open.

  5. Everyone runs the same actions behind one shortcut

    Now the whole team hits Cmd+Shift+K, picks the shared action, and gets output in the same shape: same acceptance-criteria format, same ticket structure, same tone. Chain a few of the actions into a Workflow and a multi-step routine becomes one keystroke for everyone who cloned the pack.

Why not just paste prompts into a shared doc?

You can keep a page of prompts in Confluence, but a prompt in a doc still has to be copied out, pasted into a chat, run, and the result pasted back into the tracker, every single time. A shared pack is different because it is runnable: a teammate clones it once and the action lives behind Cmd+Shift+K, working on whatever text they have selected, in the app where the work already lives. And a starter you didn't write is safe to adopt: the preview modal shows every prompt before you clone, so a shared action is never a black box. Prefer a head start? Clone a first-party starter pack and share your reshaped version.

Common questions

How do I share an AI action with my team?

Save the Action inside a Pack on the Agents page, then use Share on that pack. Khint snapshots the pack to your team, and teammates who have joined see it below their personal packs as a read-only Team Pack. One account owns one team, so there is a single, clear place your house-style actions live.

Do teammates edit my shared pack, or get their own copy?

They get their own copy. A Team Pack is read-only; a teammate clicks Copy to clone it into their personal packs, where they can tweak it freely without touching your original. Before the clone lands, a preview modal shows every Action's full prompt and every workflow's ordered steps, so nothing runs that they haven't read first.

How does someone join the team?

As the owner you share an invite link of the shape khint.app/join/<code>. The teammate opens it, signs in, and joins. After that your shared packs appear in their app. Joining grants visibility into the shared packs, not billing: every person keeps their own plan and their own daily action and capture limits.

Do I have to write every prompt from scratch?

No. In the Action editor, type a one-line description and press Generate. Khint drafts the prompt, and Improve refines it in place later. Or open Browse starter packs on the Agents page and clone a first-party pack (Meeting → Ticket, Dev Daily, Support Desk, Doc Polish, Backlog Refiner) as a starting point, then reshape it and share your version.

Where do shared packs and my text go?

Packs sync to Khint's cloud so they follow you across your devices and can be shared with your team. The content you run actions on does not: an Action only ever sees the text you selected, plus the compacted summary of your active Memory session if you opted in, and Memory sessions stay in a local database on your Mac. Your prompts travel; your selected work does not.

Give your team one good version

Free with 10 AI actions and 5 captures per day. No credit card. Build the action once, share it, and everyone runs it.