Turn one big epicinto stories that fit a sprint
An epic is a wall of intent. Khint slices it into vertical, sized user stories with a reusable AI action, keeps the context with Memory, and files each story into Jira from the same keyboard shortcut.
The decomposition tax
nobody budgets for
Writing the epic is the easy part. The grind is everything after: splitting it into stories small enough to estimate, making each slice deliver value on its own, drafting acceptance criteria, and copy-pasting the whole project background into a chatbot every time you start a new conversation. Khint compresses that grind with its three pillars: Agents, Capture, and Memory, wired together behind one palette, so the breakdown happens where the epic already lives.
One epic, start to filed stories
Breaking down a “self-serve plan downgrade” epic, step by step.
Start a session for the epic
Before you open the planning doc, start a Memory session, call it “Self-serve plan downgrade”. Everything you run from now on is logged to it, and Khint keeps a compact running summary. That summary rides along on every AI Action, so the breakdown stays anchored to this epic and not last week's. How Memory works →
Save a reusable breakdown Action
In Agents, create an Action like “Break epic into stories”. Don't have a prompt? Type a description and press Generate. Khint drafts one that asks for vertically-sliced stories, each with a clear value statement and an INVEST-style check. Or clone the Backlog Refiner starter pack and start from a working Action.
Run it on the epic
Select the epic description wherever it lives, hit Cmd+Shift+K, and run your breakdown Action. Khint returns a list of candidate stories (sliced thin enough to fit a sprint) and pastes it back in place. Because the session context is attached, the model already knows the constraints you captured earlier in the session.
Sharpen each slice
For any story that needs detail, select it and run a second Action: an acceptance-criteria drafter that returns Given/When/Then and edge cases. Chaining your slicing and criteria Actions into one Workflow turns “epic → ready stories” into a single keystroke. Acceptance criteria, in one action →
File the stories where the team works
With Atlassian connected, the palette grows a Jira Create issue row: select a story, file it under the project and issue type you pinned, one issue per run. Prefer a single artifact? Use Confluence Create page to publish the whole breakdown for refinement. How integrations work →
Why not just paste the epic into a chatbot?
You can, and you'll re-paste the roadmap context into every new chat, restate the slicing rules you like, and copy each result back out by hand. Khint removes the round-trips: the breakdown Action is saved once and reused on every epic, Memorycarries the project context into every prompt automatically, and the Atlassian and Linear integrations file the stories where the team will actually read them. Because Actions only see the text you select (plus the session summary you opted into), your unreleased roadmap isn't sitting in a chat history.
Common questions
How does Khint break an epic into user stories?
You write a reusable Action (an AI prompt) that takes a rough epic description and returns a list of vertically-sliced stories. Select the epic text in any app (your planning doc, a ticket, an email), hit Cmd+Shift+K, and run the Action. Khint sends only the selected text (plus, optionally, your active session summary) to the model and pastes the breakdown back. You can save it once and reuse it on every epic.
Do I have to write the breakdown prompt myself?
No. In the Action editor, type a one-line description and press Generate. Khint drafts the prompt for you; press Improve later to refine it in place. Khint also ships a Backlog Refiner starter pack you can browse and clone from the Agents page, so you have a working slicing Action without writing anything.
Can Khint create the stories in Jira for me?
Yes, once you connect Atlassian with your email, API token, and cloud domain. The palette then shows a Jira Create issue row: pick a story from your breakdown, select it, and file it. Title and body are taken straight from the text, with the project and issue type you pinned. Khint files one issue per run, so you create each story explicitly; the parent epic link is set in Jira. Confluence Create page is there too if you'd rather publish the whole breakdown as a page.
Where does my epic text go?
An Action only ever sees the text you selected, plus the compacted summary of your active Memory session if you opted in. Memory sessions live in a local SQLite database on your Mac and are never synced to Khint's servers. Stop the session and the context is closed. Nothing about your roadmap leaves your device silently.
Try it on your next epic
Free with 10 AI actions and 5 captures per day. No credit card. Save the Action once, slice every epic after.