Every workflow getsits own prompt pack
A product owner's day is not one job: it is intake, refinement, status, and triage, each wanting a different handful of prompts. Khint keeps each of those in its own pack, seeds you from first-party starters, and scopes the palette to whichever pack is active, so one shortcut always shows the right actions for what you are doing.
One long list of prompts
is a list nobody uses
The more useful prompts you save, the harder they are to find. A flat pile of thirty actions means scrolling past the twenty-nine that are wrong for the moment to reach the one you want, so most of them quietly go unused. Khint organizes prompts the way your week is actually organized: by job. A Pack holds the small set of Actions and Chains that belong to one context, and the palette only ever shows the active pack. Switching packs, not scrolling a mega-list, is how you find the right prompt.
From a starter pack to your daily toolset
Clone, group, switch: the shortcut follows your context.
Start from a pack you didn't have to write
On Agents, open Browse starter packs. The gallery shows five first-party packs: Meeting → Ticket, Dev Daily, Support Desk, Doc Polish, and Backlog Refiner. Preview a card to read each action, then Add to clone the whole pack into your personal packs. You have a working prompt library before you have written a single line.
Group actions by the job, not by the day
A Packbundles the Actions and Chains that belong together. Keep your intake actions (“Meeting notes → ticket”, “Refine to Definition of Ready”) in one pack, and your backlog-grooming actions in another. Drag the rows to set the order you will scan them in. Now each pack is a small, coherent toolset instead of one long list you scroll past.
Switch the active pack as your context changes
The palette is scoped to the active pack: the actions and the workflows you see under Cmd+Shift+K both come from whichever pack is active. Set the active pack on the Agents page, and the palette follows. Standup in the morning, refinement in the afternoon, support triage before you log off: same shortcut, the right five actions each time.
Reshape a starter into your house style
A cloned pack is yours to edit. Open any action and tighten its prompt: type a one-line description and press Generate for a first draft, or Improve to refine what is already there. Rename the pack, drop actions you never use, add one you keep re-typing. The starter is a head start, not a cage.
Chain a pack's actions into one keystroke
Inside a pack, a Chainruns up to five steps in series: agent actions and, where you have connected a tool, an integration write. Turn “clean up the notes → draft the ticket → open it in Jira” into a single Workflow, and the whole routine becomes one launch from the palette instead of four copy-pastes.
A PO's packs, over one day
Morning standup: your Meeting → Ticket pack is active, so Cmd+Shift+K surfaces exactly the actions that turn rough notes into tickets. Mid-morning grooming: switch to a Backlog Refinerpack and the same shortcut now offers “Refine to Definition of Ready” and epic-splitting actions instead. Afternoon support sweep: a Support Desk pack takes over. You never edited a setting mid-task or hunted through a giant list. You changed which pack was active, and the palette re-scoped itself. Pair a pack with an active Memory session and each action also sees the compacted context of what you have been working on.
Packs vs a folder of prompts
A folder of prompt text (in a doc, a notes app, a shared page) still has to be copied out, pasted into a chatbot, run, and the result pasted back into your tracker every single time. A Khint pack is different because its actions are runnable in place: you select text in the app you are already in, hit the shortcut, pick the action, and the output pastes back where you started. When you are ready to hand your setup to the rest of the team, the reusable AI actions flow lets one person own the house-style pack and everyone else clone it. For a broader tour of what a PO can assemble, see the product owner AI toolkit.
Common questions
What is a prompt pack in Khint?
A Pack is a named bundle of Actions and Chains: the actions live on the Agents page, the chains on the Workflows page. Each Action is a saved AI prompt: turn notes into a Jira ticket, refine to a Definition of Ready, tighten a status update. A Chain strings a few of those into a short workflow. The pack is the unit you organize and switch by: the palette is scoped to whichever pack is active, so you only ever see the actions that belong to what you are doing right now.
Do I have to build packs from scratch?
No. On the Agents page, open Browse starter packs to see a gallery of first-party packs (Meeting → Ticket, Dev Daily, Support Desk, Doc Polish, and Backlog Refiner) plus any packs published to the shared catalog when you are signed in. Preview a card to read exactly what its actions do, then Add to clone the pack into your personal packs. The card hides itself once you have added it, so you can tell at a glance what you have already taken.
How do I switch between packs?
Set the active pack on the Agents page. Because both actions and workflows in the palette come from the active pack, switching it changes what Cmd+Shift+K shows you. Keep a Meeting pack active during your standup, flip to a Refinement pack when you groom the backlog. The shortcut is the same, the list of actions follows the context.
Can my whole team use the same packs?
Yes. As the owner of a team you can Share a personal pack; teammates who joined see it read-only as a Team Pack and clone it into their own packs with Copy, after a preview modal shows every prompt first. The starter and switching story here is about organizing your own packs; the full sharing flow lives on the reusable AI actions page.
A pack for every part of your week
Free with 10 AI actions and 5 captures per day. No credit card. Clone a starter pack, switch by context, and run it behind one shortcut.